Alrm Clear 4xe31

323-1123-543
SDH TRANSMISSION
Nortel TN-4XE
Alarm Clearing Procedures
Release 3.01 Standard March 2000

SDH TRANSMISSION
Nortel TN-4XE
Document Number: 323-1123-543

Product Release Number: Release 3.01
Status: Standard
Date: March 2000
Copyright © 1998 - 2000 Nortel Networks, All Rights Reserved.
Printed in England
The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL:The information contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein
confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information
contained herein.
So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of
data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein
or any third party arising out of the contents of this document.
*NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are
trademarks of Nortel Networks.
Netscape is a trademark of Netscape Communications Corporation.

OPTERA is a trademark of Cambrian Systems Inc.
Nortel TN-4XE Alarm Clearing Procedures

ii
VT100 is a trademark of Digital Equipment Corporation.

Unix and the X device are trademarks of The Open Group
RS-232 is a trademark of the Electronic Industries Association
CNet is a trademark of CNet Technology Inc
Ethernet is a trademark of Xerox Corporation
323-1123-543 Release 3.01 Standard

iii
Publication history
March 2000
Release 3 Standard introduces the following TN-4XE features:
• Three channel, 34/45Mbit/s PDH electrical tributary card
• 1+1 card protection for 34/45Mbit/s and STM-1e/140Mbit/s tributaries
• Multiplex section protection for STM-1 tributary cards and STM-4
aggregate cards
July 1999
Release 2.2 Standard introduces the following TN-4XE features:
• SETS (synchronisation function) and SEMF (Shelf Controller function)
redundancy
• STM-1e/140 Mbit/s, single channel, tributary card
• Performance monitoring to G.826
• New connection types (unprotected PDH tributary to tributary, time slot
interchange on aggregate to aggregate)
February 1999
• Engineering Order Wire card
• STM-4o optical aggregate long haul 1550 nm
• Rack fan tray
December 1998
• Up to eight 2 Mbit/s PDH electrical tributary cards (75 ohm and 120 ohm)
each with 32 ports
• New connection types (tributary to tributary, ring to ring, dual tributary to
aggregate)
• Installation in 19 inch (482 mm) equipment rack

iv
June 1998
Release 1 Standard introduces the following TN-4XE features:
• SDH add drop multiplexer architecture
• STM-4o optical aggregate short haul 1310 nm
• Up to eight STM-1 optical tributaries short haul 1310 nm with two ports
• VC-12, VC-3 and VC-4 connectivity
• Sub-network connection protection and path protection
• Management from the EC-1 or CAT with HTML browser interface
end of chapter

v
Contents
About this document xi
Associated documents xi
Introduction 1-1
Maintenance philosophy 1-1
Alarm clearing 1-1
Response to action logs 1-2
Defect detection and alarm reporting 1-2
Card LEDs 1-2
Rack alarm unit (RAU) indications on the subrack 1-2
Correlation (fault masking) 1-3
Alarm severity and RAU category 1-4
Alarm severity states 1-6
RAU categories 1-6
Consequent actions and alarms 1-7
Clearing alarms 2-1

Alarm instances 2-10
OS-Optical Power High 2-11
OS-Laser Bias High 2-12
OS-Disabled Laser Shutdown 2-13
OS-Laser Shutdown 2-14
ES-Coded mark inversion violation 2-15
ES-Transmit Fail (TF) 2-16
ES-Code violation quality of service violation
(15 minute) 2-17
(24 hour) 2-18
RS-Unexpected signal 2-19
RS-Loss of Signal (LOS) 2-20
RS-Loss of Frame (LOF) 2-22
RS-Excessive errors (EXC) 2-24
RS-Trace Identifier Mismatch (TIM) 2-26
RS-Loopback On 2-28
RS-Quality of service violation (15 minute) 2-29
RS-Quality of service violation (24 hour) 2-30
MS-Alarm Indication Signal (AIS) 2-31
MS-Remote Defect Indicator (RDI) 2-33
MS-Remote Error Indicator (REI) 2-35
MS-Excessive errors (EXC) 2-37
MS-Signal Degrade (DEG) 2-39
MS-Quality of service violation (15 minute) 2-41

vi Contents
MS-Quality of service violation (24 hour) 2-42

MS-Far end quality of service violation (15 minute) 2-43
MS-Far end quality of service violation (24 hour) 2-44
AU-Alarm Indication Signal (AIS) 2-45
AU-Loss of Pointer (LOP) 2-47
HHP-Excessive errors (EXC) 2-48
HP-Signal Degrade (DEG) 2-50
HP-Trace Identifier Mismatch (TIM) 2-52
HP-Remote Defect Indicator (RDI) 2-54
HP-Loss of Multiframe (LOM) 2-56
HP-Remote Error Indicator (REI) 2-58
HP-Payload Label Mismatch (PLM) 2-59
HP-Unequipped (UNEQ) 2-61
HP-Signal Fail (SF) 2-63
INT-HP-Input Buffer Overflow 2-65
INT HP-Output Buffer Overflow 2-66
HP-Quality of service violation (15 minute) 2-67
HP-Quality of service violation (24 hour) 2-68
HP-Far end quality of service violation (15 minute) 2-69
HP-Far end quality of service violation (24 hour) 2-70
HPOM-Excessive errors (EXC) 2-71
HPOM-Trace Identifier Mismatch (TIM) 2-73
HPOM-Payload Label Mismatch (PLM) 2-75
HPOM-Unequipped (UNEQ) 2-77
TU-Alarm Indication Signal (AIS) 2-79
TU-Loss of Pointer (LOP) 2-80
INT-TU-Alarm Indication Signal (AIS) 2-81
TU INT-TU-Loss of Pointer (LOP) 2-82
LP LP-Excessive errors (EXC) 2-83
LP LP-Signal Degrade (DEG) 2-84
LP LP-Payload Label Mismatch (PLM) 2-86
LP LP-Remote Defect Indicator (RDI) 2-88
LP LP-Remote Error Indication (REI) 2-90
LP INT-LP-Input Buffer Overflow 2-91
LP INT LP-Output Buffer Overflow 2-93
LP LP-Signal Fail (SF) 2-95
LP LP-Trail Identifier Mismatch (TIM) 2-96
LP LP-Label Unequipped 2-98
LP LP-Quality of service violation (15 minute) 2-100
LP LP-Quality of service violation (24 hour) 2-101
LP LP-Far end quality of service violation (15 minute) 2-102
LP LP-Far end quality of service violation (24 hour) 2-103
LPOM LPOM-Excessive Errors (EXC) 2-104
LPOM LPOM-Trail Identifier Mismatch (TIM) 2-106
LPOM LPOM-Payload Label Mismatch (PLM) 2-108
LPOM LPOM-Label Unequipped (UNEQ) 2-110
PPI PPI-Transmit Fail (TF) 2-112
PPI PPI-Loss Of Signal (LOS) 2-114
PPI PPI-Alarm Indication Signal (AIS) 2-116
PPI PPI-Excessive errors (EXC) 2-117
PPI PPI-Signal Degrade (DEG) 2-118
PPI PPI-Unexpected Signal 2-119
PPI PPI-Loss of Frame (LOF) 2-120
PPI PPI-Loss of Multiframe (LOM) 2-121
PPI PPI-Loopback On 2-122
Release 3.01 Standard

Contents vii
PPI PPI- Transmit-Loss of Frame (T-LOF) 2-123

PPI PPI-Code violation Quality of service violation
(15 minute) 2-124
PPI PPI-Code violation-Quality of service violation
(24 hour) 2-125
SYNC Sync-SETG Fail 2-126
SYNC Sync-Unexpected signal 2-127
SYNC Sync-ESO Source Not Primary 2-128
SYNC Sync-Holdover 2-129
SYNC Sync-Source Not Primary 2-130
SYNC Sync-External Sync Loss Of Signal 2-131
SYNC Sync-SETG Frequency suspect 2-133
SYNC Sync-Source out of limits 2-134
SYNC Sync-Lock fail 2-135
Misc Qecc Comms Fail 2-136
Misc INT NE-Spi Comms Fail 2-139
Misc EA-Ext inp <1-8> 2-140
Misc INT NE-Configuration Corrupt 2-141
Misc NE-Lan Alarm 2-142
Misc NE-Unexpected LAN 2-143
Misc INT NE-Config bp mismatch 2-144
Misc Ps-power fail 2-145
Misc NE-Date time unknown 2-146
Misc Unexpected SW version 2-147
Misc Internal 1 second clock loss of signal 2-148
Card NE-Card Out 2-149
Card NE-Unexpected Card 2-151
Card NE-Card Fail 2-153
Card NE-Card Fault 2-154
Card NE-Wrong Card 2-155
Card NE-Invt Write Jumper Fitted 2-156
Card NE-Minor card mismatch 2-157
Config INT NE-Configuration Corrupt Bank 2-158
Config INT NE-Configuration All Banks Corrupt 2-159
Config INT NE-Configuration Available Bank Corrupt 2-160
Config INT NE-Configuration Software Mismatch 2-162
Config INT NE-Configuration Audit Mismatch 2-164
Config INT NE-Configuration Validation Error 2-165
Config INT NE-Standby Configuration Software Unstable 2-166
Config INT NE-Standby Configuration Flash Corrupt 2-167
Config INT NE-Standby Configuration audit mismatch 2-168
Config INT NE-Standby Configuration fail 2-169
Prot Equip_Fail 2-170
Prot Equip_Out 2-171
Prot Unexpected_Equip 2-172
Prot Cable_Error 2-173
Prot Wrong_Equip 2-174
MSP FOP_PAM 2-175
MSP FOP_SCM 2-176
MSP FOP_INV 2-177
MSP FOP_TMOUT 2-178
Index 3-1
Figures

viii Contents
Figure 1-1 RAU indicators on the Upper EOS card 1-3

Figure 1-2 Card Alarm Correlation hierarchy 1-4
Figure 1-3 Traffic and BER alarm correlation hierarchy 1-5
Figure 1-4 Hierarchy of alarm correlation for PDH traffic
Procedures
Procedure 2-1 Es-cmi-violation alarm clearing 2-15
Procedure 2-2 ES_TF alarm clearing 2-16
Procedure 2-3 Es_cv_qosv_15M alarm clearing 2-17
Procedure 2-4 ES-CV-QOSV-24H alarm clearing 2-18
Procedure 2-5 Rs-los alarm clearing 2-21
Procedure 2-6 Rs_lof alarm clearing 2-23
Procedure 2-7 Rs-exc alarm clearing 2-25
Procedure 2-8 Rs-tim alarm clearing 2-27
Procedure 2-9 Rs_qosv_15M alarm clearing 2-29
Procedure 2-10 Rs_qosv_24H alarm clearing 2-30
Procedure 2-11 MS-AIS alarm clearing 2-32
Procedure 2-12 MS-RDI alarm clearing 2-34
Procedure 2-13 MS-REI alarm clearing 2-36
Procedure 2-14 MS-EXC alarm clearing 2-38
Procedure 2-15 MS_DEG alarm clearing 2-40
Procedure 2-16 Ms_qosv_15M alarm clearing 2-41
Procedure 2-17 Ms_qosv_24H alarm clearing 2-42
Procedure 2-18 Ms_fe_qosv_15M alarm clearing 2-43
Procedure 2-19 Ms_fe_qosv_24H alarm clearing 2-44
Procedure 2-20 AU-AIS alarm clearing 2-46
Procedure 2-21 AU-LOP alarm clearing 2-47
Procedure 2-22 HP-EXC alarm clearing 2-49
Procedure 2-23 HP-DEG alarm clearing 2-51
Procedure 2-24 HP-TIM alarm clearing 2-53
Procedure 2-25 HP-RDI alarm clearing 2-55
Procedure 2-26 HP-LOM alarm clearing 2-57
Procedure 2-27 HP-REI alarm clearing 2-58
Procedure 2-28 HP-PLM alarm clearing 2-60
Procedure 2-29 HP-UNEQ alarm clearing 2-62
Procedure 2-30 HP-SF alarm clearing 2-64
Procedure 2-31 INT-HP-IP-BUFFER alarm clearing 2-65
Procedure 2-32 INT-HP-OP-BUFFER alarm clearing 2-66
Procedure 2-33 Hp_qosv_15M alarm clearing 2-67
Procedure 2-34 Hp_qosv_24H alarm clearing 2-68
Procedure 2-35 Hp_fe_qosv_15M alarm clearing 2-69
Procedure 2-36 Hp_fe_qosv_24H alarm clearing 2-70
Procedure 2-37 HPOM-EXC alarm clearing 2-72
Procedure 2-38 HPOM-TIM alarm clearing 2-74
Procedure 2-39 HPOM-PLM alarm clearing 2-76
Procedure 2-40 HPOM-UNEQ alarm clearing 2-78
Procedure 2-41 TU-AIS alarm clearing 2-79
Procedure 2-42 TU-LOP alarm clearing 2-80
Procedure 2-43 INT-TU-AIS alarm clearing 2-81
Procedure 2-44 INT-TU-LOP alarm clearing 2-82
Procedure 2-45 LP-EXC alarm clearing 2-83
Procedure 2-46 LP-DEG alarm clearing 2-85
Procedure 2-47 LP-PLM alarm clearing 2-87
Procedure 2-48 LP-RDI alarm clearing 2-89
Procedure 2-49 LP-REI alarm clearing 2-90
Release 3.01 Standard

Contents ix
Procedure 2-50 INT-LP-IP-BUFFER alarm clearing 2-92

Procedure 2-51 INT-LP-OP-BUFFER alarm clearing 2-94
Procedure 2-52 LP-SF alarm clearing 2-95
Procedure 2-53 LP-TIM alarm clearing 2-97
Procedure 2-54 LP-UNEQ alarm clearing 2-99
Procedure 2-55 Lp_qosv_15M alarm clearing 2-100
Procedure 2-56 Lp_qosv_24H alarm clearing 2-101
Procedure 2-57 Hp_fe_qosv_15M alarm clearing 2-102
Procedure 2-58 Lp_fe_qosv_24H alarm clearing 2-103
Procedure 2-59 LPOM-EXC alarm clearing 2-105
Procedure 2-60 LPOM-TIM alarm clearing 2-107
Procedure 2-61 LPOM-PLM alarm clearing 2-109
Procedure 2-62 LPOM-UNEQ alarm clearing 2-111
Procedure 2-63 PPI-TF alarm clearing 2-113
Procedure 2-64 PPI-LOS alarm clearing 2-115
Procedure 2-65 PPI-EXC alarm clearing 2-117
Procedure 2-66 PPI-DEG alarm clearing 2-118
Procedure 2-67 PPI-UNEXP_SIGNAL alarm clearing 2-119
Procedure 2-68 PPI-LOF alarm clearing 2-120
Procedure 2-69 PPI-LOM alarm clearing 2-121
Procedure 2-70 PPI-T-LOF alarm clearing 2-123
Procedure 2-71 PPI_CV_qosv_15M alarm clearing 2-124
Procedure 2-72 PPI_CV_qosv_24H alarm clearing 2-125
Procedure 2-73 SYNC-SETG_Fail alarm clearing 2-126
Procedure 2-74 SYNC-Ext_Sync_LOS alarm clearing 2-132
Procedure 2-75 SYNC-SETG_frequency_suspect alarm clearing 2-133
Procedure 2-76 SYNC-SOURCE-OUT-OF-LIMITS alarm clearing 2-134
Procedure 2-77 SYNC-LOCK-FAIL alarm clearing 2-135
Procedure 2-78 Qecc_Comms_Fail alarm clearing 2-137
Procedure 2-79 Spi-Comms_Fail alarm clearing 2-139
Procedure 2-80 NE-Card_Out alarm clearing 2-150
Procedure 2-81 NE-Unexpected_Card alarm clearing 2-152
Procedure 2-82 NE-Card_Fail alarm clearing 2-153
Procedure 2-83 NE-Wrong_Card alarm clearing 2-155
Procedure 2-84 INT-NE_Config_Corrupt_Bank 2-158
Procedure 2-85 INT-NE_Config_All_Banks_Corrupt 2-159
Procedure 2-86 INT NE-Config_Avail_Bank_Corrupt 2-161
Procedure 2-87 INT NE-Cfg_sw_mismatch 2-162
Procedure 2-88 INT NE-Cfg_Audit_Mismatch 2-164
Procedure 2-89 INT NE-Cfg_validation_error 2-165

xiii
About this document

This document contains procedures to locate and clear alarm indications on
the TN-4XE subrack.
Audience
This document is intended for use by the following people:
• field maintenance personnel
• maintenance engineers
• system test engineers
• network administrators
Associated documents
The following documents are referred to in this document:
• Documentation overview and safety, 323-1123-090
• System Description, 323-1123-100
• Software and Hardware Description, 323-1123-101
• Installation Procedures, 323-1123-201
• Provisioning and Operations Procedures, 323-1123-310
• Network Surveillance Procedures, 323-1123-510
• Maintenance Procedures, 323-1123-547
• EC-1 User Procedures, 323-1091-402

xiv
Technical support and information

So far as Nortel Networks is aware the information in this document is
correct. If, however, you discover any errors or have comments regarding the
presentation of the content, please send details by email to:
IONNTPS@nortelnetworks.com
Nortel Networks provides a comprehensive technical support service for it’s

customers. The Nortel Networks Service Desk may be contacted between the
hours of 08:30 and 17:00, Monday to Friday (UK local time), using the
following FAX or telephone numbers:
United Kingdom
Freephone: 0800 626 881
Telephone: 0208 361 4693
FAX: 0208 945 3456
International
Telephone: +44 208 361 4693
FAX: +44 208 945 3456
EMC conformance
This product/product family complies with the essential
protection requirements of the EMC Directive 89/336/EEC as
amended by 92/31/EEC, when it is properly installed and
maintained and when it is used for the purposes for which it is
intended.

Code: EDEU0001
Issue: 2
Template: v5;970307
Declaration of Conformity
Suppliers Name & Address: Nortel Networks, of Doagh Road, Newtownabbey,
County Antrim, Northern Ireland, BT36 6XA
We hereby declare that the products identified in Section 1 comply with the standards listed in
Section 2 and fulfil our obligations under the EU Directives listed in Section 3.
Section 1 - Products Covered
Product Name Product Type

TN-4XE STM4 Add Drop SDH Multiplexer system;
permissable configurations which use TN-4XE
subrack assembly (NTEU70AA) and TN-4XE fan
tray assembly (NTEU55AA) (optional)
Section 2 - Standards Applied

The Product described above is in conformity with the following standards:
Stds Standard Number Edition Amendments Subject of Standard

Ref
1 EN 55022 1995 Emissions from IT Equipment
1 EN 50082-1 1992 Generic Immunity
2 EN 60950 1992 1,2,3 & 4 Safety of IT equipment
2 EN 60825-1 1994 1 Safety of Laser Products
Section 3 - European Union Directives
Directive Abbreviated Directive Title Stds CE Marking

Number Ref Information
(if applicable)
89/336/EEC EMC Directive 1 n/a
92/31/EEC Amendment to EMC Directive n/a n/a
93/68/EEC CE Marking Amending Directive n/a n/a
Section 4 - Authority of Issuer
Declaration Issued By: Peter Schuddeboom John Freebairn
Position of Issuer: VP, ION Product Development Senior Manager, Customer

Satisfaction & Quality
Signed: ________________
Date: ________________
The instructions for installation, use and maintenance form part of the product compliance and
must be observed.
This declaration has been made in accordance with ISO/IEC Guide 22, General criteria for suppliers' declaration of conformity
1
1-1
Introduction 1-
Maintenance philosophy
This section describes the maintenance method for locating and clearing
alarm indications.
The maintenance philosophy is to identify the source of a fault without the

need for difficult on-site maintenance. At all times, the maintenance
procedures try to prevent interrupting traffic.
Procedures to locate faults use all the indications and techniques provided by
the TN-4XE and the Element Controller (EC-1) or CAT. TN-4XE has failure
indicator lamps on the hardware and also has alarm or action log reports on
the user interface.
Alarms and action logs descriptions are in the System Description,

323-1123-100.
Alarm clearing
To locate and clear a fault in a TN-4XE continue as follows:
1 Use the EC to open the Alarm Monitor tool. View the active alarm
summaries in the EC’s span of control (see Element Controller, User
Procedures, 323-1091-402). From the active alarm list, identify the NE on
which the highest severity alarm has occurred.
2 Log in to the NE and clear the alarms one channel and one direction at a
time, starting with the highest-severity alarm. If required, send a person to
the NE site to do maintenance procedures and card replacement.
3 Refer to Chapter 2 for detailed step-by-step procedures for clearing
alarms.
WARNING
Safety guidelines
Refer to safety information in Documentation Overview and
Safety, 323-1123-090.

1-2 Introduction
CAUTION
Risk of traffic interruption
The TN-4XE Network Element is a high capacity system. Be
careful not to interrupt traffic or perform any task without a
valid reason. Where possible reroute the traffic through another
path before replacing any traffic-carrying circuit pack.
Response to action logs

TN-4XE action logs are information messages that the Network Element or
the EC generate for a span of control that includes the TN-4XE NE.
Often, log messages require no action by the maintenance personnel.

However, some logs provide additional information for identified alarms or
trouble conditions.
The Network Surveillance Procedures, 323-1123-510 lists and describes logs

in detail.
Defect detection and alarm reporting

The TN-4XE subrack provides local alarm indications to aid identifying the
source of a problem.
Card LEDs
All cards have several light-emitting diodes (LEDs) on the faceplates as an
aid to fault finding. Card LED descriptions are in the Software and Hardware
Description, 323-1123-101.
Traffic cards LEDs

The LEDs on the traffic cards are:
• the Fail LED (red) indicates a card fail, power fail or watchdog timer fail
• the Active LED (green) indicates that the card is in service. Do not remove
the card while this LED is on.
• the LOS LED (yellow) indicates a loss of signal
EOS cards LEDs

The two colour Fail LED on the EOS cards indicates:
• red, a firmware, LAN or low voltage failure has occurred
• yellow, a fail on the -48V supply has occurred
Rack alarm unit (RAU) indications on the subrack

The UEOS card includes two visual alarm indicators and a push button switch
related to the RAU. The ‘Alarm’ indicator is on when any of the RAU
indicators Prompt, Deferred maintenance or In-Station are active. When you
operate the ‘Receive Attention’ switch the ‘Alarm’ indicator goes off and the
‘Alarm acknowledge’ indicator comes on.

Introduction 1-3
Figure 1-1
RAU indicators on the Upper EOS card
1
FAIL
ACK ALARM
ALARM RAU indicators
REC ATT
NPUT
Correlation (fault masking)

When the TN-4XE alarm handling hardware and software detects a fault,
often the multiplexer reports more than one alarm. Many of these alarms can
be related but vary in severity levels. Alarm correlation reduces the quantity
of alarms shown to the operator because the multiplexer only displays the
alarm nearest to the fault source.
Each alarm in the correlation process has a position in a correlation hierarchy

which defines the masking relationship between alarms. An alarm raised at
any point in the hierarchy blocks reporting of alarms which are lower in the
hierarchy.
Also, if a defect occurs, the multiplexer can report a low severity alarm before
a higher severity alarm. To make sure operators view only higher severity
alarm reports, the software applies a fault masking check period before
reporting the alarm.
Card alarm correlation

For any given card, several equipment or card alarms can mask another alarm
raised within that card or slot instance (see Figure 1-2). These card alarms can
mask traffic alarms raised against other cards depending on the connections
set up at the multiplexer.

1-4 Introduction
Figure 1-2
Card Alarm Correlation hierarchy
Equipment Alarms Card Alarms
Card Fault Card Fail Wrong Card Unexpected Card
Any alarm raised on the Card/Slot instance
Traffic and BER alarms correlation

All Traffic and BER class alarms are subject to correlation so that, generally,
the multiplexer generates one alarm report per alarm condition. Note that
traffic alarm fault masking operates within each payload instance. Traffic
alarms can mask other traffic alarms when raised against the same payload
instance. Figure 1-3 shows the cause and effect relationship which determines
the correlation hierarchy for traffic and BER alarms.
Alarm severity and RAU category

Each alarm has a severity level and related Rack Alarm Unit (RAU) category.
The multiplexer classifies alarm severity as Critical alarm, Major alarm or
Minor alarm according to the degree of their effect (or potential effect). The
RAU category defines how the external rack alarm unit processes each alarm.
The operator can change the RAU category for each alarm. If the operator
changes the RAU category for an alarm the alarm severity also changes
automatically.

Introduction 1-5
Figure 1-3
Traffic and BER alarm correlation hierarchy
1
RS LOS RS UNEXP SGNL
ES CMI
RS LOF
RS TIM MS RDI RS COMMS FAIL MS COMMS FAIL
MS AIS
MS REI
MS EXC
MS DEG AU LOP FOP_PAM FOP_SCM FOP_INV
AU AIS
HPOM EXC
HPOM TIM HPOM PLM HPOM UNEQ HP-EXC
INT HP OP BUFF HP RDI HP LOM HP TIM HP PLM HP UNEQ HP DEG
PPI LOF-T HP REI TU LOP
TU AIS
INT TU LOP LPOM EXC
INT TU AIS LPOM TIM LPOM PLM LPOM UNEQ
LP EXC
LP RDI INT LP OP BUFF LP TIM LP PLM LP UNEQ LP DEG
LP-REI
= Consequent Action configuration dependent

= Masked if TU type is TU-1

1-6 Introduction
Figure 1-4
Hierarchy of alarm correlation for PDH traffic
PPI LOS PPI UNEXP SGNL
PPI EXC
PPI DEG PPI AIS INT LP IP BUFF INT HP IP BUFF
PPI LOF
PPI LOM
Alarm severity states

The following list details the different alarm severity states:
• Critical alarm- a failure which disables or decreases the quality of services
provided by the network. Optical line failures and service-carrying card
failures are examples of critical alarms.
• Major alarm- a failure which decreases the quality of services provided by
the network, but not to the same degree as a Critical failure. RS-TIM is an
example of a major alarm.
• Minor alarm- a failure in the network or a failure which does not decrease
the quality of service provided by the network. AIS and protected card
failures are examples of minor alarms.
• Warning alarm- shown by the CAT or Element Controller but does not
provide card, subrack, or rack alarm indications or extensions. A warning
alarm indicates a condition exists that requires action.
RAU categories
Each alarm severity (except warning) matches a rack alarm unit category:
• Prompt maintenance alarm (Critical alarm) - an alarm that requires
immediate action at all times. Generally, this alarm passes to a
maintenance/control point when the station is without an operator.
• Deferred maintenance alarm (Major alarm) - an alarm that does not require
immediate action outside normal hours. Generally, this alarm passes to a
maintenance/control point when the station is without an operator.
• In Station maintenance alarm (Minor alarm) - an alarm that does not
require action outside normal hours.

Introduction 1-7
Consequent actions and alarms 1

Consequent actions are events which occur as a result of a traffic or BER
alarm to indicate the condition of the received signal. There are three main
consequent actions:
• AIS indication (internal to the multiplexer)
• Remote defect indication (RDI) or remote error indication (REI) inserted
on the return path overhead
• an SNC-P or path protection switch
The operator can configure consequent actions on or off for the complete NE
or for each alarm type. For a consequent action to be enabled all the following
conditions must be true:
• the feature is enabled (for example Path Trace)
• alarm reports are set to On or Monitor
• the consequent actions are enabled for the NE
• the consequent action is enabled for the alarm type
Refer to Provisioning and Operations Procedures, NTP 323-1123-310 for the

procedures to configure consequent actions.
Details of the consequent actions for each alarm are in Chapter 2.

end of chapter

2-1
2
Clearing alarms 2-
This chapter describes how to locate and clear alarms on the TN-4XE
subrack.
To locate and clear a specific alarm, refer to the following procedures.
Optical system alarms
Alarm Displayed as Page
OS-Optical Power High Os_optical_power_high 2-11
OS-Laser Bias High Os_laser_bias_high 2-12
OS-Disabled Laser Shutdown Os_dis_laser shutdown 2-13
OS-Laser Shutdown Os_laser_shutdown 2-14
Electrical section alarms
es-coded mark inversion violation es_cmi_violation 2-15
es-transmit fail es_tf 2-16
es-code violation-quality of service es_cv_qosv_15M 2-17

violation 15 minute
es-code violation-quality of service es_cv_qosv_24H 2-18

violation 24 hour

2-2 Clearing alarms
Regenerator section alarms
RS-Unexpected signal Rs_unexp_signal 2-19
RS-Loss of Signal (LOS) Rs_los 2-20
RS-Loss of Frame (LOF) Rs_lof 2-22
RS-Excessive errors (EXC) Rs_exc 2-24
RS-Trace Identifier Mismatch (TIM) Rs_tim 2-26
RS-Loopback On Rs_loopback_on 2-28
RS-quality of service violation 15 minute RS_qosv_15M 2-29
RS-quality of service violation 24 hour RS_qosv_24H 2-30
Multiplexer section alarms
MS-Alarm Indication Signal (AIS) Ms_ais 2-31
MS-Remote Defect Indicator (RDI) Ms_rdi 2-33
MS-Remote Error Indicator (REI) Ms_rei 2-35
MS-Excessive errors (EXC) Ms_exc 2-37
MS-Signal Degrade (DEG) Ms_deg 2-39
MS-quality of service violation 15 minute Ms_qosv_15M 2-41
MS-quality of service violation 24 hour Ms_qosv_24H 2-42
MS-far end quality of service violation 15 Ms_fe_qosv_15M 2-43

minute
MS-far end quality of service violation 24 Ms_fe_qosv_24H 2-44

hour
Administrative Unit alarms
AU-Alarm Indication Signal (AIS) Au_ais 2-45
AU-Loss of Pointer (LOP) Au_lop 2-47

Clearing alarms 2-3
Higher order path alarms
HP-Excessive errors (EXC) Hp_exc 2-48

2
HP-Signal Degrade (DEG) Hp_deg 2-50
HP-Trace Identifier Mismatch (TIM) Hp_tim 2-52
HP-Remote Defect Indicator (RDI) Hp_rdi 2-54
HP-Loss of Multiframe (LOM) Hp_lom 2-56
HP-Remote Error Indicator (REI) Hp_rei 2-58
HP-Payload Label Mismatch (PLM) Hp_plm 2-59
HP-Unequipped (UNEQ) Hp_uneq 2-61
HP-Signal Fail (SF) Hp_sf 2-63
Internal high order input buffer overflow Int_hp_ip_buffer 2-65
Internal high order output buffer overflow Int_hp_op_buffer 2-66
HP-quality of service violation 15 minute Hp_qosv_15M 2-67
HP-quality of service violation 24 hour Hp_qosv_24H 2-68
HP-far end quality of service violation 15 Hp_ fe_qosv_15M 2-69

minute
HP-far end quality of service violation 24 Hp_fe_qosv_24H 2-70

hour
Higher order path alarms with overhead monitoring
HPOM-Excessive errors (EXC) Hpom_exc 2-71
HPOM-Trail Identifier Mismatch (TIM) Hpom_tim 2-73
HPOM-Payload Label Mismatch (PLM) Hpom_plm 2-75
HPOM-Unequipped (UNEQ) Hpom_uneq 2-77

2-4 Clearing alarms
Transport unit alarms
TU-Alarm Indication Signal (AIS) Tu_ais 2-71
TU-Loss of Pointer (LOP) Tu_lop 2-79
INT-TU-Alarm Indication Signal (AIS) Int_tu_ais 2-81
INT-TU-Loss of Pointer (LOP) Int_tu_lop 2-82
Low order path alarms
LP-Excessive errors (EXC) Lp_exc 2-83
LP-Signal Degrade (DEG) Lp_deg 2-84
LP-Payload Label Mismatch (PLM) Lp_plm 2-86
LP-Remote Defect Indicator (RDI) Lp_rdi 2-88
LP-Remote Error Indication (REI) Lp_rei 2-90
INT-LP-Input Buffer Overflow Lp_lp_buffer 2-91
INT LP-Output Buffer Overflow Lp_op_buffer 2-93
LP-Signal Fail (SF) Lp_sf 2-95
LP-Trail Identifier Mismatch (TIM) Lp_tim 2-96
LP-Label Unequipped Lp_uneq 2-98
LP-quality of service violation 15 minute Lp_qosv_15M 2-100
LP-quality of service violation 24 hour Lp_qosv_24H 2-101
LP-far end quality of service violation 15 Lp_fe_qosv_15M 2-102

minute
LP-far end quality of service violation 24 Lp_fe_qosv_24H 2-103

hour
Low order path alarms with overhead monitoring
LPOM-Excessive Errors (EXC) Lpom_exc 2-104

Clearing alarms 2-5
LPOM-Trail Identifier Mismatch (TIM) Lpom_tim 2-106
LPOM-Payload Label Mismatch (PLM) Lpom_plm 2-108
LPOM-Unequipped (UNEQ) Lpom_uneq 2-110

2
PDH physical interface alarms
PPI-Transmit Fail (TF) Ppi_tf 2-112
PPI-Loss Of Signal (LOS) Ppi_los 2-114
PPI-Alarm Indication Signal (AIS) Ppi_ais 2-116
PPI-Excessive errors (EXC) Ppi_exc 2-117
PPI-Signal Degrade (DEG) Ppi_deg 2-118
PPI-Unexpected Signal Ppi_unexp_signal 2-119
PPI-Loss of Frame (LOF) Ppi_lof 2-120
PPI-Loss of Multiframe (LOM) Ppi_lom 2-121
PPI-Loopback On Ppi_loopback_on 2-122
PPI-Loss of Frame - transmit (T-LOF) Ppi_T_lof 2-123
PPI-code violation-quality of service Ppi_cv_qosv_15M 2-124

violation 15 minute
PPI-code violation-quality of service Ppi_cv_qosv_24H 2-125

violation 24 hour

2-6 Clearing alarms
Synchronization alarms
Sync-SETG Fail Sync_setg_fail 2-126
Sync-Unexpected signal Sync_unexp_signal 2-127
Sync-ESO Source Not Primary Sync_eso_src_not_primary 2-128
Sync-Holdover Sync_holdover 2-129
Sync-Source Not Primary Sync_src_not_primary 2-130
Sync-External Sync Loss Of Signal Sync_ext_sync_los 2-131
Sync-SETG Frequency suspect Sync_frequency_suspect 2-133
Sync-Source out of limits Sync_source_out _of_limits 2-134
Sync-Lock fail Sync_lock_fail 2-135

Clearing alarms 2-7
Miscellaneous alarms
Qecc Comms Fail Qecc_comms_fail 2-136

2
Misc INT NE-Spi Comms Fail Int_ne_spi_comms_fail 2-139
Misc EA-Ext inp <1-8> Ea_ext_inp 2-140
Misc INT NE-Configuration Corrupt Int_ne_config_corrupt 2-141
Misc NE-Lan Alarm Ne_lan_alarm 2-142
Misc NE-Unexpected LAN Ne_unexpected_lan 2-143
Misc INT NE-Config bp mismatch Int_ne_config_bp_mismatch 2-144
Misc Ps-power fail Ps_power_fail 2-145
Misc NE-Date time unknown Ne_date_time_unknown 2-146
Misc Unexpected SW version Unexp_sw_version 2-147
Misc Internal 1 second clock loss of Int_ne_1s_clk_los 2-148

signal
Card alarms
Card NE-Card Out Ne_card_out 2-149
Card NE-Unexpected Card Ne_unexpected_card 2-151
Card NE-Card Fail Ne_card_fail 2-153
Card NE-Card Fault Ne_card_fault 2-154
Card NE-Wrong Card Ne_wrong_card 2-155
Card NE-Invt Write Jumper Fitted Ne_invt_wri_jumper_fitted 2-156
Card NE-Minor card mismatch Ne_minor_card_mismatch 2-157

2-8 Clearing alarms
Configuration alarms
Config INT NE-Configuration Corrupt Int_ne_cfg_corrupt_bank 2-158

Bank
Config INT NE-Configuration All Banks Int_ne_cfg_all_banks_corrupt 2-159

Corrupt
Config INT NE-Configuration Available Int_ne_cfg_avail_bank_corrupt 2-160

Bank Corrupt
Config INT NE-Configuration Software Int_ne_cfg_sw_mismatch 2-162

Mismatch
Config INT NE-Configuration Audit Int_ne_cfg_audit_mismatch 2-164

Mismatch
Config INT NE-Configuration Validation Int_ne_cfg_validation_error 2-165

Error
Config INT NE-Standby Configuration Int_ne_stdby_cfg_sw_unstab 2-166

Software Unstable
Config INT NE-Standby Configuration Int_ne_stdby_flash_crpt 2-167

Flash Corrupt
Config INT NE-Standby Configuration Int_ne_stdby_Cfg_Audit_Mism 2-168

Audit Mismatch atch
Config INT NE-Standby Configuration Int_ne_stdby_cfg_fail 2-169

fail

Clearing alarms 2-9
1+1 Card Protection alarms
Equipment fail Equip_Fail 2-170

2
Equipment Out Equip_Out 2-171
Unexpected Equipped Unexpected_Equip 2-172
Cable error Cable_Error 2-173
Wrong equipment Wrong_Equip 2-174
Multiplex section protection alarms
Protection scheme mismatch FOP_PAM 2-175
Channel mismatch FOP_SCM 2-176
Invalid K bytes (Invalid command) FOP_INV 2-177
Invalid K bytes (timeout) FOP_TMOUT 2-178

2-10 Clearing alarms
Alarm instances
The following table details the alarm instances that are valid for each card
type in a TN-4XE.
Table 2-1
Possible alarm instances
Card <Slot-no> <Port> J<VC-4> <KLM>
aggregate 6,8 1 1 to 4 111 to 373
STM-1o tributary 1 to 4, 11 to 14 1 or 2 1 111 to 373
STM-1e/140 Mbit/s 1 to 4, 11 to 14 1 1 111 to 373

tributary (STM-1e mode)
STM-1e/140 Mbit/s 1 to 4, 11 to 14 1 - -
tributary (140 Mbit/s mode)
STM-1e/140 Mbit/s I/O 2, 5, 10, 11, 1 - -

card 12
34/45 Mbit/s tributary 1 to 4, 11 to 14 1 to 3 - -

(34 Mbit/s mode)
34/45 Mbit/s tributary 1 to 4, 11 to 14 1 to 3 - -

(45 Mbit/s mode)
34/45 Mbit/s I/O card 2, 5, 10, 11, 1 - -

12
2 Mbit/s tributary 1 to 4, 11 to 14 1 to 32 - -
UEOS 15A 1 - -
LEOS (LAN) 15B 1 or 2 - -
LEOS (Synchronization) 15B 1 - -

Clearing alarms 2-11
OS
OS-Optical Power High
Significance
The laser or its related control loop has failed. As a result the optical power
2
output exceeds the nominal limit by +4dB or greater (i.e. Optical Power
High).
Note: This alarm also provides a hardwired Metallic Alarm signal to the
RAU. The alarm does not respond to the Receive Attention button on the
UEOS card.
Instance/Unit
The multiplexer raises this alarm on an optical port instance, reported as
S <slot-no> - <port-no>
For details of valid arguments see Table 2-1 on page 2-10
Impact
Critical alarm
Traffic hit on unprotected paths.

Protection switch on protected paths.
Consequent action
The laser is shutdown. This is a safety feature, although the laser output is still
within the standard safe range.
Note: The laser shutdown is latched, the laser will remain off until the
card is reseated or a cold restart is performed.
Resulting alarms
None
Possible causes
Faulty aggregate card or STM-1o tributary card.
Corrective actions
Re-seat the indicated card.
Switch off and restore power to the multiplexer.
If the alarm is still present replace the card. Refer to the Maintenance
Procedures, 323-1123-547.

OS
OS-Laser Bias High
Significance
The laser bias current exceeds the nominal limits. This indicates that the laser
performance has degraded and that the laser is nearing it’s end-of-life.
Instance/Unit
This alarm is raised against an optical port instance, reported as
Impact
Critical alarm
Traffic on unprotected paths is affected.

Temporary traffic hit on protected paths.
Consequent action
None.
Possible causes
Ageing of the laser on the indicated optical port.
Corrective actions
Replace the indicated aggregate card or STM-1 tributary card. Refer to the
Maintenance Procedures, 323-1123-547.

OS
OS-Disabled Laser Shutdown
Significance
The automatic laser shutdown (ALS) function is disabled on the indicated
2
optical port.
Note: This alarm is raised against an optical port; however, the ALS
function is enabled or disabled on a card basis.
Instance/Unit
Impact
Minor alarm.
Does not affect traffic.
Consequent action
Automatic laser shutdown will not operate on the indicated port.
Possible causes
The automatic laser shutdown (ALS) function has been disabled.
Corrective actions
This alarm is only cleared when ALS is enabled. ALS is enabled by removing
a plug-in link on the appropriate card. Refer to the Software and Hardware
Description, 323-1123-101 for the position of the links on the cards.

OS
OS-Laser Shutdown
Significance
This alarm is raised when the laser on the specified optical port is shutdown
by the automatic laser shutdown (ALS) circuit.
Instance/Unit
Impact
Critical alarm
Traffic is affected on unprotected paths.

Consequent action
None.
Possible causes
Possible causes for the OS-Laser shutdown alarm are:
• RS_LOS alarm.
• Faulty aggregate or STM-1o tributary.
Corrective actions
If the RS_LOS alarm is present, perform the alarm clearing procedures for
that alarm.
If the RS_LOS alarm is not present, replace the indicated aggregate or

STM-1o tributary. Refer to the Maintenance Procedures, 323-1123-547.

ES
ES-Coded mark inversion violation
Significance
The Es_cmi_violation alarm is raised when CMI violations exceed the
2
threshold in an STM-1e signal.
Instance/Unit
This alarm is raised against a port instance, reported as
Impact
Critical alarm

Consequent action
If this port is the synchronization source for the multiplexer then a
synchronization switch occurs. If the port is in the synchronization source
hierarchy list, then the port is marked not available for synchronization.
Possible causes
Possible causes for the Es_cmi_violation alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty STM-1e/140 Mbit/s tributary card.
Corrective actions
Procedure 2-1
Es-cmi-violation alarm clearing
Step Action
1 Investigate preceding STM-1e equipment and cable for cause of errors.

If errors are intermittent, most likely cause is cabling and the connectors.
If no errors from preceding equipment, go to step 2.
2 Replace the indicated STM-1e/140 Mbit/s tributary card. Refer to the
Equipment Maintenance Procedures, 323-1123-547 for details.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem or replace subrack.
—end—

ES
ES-Transmit Fail (TF)
Significance
The STM-1e tributary output signal has fallen below a predefined threshold.
Instance/Unit
Impact
Critical Alarm
Loss of STM-1e traffic output
Consequent action
None.
Possible causes
Possible causes for the ES-TF alarm are:
• Cable fault.
Corrective actions
Procedure 2-2
ES_TF alarm clearing
Step Action
1 Ensure that the STM-1e traffic output cable is properly terminated.

Re-terminate the connector if required.
If the alarm clears, the alarm clearing procedure is complete.If the alarm is
still present, go to step 2.
2 Check the far end equipment and cable for a short circuit.
If the alarm clears, the alarm clearing procedure is complete. If the alarm is
3 Replace the indicated STM-1e/140 Mbit/s tributary card. Refer to the
Equipment Maintenance Procedures, 323-1123-547, for replacement
procedures.
If the alarm is still present, escalate problem or replace subrack.
—end—

ES
(15 minute)
2
Significance
The Es_cv_qosv_15M alarm is raised to indicate that any BBE, ES, SES,
UAS active performance monitoring threshold has been broken within a 15
minute monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the The Es_cv_qosv_15M alarm are:
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-3
Es_cv_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs-los alarm. Identify and remove the cause of
this alarm.
2 Check for the presence of the Es_cmi_violation alarm. Identify and remove
the cause of this alarm.
3 The Es_cv_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—

ES
(24 hour)
Significance
The Es_cv_qosv_24H alarm is raised to indicate that any BBE, ES, SES,
hour monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Es_cv_qosv_24H alarm are:
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period. The following procedure describes how to detect the cause of the
alarm.
Procedure 2-4
ES-CV-QOSV-24H alarm clearing
Step Action
1 Check for the presence of the Rs_los alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the Es_cmi_violation alarm. Identify and remove
the cause of this alarm.
3 The Es_cv_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—

RS
RS-Unexpected signal
Significance
Indicates that an optical signal is present at a specified port, but the port has
2
not been configured to receive the connection.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Incorrect configuration of connections.
Corrective actions
Configure the STM1 port as detailed in Provisioning and Operations

RS
RS-Loss of Signal (LOS)
Significance
The indicated card detects the loss of the received signal.
Instance/Unit
Impact
Critical alarm

Consequent action
AIS is injected on the MS overhead of the transmitted path.
On optical cards, the laser is shut down by the ALS circuit (if ALS is
enabled).
If this port is used as the synchronization source a synchronization switch

occurs. If entered in the synchronization source hierarchy list, this port will be
marked unavailable for synchronization.
Resulting alarm
OS_laser_shutdown, Ms_ais alarms.
Possible causes
Possible causes for the Rs-los alarm are:
• Faulty optical fibre or cable.
• Faulty local aggregate, STM-1o tributary or STM-1e tributary.
• Faulty far end aggregate, STM-1o tributary or STM-1e tributary.

Corrective actions
Procedure 2-5
Rs-los alarm clearing
Step Action 2
1 Perform a ‘Local’ loopback on the indicated port (see Network Surveillance
Procedures, 323-1123-510).
If the alarm is still present, remove the loopback and go to step 2.
If the alarm clears, remove the loopback and go to step 4.
2 Replace the local STM-N card. Refer to the Maintenance Procedures,
323-1123-547.
3 If the far end port provides the current synchronization source, switch to an
alternative source.
4 Perform a ‘Local’ loopback on the appropriate far end port (see Network
Surveillance Procedures, 323-1123-510).
If a Rs_los alarm is present at the far multiplexer, remove the ‘Local’ loopback
and go to step 5.
If a Rs_los alarm is not present at the far multiplexer, remove the ‘Local’
loopback and go to step 6.
5 Replace the far end STM-N card. Refer to the Maintenance Procedures,
323-1123-547.
6 On optical cards, clean the receive optical connections at the local aggregate
or STM-1o tributary and verify that the received optical power is in the correct
range. Refer to Maintenance Procedures, 323-1123-547.
If the received optical power is not within range, go to step 7.
7 On optical cards, clean the transmit optical connections at the far aggregate
or STM-1o tributary and verify that the transmit optical power at the far
aggregate or STM-1o tributary is in the correct range. Refer to Maintenance
If the transmit optical power is not within range, go to step 5.
If the transmit optical power is within range, the fault is associated with the
optical fibre. Use appropriate methods to isolate and repair a fibre fault.
—end—

RS
RS-Loss of Frame (LOF)
Significance
The frame alignment algorithm detects loss of frame alignment (loss of
framing pattern in the A1 and A2 bytes of the section overhead for three
consecutive frames).
Instance/Unit
Impact
Critical alarm

Consequent action
AIS is injected on the MS overhead of the transmitted path.
If entered in the synchronization source hierarchy list, this port will be

Resulting alarms
Ms_ais alarm.
Possible causes
Possible causes for the Rs_lof alarm are:
• Faulty optical fibre or cable.

Corrective actions
Procedure 2-6
Rs_lof alarm clearing
Step Action 2
1 If the indicated STM-4o,STM-1o or STM-1e port provides the current
synchronization source, switch to an alternative synchronization source.
2 Perform a loopback on the ‘Local’ card (see Network Surveillance
Procedures, 323-1123-510).
Replace the local card. Refer to the Maintenance Procedures, 323-1123-547.
3 Perform a ‘Local’ loopback on the appropriate far end card (see Network
If a Rs_lof alarm is present at the far multiplexer, remove the ‘Local’ loopback
and go to step 5.
If a Rs_lof alarm is not present at the far multiplexer, remove the ‘Local’
alternative source.
5 Replace the far end card. Refer to the Maintenance Procedures,
323-1123-547.
—end—

RS
RS-Excessive errors (EXC)
Significance
The error rate of the BIP-8 error check (B1 overhead byte) exceeds the
configured threshold.
Instance/Unit
Impact
Critical alarm

Consequent action
AIS is injected on the MS overhead of the transmitted path
(the consequent action is configurable - default to off).
If entered in the synchronization source hierarchy list, this port will be

Possible causes
Possible causes for the RS-EXC alarm are:
• Faulty optical fibre or connections.
• Faulty local aggregate or STM-1o tributary.
• Faulty far end aggregate or STM-1o tributary.

Corrective actions
Procedure 2-7
Rs-exc alarm clearing
Step Action 2
1 If the indicated port provides the current synchronization source, switch to an
alternative source.
2 Perform a ‘Local’ loopback on the local card (see Network Surveillance
Procedures, 323-1123-510).
3 Replace the local card. Refer to the Maintenance Procedures, 323-1123-547.
alternative source.
If a Rs_exc alarm is present at the far multiplexer, remove the ‘Local’ loopback
and go to step 6.
If a Rs_exc alarm is not present at the far multiplexer, remove the ‘Local’
6 Replace the far end card. Refer to the Maintenance Procedures,
323-1123-547.
—end—

RS
RS-Trace Identifier Mismatch (TIM)
Significance
This alarm indicates that the received STM path trace string in the J0 byte of
the RS overhead does not match the expected string. The alarm is not raised
until four successive occurrences of the string mismatch.
Instance/Unit
Impact
Major alarm
Consequent action
The received STM signal is set to AIS before further processing
(the consequent action is configurable - the default is off).
Resulting alarm
MS_AIS if the consequent action is on.
Possible causes
Possible causes for the Rs-tim alarm are:
• Incorrect connection setup.
• Path trace settings incorrect (i.e. receive string or far end transmit string).
• Cyclic redundancy check (CRC) settings incorrect.
• Faulty aggregate, STM-1o tributary or STM-1e tributary.
• If intermittent or transient events, errors in signal.

Corrective actions
Procedure 2-8
Rs-tim alarm clearing
Step Action 2
1 Check that the correct connections have been made.
If the connections are incorrect, reconnect as required.
If the connections are correct, go to step 2.
2 Check the system path trace and CRC settings at both ends.
To view, and if necessary correct, the settings refer to the Provisioning and
Operations Procedures, 323-1123-310.
If settings are correct, go to step 3.
3 At the local multiplexer, replace the appropriate aggregate or tributary card.
Refer to the Maintenance Procedures, 323-1123-547.
If the alarm is still present, go to step 4.
4 At the far multiplexer, replace the appropriate aggregate or tributary card.
Refer to the Maintenance Procedures, 323-1123-547.
—end—

RS
RS-Loopback On
Significance
This alarm indicates that an internal local or remote loopback is present at the
indicated port.
Instance/Unit
Impact
Minor alarm.
Consequent action
None.
Possible causes
The operator has applied a local or remote loopback at the indicated port.
Corrective actions
If required, remove the loopback as detailed in Network Surveillance

RS
RS-Quality of service violation (15 minute)
Significance
The Rs_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAS
2
active performance monitoring threshold has been broken within a 15 minute
monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Rs_qosv_15M alarm are:
• Excessive attenuation in cable or optical fibre.
• Faulty traffic card.
Corrective actions
Procedure 2-9
Rs_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los or Rs_lof alarm. Identify and remove the
cause of this alarm.
2 Check for the presence of B1 bit errors. Identify and remove the cause of
these errors.
3 The Rs_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—

RS
RS-Quality of service violation (24 hour)
Significance
The Rs_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAS
active performance monitoring threshold has been broken within a 24 hour
monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Rs_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-10
Rs_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Rs_los or Rs_lof alarm. Identify and remove the
cause of this alarm.
these errors.
3 The Rs_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—

MS
MS-Alarm Indication Signal (AIS)
Significance
An AIS is detected in the K2 byte in the multiplex section overhead which
2
indicates a failure at the far multiplexer. The alarm is raised when there are
three successive occurrences of AIS.
Instance/Unit
Impact
Minor alarm.
Temporary traffic hit on protected paths during switch.
Consequent action
AIS is inserted on the MS overhead K2 byte of the on-going path. RDI is
inserted in the overhead of the return path.
Resulting alarm
MS-RDI alarm is raised at the remote (source) multiplexer.
This alarm causes the port to be marked unavailable for synchronization if it

is entered in the synchronization source priority list.
Possible causes
MS-AIS alarm is generated at the source multiplexer or by a regenerator in
between.

Corrective actions
Procedure 2-11
MS-AIS alarm clearing
Step Action
1 Check the far multiplexer and any intermediate regenerators for the cause of
the AIS.
If the cause of the AIS is found, perform the appropriate alarm clearing
procedure.
If the cause of the alarm is not found, go to step 3.
2 If the ‘Local’ port provides the current synchronization source, switch to an
alternative source.
Procedures, 323-1123-510).
If the alarm is still present, remove the ‘Local’ loopback and go to step 3.
If the alarm clears, remove the ‘Local’ loopback and go to step 5.
4 Replace the local card. Refer to Maintenance Procedures, 323-1123-547.
5 Replace the far end card. Refer to Maintenance Procedures, 323-1123-547.
—end—

MS
MS-Remote Defect Indicator (RDI)
Significance
An MS Remote Defect Indicator has been detected in the K2 bytes of the MS
2
overhead. This indicates that the far multiplexer has detected a fault in its
incoming signal. The alarm is raised when there are five successive
occurrences of RDI and cleared when there are three successive absences of
RDI.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the MS-RDI alarm are:
• MS-AIS alarm at the far multiplexer.

Corrective actions
Procedure 2-12
MS-RDI alarm clearing
Step Action
1 Check the far multiplexer for the cause of the MS-AIS alarm.
If the cause of the alarm is found, perform the appropriate alarm clearing
procedure.
If the cause of the alarm is not found, go to step 2.
2 Check local multiplexer for local receive errors.
If local receive errors are found, investigate cause of errors.
—end—

MS
MS-Remote Error Indicator (REI)
Significance
An MS Remote Error Indication (the M1 byte of the section overhead)
2
indicates that the bit errors received at the far end multiplexer exceed the
configured threshold.
Note: REI alarm reports can be disabled.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the MS-REI alarm are:
• Ms-exc alarm at the far multiplexer.

Corrective actions
Procedure 2-13
MS-REI alarm clearing
Step Action
1 Check the far multiplexer for the cause of the MS-EXC alarm.
If the cause of the alarm is found, perform the appropriate alarm clearing
procedure.
3 Replace the local card Refer to Maintenance Procedures, 323-1123-547.
—end—

MS
MS-Excessive errors (EXC)
Significance
An MS Excessive Bit Error alarm is raised when the BER of the BIP-24 error
2
check on a received signal exceeds the configured threshold.
Instance/Unit
Impact
Critical alarm

If this port is entered in the synchronization source priority list this alarm
causes it to be marked unavailable for synchronization.
Consequent action
AIS is injected on the AU-4 payload of the transmitted path
(the consequent action is configurable - the default is off).
Transmission of MS-RDI in the return path (if the consequent action is on).
Possible causes
Possible causes for the MS-EXC alarm are:
• Faulty optical fibre, cable or connections.

Corrective actions
Procedure 2-14
MS-EXC alarm clearing
Step Action

Procedures, 323-1123-510).
alternative source.
If a MS-EXC alarm is present at the far multiplexer, remove the ‘Local’
If a MS-EXC alarm is not present at the far multiplexer, remove the ‘Local’
range (see Chapter 4).
If the received optical power is within range, go to step 7.
If the received optical power is not within range, clean the receive optical
connections at the local aggregate or STM-1o tributary.
optical fibre. Use appropriate methods to isolate and repair fibre fault.
—end—

MS
MS-Signal Degrade (DEG)
Significance
The MS Signal Degrade alarm is raised when the BER of the BIP-24 error
2
check exceeds the configured threshold.
Instance/Unit
Impact
Major alarm.

Consequent action
None.
Resulting alarm
Possible intermittent HP-REI alarms raised at an HP source.
Possible causes
Possible causes for the MS-DEG alarm are:
• Faulty optical fibre, cable or connections.

Corrective actions
Procedure 2-15
MS_DEG alarm clearing
Step Action

Procedures, 323-1123-510).
alternative source.
If a MS_DEG alarm is present at the far multiplexer, remove the ‘Local’
If a MS-DEG alarm is not present at the far multiplexer, remove the ‘Local’
5 Replace the far end card. Refer to Maintenance Procedures,323-1123-547.
range (see Chapter 4).
If the received optical power is within range, go to step 7.
If the received optical power is not within range, clean the receive optical
connections at the local aggregate or STM-1o tributary.
optical fibre. Use appropriate methods to isolate and repair fibre fault.
—end—

MS
MS-Quality of service violation (15 minute)
Significance
The Ms_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAS
2
active performance monitoring threshold has been broken within a 15 minute
monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Ms_qosv_15M alarm are:
Corrective actions
Procedure 2-16
Ms_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ma-ais or Ms-exc.
Identify and remove the cause of this alarm.
these errors.
3 The Ms_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—

MS
MS-Quality of service violation (24 hour)
Significance
The Ms_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAS
active performance monitoring threshold has been broken within a 24 hour
monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Ms_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-17
Ms_qosv_24H alarm clearing
Step Action
these errors.
3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—

MS
MS-Far end quality of service violation (15 minute)
Significance
The Ms_fe_qosv_15M alarm is raised to indicate that any BBE, ES, SES,
2
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Ms_fe_qosv_15M alarm are:
Corrective actions
Procedure 2-18
Ms_fe_qosv_15M alarm clearing
Step Action
these errors.
3 The Ms_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—

MS
MS-Far end quality of service violation (24 hour)
Significance
The Ms_fe_qosv_24H alarm is raised to indicate that any BBE, ES, SES,
UAS active performanance monitoring threshold has been broken within a 24
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Ms_fe_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-19
Ms_fe_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Rs_los,Rs_lof alarm, Ma-ais or Ms-exc. Identify
and remove the cause of this alarm.
these errors.
3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—

AU
AU-Alarm Indication Signal (AIS)
Significance
An AIS has been detected in the H1 and H2 bytes indicating a failure in the
2
upstream path. This alarm is raised when AIS occurs on three consequent
frames.
Instance/Unit
This alarm is raised against a high order path instance, reported as
S <slot-no> - <port-no> - J<AU-4>
Impact
Minor alarm.

Consequent action
AIS is injected on the AU-4 payload of the transmitted path.
A protection switch occurs at PPS protected VC-4 connections.
Resulting alarms
Transmission of HP-RDI in the return path.
Possible causes
Possible causes for the AU-AIS alarm are:

Corrective actions
Procedure 2-20
AU-AIS alarm clearing
Step Action
1 If the indicated port provides the current synchronization source, switch to an

alternative synchronization source.
2 Check the remote multiplexer and any intermediate regenerators for the
cause of AIS.
If the cause of AIS found, perform the appropriate alarm clearing procedure.
If the cause of AIS not found, go to step 3.
3 Perform a ‘Local’ loopback on the card (see Network Surveillance
Procedures, 323-1123-510).
Note: This loops back the STM-N data.
If the alarm is still present remove the ‘Local’ loopback and go to step 4.
If the alarm clears, the fault is at the far multiplexer. Remove the ‘Local’
4 Replace the indicated card. Refer to Maintenance Procedures,
323-1123-547.
—end—

AU
AU-Loss of Pointer (LOP)
Significance
The pointer value in the H1 and H2 bytes in the AU pointer is invalid for three
2
consecutive frames.
Instance/Unit
Impact
Minor alarm.

Consequent action
AIS injection on the AU-4 payload of the transmitted path.
A protection switch occurs at PPS protected VC-4 connections.
Resulting alarms
Possible causes
Faulty aggregate, STM-1o tributary or STM-1e tributary.
Corrective actions
Procedure 2-21
AU-LOP alarm clearing
Step Action
1 If the indicated card provides the current synchronization source, switch to an

323-1123-547.
—end—

HP
HP-Excessive errors (EXC)
Significance
When a VC-4 signal is created, a BIP-8 parity checksum is generated and
transmitted with the signal in the B3 byte. The B3 byte is examined and the
Bit error rate (BER) calculated when the VC-4 signal is received and
terminated.
When the BER value exceeds the operator configured threshold, the HP-EXC
alarm is raised.
Instance/Unit
Impact
Critical alarm.
Traffic is affected.
Consequent action
A protection switch occurs at protected VC-4 connections.
AIS is injected on the payload of the VC-4 transmitted path.
Note: The consequent actions are configurable (default off).
Resulting alarms
HP-RDI is transmitted in the return path (if the consequent action is on).
Possible causes
Possible causes for the HP-EXC alarm are:
• Possible line errors.

Corrective actions
Procedure 2-22
HP-EXC alarm clearing
Step Action 2
2 On an aggregate card check the other VC-4 paths. If these are carrying error
free traffic then switch this traffic before proceeding.
3 Perform a ‘Local’ loopback on the indicated card (see Network Surveillance
Procedures, 323-1123-510).
If the alarm is still present, the fault is at the local multiplexer. Remove the
‘Local’ loopback and perform step 4 at the local multiplexer.
loopback and perform step 5 at the far multiplexer.
323-1123-547.
—end—

HP
HP-Signal Degrade (DEG)
Significance
Signal degrade is an intermediate alarm which informs the operator that
signal quality is declining. The B3 byte is examined and the Bit error rate
(BER) calculated when the VC-4 signal is received and terminated. When the
BER value exceeds the operator configured threshold, the HP-DEG alarm is
raised.
If signal quality continues to decline the HP-EXC alarm threshold will be

crossed.
Instance/Unit
Impact
Major alarm.

Resulting alarm
HP-REI alarm.
Consequent action
None.
Possible causes
Possible causes for the HP-DEG alarm are:

Corrective actions
Procedure 2-23
HP-DEG alarm clearing
Step Action 2
Procedures, 323-1123-510).
323-1123-547.
5 Replace the appropriate card. Refer to Maintenance Procedures,
323-1123-547.
—end—

HP
HP-Trace Identifier Mismatch (TIM)
Significance
The VC-4 path trace feature allows the operator to specify a trace identifier at
the transmitting multiplexer and an expected identifier at the terminating
multiplexer. In the event of four successive occurrences of the expected trace
identifier not matching the transmitted identifier, the HP-TIM alarm is raised.
Note: You can disable reporting of this alarm.
Instance/Unit
Impact
Major alarm.
Traffic is affected if incorrect connection (wrong traffic).
Consequent action
Resulting alarm
Note: The consequent action is configurable; the default is off.
Possible causes
Possible causes for the HP-TIM alarm are:

Corrective actions
Procedure 2-24
HP-TIM alarm clearing
Step Action 2
2 Check the connections have been provisioned correctly. Refer to Provisioning
and Operations Procedures, 323-1123-310 for the procedure to view and
change connections.
If the connections are incorrect, reconfigure as necessary.
3 Check the system path trace settings at both ends (refer to Provisioning and
Operations Procedures, 323-1123-310).
If settings are incorrect, reconfigure as necessary.
4 At the local multiplexer, replace the indicated card. Refer to Maintenance
5 At the far multiplexer, replace the appropriate card. Refer to Maintenance
If the alarm clears, alarm clearing procedure is complete.
—end—

HP
HP-Remote Defect Indicator (RDI)
Significance
The VC-4 path remote defect indication (RDI) bit in the VC-4 path status byte
(G1) is set. This indicates that the far end multiplexer has detected a fault in
the incoming VC-4.
This alarm is raised when three successive RDI indications occur.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the HP-RDI alarm are:
• AU_AIS, AU_LOP, HP_LOM, or HP_EXC alarm at far multiplexer.

Corrective actions
Procedure 2-25
HP-RDI alarm clearing
Step Action 2
1 Check far multiplexer for cause of alarm (AU_AIS,AU_LOP, HP_LOM, or
HP_EXC alarm).
If the cause of the alarm found, perform the appropriate alarm clearing
procedure.
If the cause of the alarm not found, go to step 2.
If the alarm is permanent, go to step 3.
—end—

HP
HP-Loss of Multiframe (LOM)
Significance
When the VC-4 contains TU-12 payloads, the H4 byte indicates valid
multiframes. Loss of multiframe alignment is indicated if three consecutive
bad H4 bytes are received. Alignment is regained if two consecutive good H4
bytes are received.
Instance/Unit
Impact
Major alarm.

Consequent action
AIS injection on the payload of the VC-4 transmitted path.
Possible causes
Possible causes for the HP_LOM alarm are:
• Faulty aggregate, STM-1o tributary or STM-1e tributary
• Faulty far end aggregate, STM-1o tributary or STM-1e tributary

Corrective actions
Procedure 2-26
HP-LOM alarm clearing
Step Action 2
Procedures, 323-1123-510).
‘Local’ loopback. Goto step 2.
loopback. Goto step 3.
—end—

HP
HP-Remote Error Indicator (REI)
Significance
The BER of the remote error indication (REI) bits in the VC-4 path status
byte (G1) exceeds the configured threshold. This indicates that the far end
multiplexer has detected errors in the VC-4 path.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the HP-REI alarm are:
• HP errors on network.
• Faulty remote aggregate, STM-1o tributary or STM-1e tributary.
Corrective actions
Procedure 2-27
HP-REI alarm clearing
Step Action
1 Check remote multiplexer for cause of errors.

If the cause of the errors found, perform the appropriate alarm clearing
procedure.
If the cause of the errors not found, go to step 2.
If the alarm is permanent, go to step 3.
—end—

HP
HP-Payload Label Mismatch (PLM)
Significance
The value of the VC-4 signal label code in the C2 byte does not correspond
2
with the expected value. This alarm is raised when five successive string
mismatches occur.
Note: This alarm report can be disabled.
Instance/Unit
Impact
Major alarm.
Traffic is affected if the connection is incorrectly setup (wrong traffic).
Consequent action
Note that:
1 The consequent action is configurable. The default is off.
2 The consequent action for the HP-UNEQ and HP-PLM alarms are
configured together for any instance of VC-4.
Resulting alarms
Transmission of HP-RDI in the return path (if the consequent action is on).
Possible causes
Possible causes for the HP-PLM alarm are:
• Settings incorrectly set during configuration (i.e. receive string or far end
transmit string).
• If intermittent or transient events, errors in the signal.

Corrective actions
Procedure 2-28
HP-PLM alarm clearing
Step Action
1 Check that the optical connections are correct.

If the optical connections are incorrect, reconnect as required.
If the optical connections are correct, go to step 3.
change connections.
3 Check the HP signal label settings for each node. Refer to Provisioning and
Operations Procedures, 323-1123-310 for the procedure to view and change
the settings.
If the settings are incorrect, reconfigure as necessary.
If the settings are correct, go to step 4.
4 At the far multiplexer, replace the indicated card. Refer to Maintenance
—end—

HP
HP-Unequipped (UNEQ)
Significance
The value of the VC-4 path signal label code in the C2 byte indicates
2
unequipped (no connection is made). This alarm is raised when five
successive string mismatches occur.
Instance/Unit
Impact
Major alarm.
Consequent action
AIS injection on the VC-4 payload of the transmitted path.
Resulting alarms
Transmission of HP-RDI in the return path overhead.
Please note:
1 The consequent action is configurable; the default is off.
2 The consequent action for the HP-UNEQ and HP-PLM alarms are
configured together for any instance of VC-4.
Possible causes
Possible causes for the HP-UNEQ alarm are:
• Signal label incorrect (i.e. receive string or far end transmit string).

Corrective actions
Procedure 2-29
HP-UNEQ alarm clearing
Step Action

2 Check the signal label settings at both ends. Refer to Provisioning and
3 At the local multiplexer, replace the appropriate card. Refer to Maintenance
—end—

HP
HP-Signal Fail (SF)
Significance
The HP Signal Fail alarm is raised if both paths of a VC-4 protected
2
connection fail.
Instance/Unit
Impact
Critical alarm.
Consequent action
None.
Possible causes
Possible causes for the HP-SF alarm are:
• Incorrect connections.
• Faulty far end card.

Corrective actions
Procedure 2-30
HP-SF alarm clearing
Step Action

2 Check the provisioned connections at both ends. Refer to Provisioning and
—end—

HP
INT-HP-Input Buffer Overflow
Significance
The INT-HP-IP-BUFFER is raised if the input buffer for the high order
2
(VC-4) PDH mapper overflows.
Instance/Unit
This alarm is raised against a high order slot instance, reported as
S <slot-no> - <port-no> - J<AU-4>.
Impact
Major alarm
Consequent action
The VC-4 payload of the ongoing path is filled with ‘all ones’.
Possible causes
Possible causes for the INT-HP-IP-BUFFER alarm are:
• Incoming 140 Mbit/s signal bit-rate out-of-limits.
• Faulty 140 Mbit/s tributary card.
Corrective actions
Procedure 2-31
INT-HP-IP-BUFFER alarm clearing
Step Action
1 Check if the tributary input signal is within limits.

If the tributary input signal is not within limits, investigate preceding 140 Mbit/
s equipment.
If the tributary signal is within limits, go to step 2.
2 Replace the indicated 140 Mbit/s tributary card. Refer to the Equipment
Maintenance Procedures, 323-1123-547, for replacement procedures.
—end—

HP
INT HP-Output Buffer Overflow
Significance
The INT-HP-OP-BUFFER is raised if the output buffer for the 140M bit/s
desynchronizer overflows.
Instance/Unit
This alarm is raised against a high order port instance, reported as
S <slot-no> - <port-no> - J<AU-4>.
Impact
Major alarm
Consequent action
Possible causes
Possible causes for the INT-HP-OP-BUFFER alarm are:
• Transient changes in the payload bit rate.
Corrective actions
Procedure 2-32
INT-HP-OP-BUFFER alarm clearing
Step Action
1 Check if the tributary received signal is stable and within limits.

If the tributary input signal is not within limits, investigate preceding 140 Mbit/
s equipment.
2 Replace the indicated 140 Mbit/s tributary card. Refer to Maintenance
Procedures, 323-1123-547, for replacement procedures.
—end—

HP
HP-Quality of service violation (15 minute)
Significance
The Hp_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAS
2
active performanance monitoring threshold has been broken within a 15
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Hp_qosv_15M alarm are:
Corrective actions
Procedure 2-33
Hp_qosv_15M alarm clearing
Step Action
1 Check for the presence of the RS defects,MS defects, AU-AIS, AU-LOP,

INT-AU-AIS, INT-AU-LOP, HP-LOM,HP-TIM, HP-PLM or HP-EXC. Identify
and remove the cause of these alarms.
these errors.
3 The Hp_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—

HP
HP-Quality of service violation (24 hour)
Significance
The Hp_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAS
active performanance monitoring threshold has been broken within a 24 hour
monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Hp_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-34
Hp_qosv_24H alarm clearing
Step Action
1 Check for the presence of the RS defects,MS defects, AU-AIS, AU-LOP,

INT-AU-AIS, INT-AU-LOP, HP-LOM,HP-TIM, HP-PLM or HP-EXC. Identify
these errors.
3 The Hp_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—

HP
HP-Far end quality of service violation (15 minute)
Significance
The Hp_fe_qosv_15M alarm is raised to indicate that any BBE, ES, SES,
2
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Hp_fe_qosv_15M alarm are:
• HP-RDI alarm from the far multiplexer.
Corrective actions
Procedure 2-35
Hp_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the HP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from HP-REI. Identify and remove
the cause of these errors.
3 The Hp_fe_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—

HP
HP-Far end quality of service violation (24 hour)
Significance
The HP_fe_qosv_24H alarm is raised to indicate that any BBE, ES, SES,
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the HP_fe_qosv_24H alarm are:
• HP-RDI alarm from the far multiplexer.
Corrective actions
alarm.
Procedure 2-36
Hp_fe_qosv_24H alarm clearing
Step Action
1 Check for the presence of the HP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from HP-REI. Identify and remove
3 The Hp_fe_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—

HPOM
HPOM-Excessive errors (EXC)
Significance
When a VC-4 signal is created, a BIP-8 parity checksum is generated and
2
transmitted with the signal in the B3 byte. The B3 byte is examined and the
Bit error rate (BER) calculated from the VC-4 signal. When the BER value
exceeds the operator configured threshold, the HP-EXC alarm is raised.
The HPOM-EXC alarm is similar to the HP-EXC alarm. The HPOM-EXC

alarm is non-intrusively monitored whereas the HP-EXC is monitored from a
terminated connection.
Instance/Unit
Impact
Critical alarm.
Consequent action
A protection switch occurs at protected VC-4 connections.
AIS is injected on the payload of the VC-4 transmitted path.
Note: The consequent actions are configurable (default off).
Resulting alarms
HP-RDI is transmitted in the return path (if the consequent action is on).
Possible causes
Possible causes for the HPOM-EXC alarm are:

Corrective actions
Procedure 2-37
HPOM-EXC alarm clearing
Step Action

3 Perform a ‘Local’ loopback on the indicated card(see Network Surveillance
Procedures, 323-1123-510).
4 Replace the indicated card. Refer to Maintenance Procedures,323-1123-547.
—end—

HPOM
HPOM-Trace Identifier Mismatch (TIM)
Significance
The VC-4 path trace feature allows the operator to specify a trace identifier at
2
the transmitting multiplexer and an expected identifier at the terminating
multiplexer. In the event of four successive occurrences of the expected trace
identifier not matching the transmitted identifier, the HP-TIM alarm is raised.
The HPOM-TIM alarm is similar to the HP-TIM alarm. The HPOM-TIM

alarm is non-intrusively monitored whereas the HP-TIM is monitored from a
Note: You can disable reporting of this alarm.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the HPOM-TIM alarm are:

Corrective actions
Procedure 2-38
HPOM-TIM alarm clearing
Step Action

change connections.
3 Check the system path trace settings at both ends (refer to Provisioning and
4 At the local multiplexer, replace the indicated card. Refer to Maintenance
—end—

HPOM
HPOM-Payload Label Mismatch (PLM)
Significance
The value of the VC-4 signal label code in the C2 byte does not correspond
2
with the expected value. This alarm is raised when five successive string
mismatches occur.
The HPOM-PLM alarm is similar to the HP-PLM alarm. The HPOM-PLM

alarm is non-intrusively monitored whereas the HP-PLM is monitored from a
Instance/Unit
Impact
Major alarm.
Traffic is affected if the connection is incorrectly setup (wrong traffic).
Consequent action
None.
Possible causes
Possible causes for the HPOM-PLM alarm are:
• Settings incorrectly set during configuration (i.e. receive string or far end
transmit string).
• If intermittent or transient events, errors in the signal.

Corrective actions
Procedure 2-39
HPOM-PLM alarm clearing
Step Action
1 Check that the optical connections are correct.

change connections.
3 Check the HP signal label settings for each node. Refer to Provisioning and
Operations Procedures, 323-1123-310 for the procedure to view and change
the settings.
If the settings are incorrect, reconfigure as necessary.
4 At the far multiplexer, replace the indicated card. Refer to Maintenance
—end—

HPOM
HPOM-Unequipped (UNEQ)
Significance
The value of the VC-4 path signal label code in the C2 byte indicates
2
unequipped (no connection is made). This alarm is raised when five
successive string mismatches occur.
The HPOM-UNEQ alarm is similar to the HP-UNEQ alarm. The

HPOM-UNEQ alarm is non-intrusively monitored whereas the HP-UNEQ is
monitored from a terminated connection.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the HPOM-UNEQ alarm are:
• Signal label incorrect (i.e. receive string or far end transmit string).

Corrective actions
Procedure 2-40
HPOM-UNEQ alarm clearing
Step Action

2 Check the signal label settings at both ends. Refer to Provisioning and
—end—

TU
TU-Alarm Indication Signal (AIS)
Significance
An AIS has been detected in the pointer bytes of the TU overhead.
2
Instance/Unit
This alarm is raised against a low order path instance, reported as
S <slot-no> - <port-no> - J<VC-4> - K<klm>
Impact
Minor alarm
Consequent action
TU-AIS is injected on all through and add/drop TU connections.
TU-AIS is injected temporarily on protected TU connections.
A protection switch occurs on VC-3 or VC-12 PPS connections.
Possible causes
TU-AIS being generated by another multiplexer on the network.
Corrective actions
Procedure 2-41
TU-AIS alarm clearing
Step Action
1 Investigate network (LP path source and intermediate locations) for cause of
AIS (e.g., alarms that cause pass-through TU-AIS injection).
If the cause of AIS is found, perform the appropriate alarm clearing
procedures.
If cause of alarm not found, escalate problem.
—end—

TU
TU-Loss of Pointer (LOP)
Significance
The pointer value in the pointer bytes of the TU overhead is invalid for three
consecutive frames.
Instance/Unit
This alarm is raised against a low order path instance, reported as
S <slot-no> - <port-no> - J<VC-4> - K<klm>
Impact
Major alarm
Consequent action
TU-AIS is injected on all through and add/drop TU connections.
A protection switch occurs on VC-3 or VC-12 protected connections.
TU-AIS is injected temporarily on protected TU connections.
Possible causes
Faulty aggregate or tributary card.
Corrective actions
Procedure 2-42
TU-LOP alarm clearing
Step Action
1 Check that the correct network settings have been made. Refer to
Provisioning and Operations Procedures, 323-1123-310.
If network connection settings are incorrect, correct as necessary.
If network connection settings are correct, go to step 2.
—end—

TU
INT-TU-Alarm Indication Signal (AIS)
Significance
INT-TU-AIS is raised where the an AIS has been detected in the pointer bytes
2
of the TU overhead. This alarm is monitored later in the demultiplexer path
than the observation of TU-AIS, therefore an occurrence of INT-TU-AIS in
the absence of TU-AIS indicates an internal problem in the NE.
Instance/Unit
This alarm is raised against a PDH port instance, reported as
Impact
Major alarm
Consequent action
AIS is injected downstream to the PDH port output.
Possible causes
Faulty upstream traffic source.
Faulty tributary.
Corrective actions
Procedure 2-43
INT-TU-AIS alarm clearing
Step Action
1 If INT_TU_AIS and TU-AIS are both present, Investigate network (LP path
source and intermediate locations) for cause of AIS (e.g., alarms that cause
pass-through TU-AIS injection).
procedures.
2 If INT_TU_AIS is present and TU-AIS is not present, replace the aggregate
or tributary Unit. Refer to Maintenance Procedures, 323-1123-547.
—end—

TU
INT-TU-Loss of Pointer (LOP)
Significance
INT-TU-LOP is raised where the pointer value in the pointer bytes of the TU
overhead are invalid for three consecutive frames. This alarm is monitored
later in the demultiplexer path than the observation of TU-LOP, therefore an
occurrence of INT-TU-LOP in the absence of TU-LOP indicates an internal
problem in the NE.
Instance/Unit
This alarm is raised against a PDH port instance, reported as
Impact
Major alarm
Consequent action
AIS is injected downstream to the PDH port output.
Possible causes
Faulty upstream traffic source.
Faulty tributary.
Corrective actions
Procedure 2-44
INT-TU-LOP alarm clearing
Step Action
1 If INT_TU_LOP and TU-LOP are both present, Investigate network (LP path
source and intermediate locations) for cause of AIS (e.g., alarms that cause
pass-through TU-AIS injection).
procedures.
2 If INT_TU_LOP is present and TU-LOP is not present, replace the aggregate
or tributary Unit. Refer to Maintenance Procedures, 323-1123-547.
—end—

LP
LP-Excessive errors (EXC)
Significance
The BER of the VC-12 path status byte (V5) has exceeded the configured
2
threshold. This alarm is observed at the termination of the Low order
container.
Instance/Unit
Impact
Critical alarm
Traffic is affected on the outgoing signal.
Consequent action
LP-RDI is injected in the return path.
Possible causes
Corrective actions
Procedure 2-45
LP-EXC alarm clearing
Step Action
1 Check upstream for Lpom alarms. If Lpom alarms present, fault lies
upstream. If no Lpom alarms are present, fault is local.
2 Check network for possible bit errors.
3 Replace the indicated 2 Mbit/s tributary card. Refer to Maintenance
4 Restore to the old configuration.
—end—

LP
LP-Signal Degrade (DEG)
Significance
The LP-DEG alarm is raised when the BER of the VC-12 path status byte
(V5) has exceeded the configured threshold.
If signal quality continues to decline the LP-EXC alarm threshold will be

crossed.
Instance/Unit
S <slot-no> - <port-no>-J<VC-4>-Kklm
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the LP-DEG alarm are:
• Errors on network (Traffic source containing errors).
• Faulty tributary.
• Faulty backplane interface.

Corrective actions
Procedure 2-46
LP-DEG alarm clearing
Step Action 2
1 Check if there are any MS or HP alarms in upstream NE’s.
If there are MS or HP alarms in the network, perform the recommended
actions to clear alarms.
If there are no MS or HP alarms in the network, go to step 2.
2 Replace the indicated tributary card. Refer to Maintenance Procedures,
323-1123-547.
3 Restore to the old configuration.
4 Replace upstream traffic cards.
If the alarm is still present, escalate problem.
—end—

LP
LP-Payload Label Mismatch (PLM)
Significance
The value of the VC-12 signal label code in the V5 byte does not correspond
with the expected value. This alarm is raised at a path termination point,
subsequent to a protection switch.
Note: The reporting of this alarm and its consequent actions can be
enabled/disabled.
Instance/Unit
Impact
Major alarm
Traffic is affected
Consequent action
If configured to on, the:
• The VC-12 payload of the ongoing path is filled with ‘all ones’.
• LP-RDI is injected in the return path.
Possible causes
Possible causes for the LP-PLM alarm are:
• Incorrect overhead configuration at near or far end.
• Incorrect path connection.

Corrective actions
Procedure 2-47
LP-PLM alarm clearing
Step Action 2
1 Ensure that the system path configuration at both ends is correct as follows:
- if no traffic expected, both ends should be configured to send a
value of ‘0’.
- if traffic is expected, both ends should be configured to send a
value of ‘1’ or ‘2’.
Refer to Provisioning and Operations Procedures, 323-1123-310 for the
procedure to view and change connections.
2 Verify that the path is correctly connected at all intermediate multiplexers and
that no LP errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local 2 Mbit/s tributary card. Refer to the Equipment
If the alarm clears, the alarm clearing procedures are complete.
4 Replace the far 2 Mbit/s card. Refer to the Equipment Maintenance
Procedures, 323-1123-547 for replacement procedures.
—end—

LP
LP-Remote Defect Indicator (RDI)
Significance
The RDI bit (bit 8 in the V5 byte) is set. This indicates that the far end
multiplexer has detected a fault in the incoming VC-12.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the LP-RDI alarm are:
• AIS has occurred at path far end.
• If alarm raised for all tributaries, RS-LOS, RS-LOF, MS-AIS, MS-EXC,
AU-AIS, INT-AU-AIS, INT-AU-LOP, HP-TIM, HP-PLM or HP-LOM
alarm at the far multiplexer.
• If alarm raised for one tributary only, TU-AIS, TU-LOP, INT-TU-AIS,
INT-TU-LOP, LP-PLM or LP-EXC alarm present at far path termination.

Corrective actions
Procedure 2-48
LP-RDI alarm clearing
Step Action 2
1 Investigate far multiplexer/path termination for cause of alarm and carry out
fault finding procedures for appropriate alarm.
If cause of alarm found, perform the appropriate alarm clearing procedure.
If cause of alarm not found, go to step 2.
2 Verify that no LP errors are present on the network.
If the LP errors are present, investigate network errors.
If there are no LP errors in the network, go to step 3.
3 Replace the local tributary card. Refer to the Equipment Maintenance
4 Replace the far end tributary card. Refer to the Equipment Maintenance
—end—

LP
LP-Remote Error Indication (REI)
Significance
The REI bit (bit 3 in the V5 byte) is set. This indicates that the far end
multiplexer has detected a fault in the incoming VC-12.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
TU errors observed at path far end.
Corrective actions
Procedure 2-49
LP-REI alarm clearing
Step Action
1 Investigate far path termination for cause of errors and carry out fault finding
procedures for appropriate alarm (e.g. LP-DEG alarm).
If cause of alarm found, perform the appropriate alarm clearing procedure.
If cause of alarm not found, go to step 2.
3 Replace the far end tributary card. Refer to the Equipment Maintenance
—end—

LP
INT-LP-Input Buffer Overflow
Significance
The INT-LP-IP-BUFFER is raised if the input buffer for the low order
2
(VC-12, VC-3) PDH mapper overflows.
Instance/Unit
Impact
Major alarm
Consequent action
Possible causes
Possible causes for the INT-LP-IP-BUFFER alarm are:
• Incoming signal bit-rate out-of-limits.
• Faulty tributary card.

Corrective actions
Procedure 2-50
INT-LP-IP-BUFFER alarm clearing
Step Action
1 Check if the INT-LP-IP_Buffer alarm is present on more than one 2 Mbit/s

tributary port.
If the INT-LP-IP_Buffer alarm is only present on one tributary port, go to
step 2.
If the INT-LP-IP_Buffer alarm is present on more than one tributary port on a
single 2 Mbit/s card, go to step 3
If the INT-LP-IP_Buffer alarm is present on all the tributary ports on more than
one 2 Mbit/s cards, go to step 2.
2 Check if the tributary input signal is within limits.
If the tributary input signal is not within limits, investigate preceding 2 Mbit/s
equipment.
—end—

LP
INT LP-Output Buffer Overflow
Significance
The INT-LP-OP-BUFF is raised if the output buffer for the low order (VC-12,
2
VC-3) desynchronizer overflows.
Instance/Unit
Impact
Major alarm
Consequent action
Possible causes
Possible causes for the INT-LP-OP-BUFF alarm are:
• Transient changes in the received payload bit rate.

Corrective actions
Procedure 2-51
INT-LP-OP-BUFFER alarm clearing
Step Action
1 Check if the INT-LP-OP_BUFFER alarm is present on more than one 2 Mbit/

s tributary port.
If the INT-LP-OP_BUFFER alarm is only present on one tributary port, go to
step 2.
If the INT-LP-OP_BUFFER alarm is present on more than one tributary port
on a single 2 Mbit/s card, go to step 3
If the INT-LP-OP_BUFFER alarm is present on all the tributary ports on more
than one 2Mbit/s cards, go to step 2.
2 Check if the tributary received signal is stable and within limits.
If the tributary input signal is not within limits, investigate preceding 2 Mbit/s
equipment.
—end—

LP
LP-Signal Fail (SF)
Significance
The LP Signal Fail alarm is raised if both paths in a protected VC-12 or VC-3
2
connection fail.
Instance/Unit
Impact
Critical alarm.
Consequent action
None.
Possible causes
Upstream fault in both traffic paths.
Corrective actions
Procedure 2-52
LP-SF alarm clearing
Step Action
1 Check that the correct optical connections have been made.

2 Check the provisioned connections at both ends. Refer to Provisioning and
3 Investigate the traffic path alarms which are causing the SF alarm.
—end—

LP
LP-Trail Identifier Mismatch (TIM)
Significance
The VC-12 path trace feature allows the operator to specify a trace identifier
in the J2 byte at the transmitting multiplexer and an expected identifier at the
terminating multiplexer. In the event of the expected trace identifier not
matching the transmitted identifier, the LP-TIM alarm is raised. This alarm is
detected at a path termination after a path protection operation.
Instance/Unit
Impact
Major alarm
If consequent actions are configured to ON traffic is affected.
Consequent action
AIS is injected in VC-12 payload.
RDI sent downstream in V5 byte.
Possible causes
Possible causes for the LP-TIM alarm are:
• Incorrect configuration of far end or near end path string.

Corrective actions
Procedure 2-53
LP-TIM alarm clearing
Step Action 2
1 Ensure that the operator entered string has been entered correctly at both
ends:
If the settings are incorrect, correct as necessary
2 Verify that the path is correctly connected at all local and intermediate
multiplexers and that no LP errors are present on the network.
go to step 3.
4 Replace the far end card. Refer to the Equipment Maintenance Procedures,
323-1123-547, for replacement procedures.
—end—

LP
LP-Label Unequipped
Significance
The LP-UNEQ value of the VC-12 payload signal label indicates unequipped
(no traffic in payload).
Instance/Unit
Impact
Major alarm
If consequent actions are configured to on traffic is affected
Consequent action
Possible causes
Possible causes for the LP-UNEQ alarm are:

Corrective actions
Procedure 2-54
LP-UNEQ alarm clearing
Step Action 2
value of ‘0’.
go to step 3.
4 Replace the far end card. Refer to the Equipment Maintenance Procedures,
323-1123-547 for replacement procedures.
—end—

LP
LP-Quality of service violation (15 minute)
Significance
The Lp_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAS
active performanance monitoring threshold has been broken within a 15
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Lp_qosv_15M alarm are:
Corrective actions
Procedure 2-55
Lp_qosv_15M alarm clearing
Step Action
1 Check for the presence of the RS defects,MS defects, AU defects,HP defects,

TU-AIS, TU-LOP, LP-TIM, LP-PLM, LP-EXC, INT-LO-BUFFER-OVERFLOW.
Identify and remove the cause of these alarms.
2 Check for the presence of errored blocks. Identify and remove the cause of
these errors.
3 The Lp_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—

LP
LP-Quality of service violation (24 hour)
Significance
The Lp_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAS
2
active performanance monitoring threshold has been broken within a 24 hour
monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Lp_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-56
Lp_qosv_24H alarm clearing
Step Action
1 Check for the presence of the RS defects,MS defects, AU defects,HP defects,

TU-AIS, TU-LOP, LP-TIM, LP-PLM, LP-EXC, INT-LO-BUFFER-OVERFLOW.
Identify and remove the cause of these alarms.
2 Check for the presence of errored blocks. Identify and remove the cause of
these errors.
3 The Lp_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—

LP
LP-Far end quality of service violation (15 minute)
Significance
The Lp_fe_qosv_15M alarm is raised to indicate that any BBE, ES, SES,
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the Lp_fe_qosv_15M alarm are:
• LP-RDI alarm from the far multiplexer.
• Faulty local tributary.
• Faulty far end tributary.
Corrective actions
Procedure 2-57
Hp_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the LP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from LP-REI. Identify and remove
3 The Lp_fe_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—

LP
LP-Far end quality of service violation (24 hour)
Significance
The LP_fe_qosv_24H alarm is raised to indicate that any BBE, ES, SES,
2
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the LP_fe_qosv_24H alarm are:
• LP-RDI alarm from the far multiplexer.
• Faulty local tributary.
• Faulty far end tributary.
Corrective actions
alarm.
Procedure 2-58
Lp_fe_qosv_24H alarm clearing
Step Action
1 Check for the presence of the LP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from LP-REI. Identify and remove
3 The Lp_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—

LPOM
LPOM-Excessive Errors (EXC)
Significance
The LPOM-EXC is raised when the BER of the VC-12 path status byte (V5)
has exceeded the configured threshold.
The LPOM_EXC alarm is similar to the LP-EXC alarm. The LPOM-EXC

alarm is non-intrusively monitored at the STM-N receive port of the
container. The LP-EXC is monitored from a terminated connection at the
termination point.
Instance/Unit
Impact
Critical alarm
Consequent action
A traffic protection switch occurs.
Possible causes
Possible causes for the LPOM-EXC alarm are:
• Errors on network.

Corrective actions
Procedure 2-59
LPOM-EXC alarm clearing
Step Action 2
1 Check if there are any MS or HP bit error alarms in the network, upstream.
If there are MS or HP alarms in the network, perform the recommended
actions to clear alarms.
If there are no MS or HP alarms in the network, go to step 2.
323-1123-547. Restore to the old configuration.
—end—

LPOM
LPOM-Trail Identifier Mismatch (TIM)
Significance
The VC-12 path trace feature allows the operator to specify a trace identifier
in the J2 byte at the transmitting multiplexer and an expected identifier at the
terminating multiplexer. In the event of the expected trace identifier not
matching the transmitted identifier, the LPOM-TIM alarm is raised.
The LPOM-TIM alarm is similar to the LP-TIM alarm. The LPOM-TIM

alarm is non-intrusively monitored whereas the LP-TIM is monitored from a
Instance/Unit
S <slot-no> - <port-no>--J<VC-4>-Kklm
Impact
Major alarm
Consequent action
None.
Possible causes
Possible causes for the LPOM-TIM alarm are:
• Incorrect configuration of far end or near end path string.
• Faulty 2 Mbit/s tributary.

Corrective actions
Procedure 2-60
LPOM-TIM alarm clearing
Step Action 2
1 Ensure that the operator entered string has been entered correctly at both
ends:
2 Verify that the path is correctly connected at all local and intermediate
multiplexers and that no LP errors are present on the network.
go to step 3.
—end—

LPOM
LPOM-Payload Label Mismatch (PLM)
Significance
The value of the VC-12 signal label code in the V5 byte does not correspond
with the expected value. This alarm is raised at a path termination point,
subsequent to a protection switch.
The LPOM-PLM alarm is similar to the LP-PLM alarm. The LPOM-PLM

alarm is non-intrusively monitored whereas the LP-PLM is monitored from a
Note: The reporting of this alarm can be enabled/disabled.
Instance/Unit
Impact
Major alarm
Consequent action
None.
Possible causes
Possible causes for the LPOM-PLM alarm are:

Corrective actions
Procedure 2-61
LPOM-PLM alarm clearing
Step Action 2
value of ‘0’.
Refer to Provisioning and Operations Procedures, 323-1123-310 for the
procedure to view and change connections.
go to step 3.
—end—

LPOM
LPOM-Label Unequipped (UNEQ)
Significance
The LP-UNEQ value of the VC-12 payload signal label indicates unequipped
(no traffic in payload).
The LPOM-UNEQ alarm is similar to the LP-UNEQ alarm. The

LPOM-UNEQ alarm is non-intrusively monitored whereas the LP-UNEQ is
monitored from a terminated connection.
Instance/Unit
Impact
Major alarm
If consequent actions are configured to on traffic is affected
Consequent action
None.
Possible causes
Possible causes for the LPOM-UNEQ alarm are:

Corrective actions
Procedure 2-62
LPOM-UNEQ alarm clearing
Step Action 2
value of ‘0’.
that no LP or LPOM errors are present on the network.
go to step 3.
Maintenance Procedures, 323-1123-547 for replacement procedures.
—end—

PPI
PPI-Transmit Fail (TF)
Significance
The tributary output signal has fallen below a predefined threshold.
Instance/Unit
Impact
Critical Alarm
Loss of tributary traffic output
Consequent action
None.
Possible causes
Possible causes for the PPI-TF alarm are:
• Cable fault.

Corrective actions
Procedure 2-63
PPI-TF alarm clearing
Step Action 2
1 Ensure that the traffic output cable is properly terminated. Re-terminate the
connector if required.
2 Ensure that the traffic output cable is properly terminated. Re-terminate the
connector if required.
3 Check the far end equipment for a short circuit.
If the alarm clears, the alarm clearing procedure is complete. If the alarm is
4 Replace the indicated tributary card. Refer to the Equipment Maintenance
—end—

PPI
PPI-Loss Of Signal (LOS)
Significance
The PPI-LOS is raised where the loss of a PDH input signal is detected.
Instance/Unit
Impact
Critical alarm.
Consequent action
All-ones(AIS) are transmitted in the traffic payload.
Possible causes
Possible causes for the PPI-LOS alarm are:
• Preceding equipment failure.
• Input connector not properly connected.

Corrective actions
Procedure 2-64
PPI-LOS alarm clearing
Step Action 2
1 Ensure that the associated input connector is properly connected.
If connector is not properly connected, re-insert connector.
If connector is properly connected, go to step 2.
2 Verify that a valid tributary signal is present at distribution frame.
If a valid signal is not present, check the tributary source equipment.
If a valid signal is present, go to step 4.
3 Verify that a valid tributary signal is present at the cable headshell.
Note: Removal of a 2 Mbit/s cable headshell causes a traffic loss on all 16
ports.
If a spare unused traffic port is available, the PDH signal can be verified by
connecting the cable to the spare port. If a signal is present, a
‘PPI-Unexp_Signal’ alarm will be raised for the spare port.
If a valid signal is not present, a cable fault is suspected.
4 Replace the indicated tributary card, Refer to the Equipment Maintenance
—end—

PPI
PPI-Alarm Indication Signal (AIS)
Significance
The PPI-AIS alarm is raised when the PDH interface detects an AIS condition
on the PDH input traffic.
Instance/Unit
Impact
Minor alarm.
Consequent action
All-ones(AIS) are transmitted in the traffic payload.
Possible causes
AIS being generated by preceding equipment.
Corrective actions
Investigate preceding equipment for the cause of AIS.

PPI
PPI-Excessive errors (EXC)
Significance
The PPI-EXC alarm is raised when HDB3 code violations exceed the
2
threshold in a PDH signal.
Instance/Unit
Impact
Critical alarm.
Consequent action
All-ones(AIS) are sent via the PDH input payload to the VC12 container.
Possible causes
Possible causes for the PPI-EXC alarm are:
• Errored input signal.
Corrective actions
Procedure 2-65
PPI-EXC alarm clearing
Step Action
1 Investigate preceding equipment and cable for cause of errors.

—end—

PPI
PPI-Signal Degrade (DEG)
Significance
The PPI-DEG alarm is raised when HDB3 code violations exceed the
threshold in a PDH signal.
If signal quality continues to decline the PPI-EXC alarm threshold will be

crossed.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the PPI-DEG alarm are:
• Errored input signals.
Corrective actions
Procedure 2-66
PPI-DEG alarm clearing
Step Action
1 Investigate preceding equipment and cables for cause of errors.

—end—

PPI
PPI-Unexpected Signal
Significance
The PPI-UNEXP_SIGNAL alarm is raised where a signal is connected to a
2
2 Mbit/s or 140 Mbit/s port for which a traffic connection is not configured.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the PPI-UNEXP_SIGNAL alarm are:
• Incorrect cable connection.
• Incorrect System configuration.
• Faulty 2 Mbit/s or 140 Mbit/s tributary card.
Corrective actions
Procedure 2-67
PPI-UNEXP_SIGNAL alarm clearing
Step Action
1 Check whether a connection is expected on this tributary.

If a connection is expected, re-configure system as necessary.
If a connection is not expected, go to step 2.
2 Check cable connections to ensure that the cables are connected to the
correct input terminations.
If the cable connections are incorrect, re-connect the cables as required.
If the cable connections are correct, go to step 3.
—end—

PPI
PPI-Loss of Frame (LOF)
Significance
The PPI-LOF alarm is raised where a PDH port reports that signal framing
information cannot be recovered in the recieve path. This alarm will ony be
reported if the input port is configured to framed or multi-framed.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the PPI-LOF alarm are:
Corrective actions
Procedure 2-68
PPI-LOF alarm clearing
Step Action
1 Investigate preceding equipment and cables for cause of errors.

—end—

PPI
PPI-Loss of Multiframe (LOM)
Significance
The PPI-LOM alarm is raised where a 2 Mbit/s PDH port reports that signal
2
multiframing information cannot be recovered in the recieve path. The input
port must be configured to multi-framed.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the PPI-LOM alarm are:
Corrective actions
Procedure 2-69
PPI-LOM alarm clearing
Step Action
1 Investigate preceding 2 Mbit/s equipment and cables for cause of errors.

—end—

PPI
PPI-Loopback On
Significance
The PPI-LOOPBACK-ON alarm is raised if a local or remote loopback is
placed on a PDH port. This alarm is a reminder to the network operator of
existing configured loopbacks.
Instance/Unit
Impact
Minor alarm.
Consequent action
None.
Possible causes
Local or remote loopback has been placed on a PDH port.
Corrective actions
If required, remove the loopback as detailed in Network Surveillance

PPI
PPI- Transmit-Loss of Frame (T-LOF)
Significance
The PPI-T-LOF alarm is raised where a 140 Mbit/s PDH port reports that
2
signal framing information cannot be recovered in the transmit path. This
alarm will ony be reported if the input port is configured to framed or
multi-framed.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the PPI-T-LOF alarm are:
• Output cable fault.
Corrective actions
Procedure 2-70
PPI-T-LOF alarm clearing
Step Action
1 Investigate preceding 140 Mbit/s equipment and cables for cause of errors.
—end—

PPI
PPI-Code violation Quality of service violation
(15 minute)
Significance
The PPI_CV_qosv_15M alarm is raised to indicate that any BBE, ES, SES,
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the PPI_CV_qosv_15M alarm are:
Corrective actions
Procedure 2-71
PPI_CV_qosv_15M alarm clearing
Step Action
1 Check for the presence of code violation defects, PPI-LOF, PPI-AIS. Identify
2 Check for the presence of errored frames. Identify and remove the cause of
these errors.
3 The PPI_CV_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—

PPI
PPI-Code violation-Quality of service violation
(24 hour)
2
Significance
The PPI_CV_qosv_24H alarm is raised to indicate that any BBE, ES, SES,
Instance/Unit
Impact
Minor Alarm
Consequent action
None.
Possible causes
Possible causes for the PPI_CV_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-72
PPI_CV_qosv_24H alarm clearing
Step Action
1 Check for the presence of code violation defects, PPI-LOF, PPI-AIS. Identify
2 Check for the presence of errored frames. Identify and remove the cause of
these errors.
3 The PPI_CV_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—

SYNC
Sync-SETG Fail
Significance
This alarm indicates that a serious problem has occurred in the
synchronization source selection circuit on the indicated aggregate card.
Instance/Unit
This alarm is raised against an aggregate card instance, reported as
S <slot-no>
Impact
Critical alarm
The standby aggregate card is used as the source of synchronization timing.
Consequent action
None.
Possible causes
Failure of the synchronization circuit on the indicated aggregate card.
Corrective actions
Procedure 2-73
SYNC-SETG_Fail alarm clearing
Step Action
1 Replace the indicated aggregate card. Refer to Maintenance Procedures,

323-1123-547.
2 If the alarm is still present, escalate problem or replace subrack.
—end—

SYNC
Sync-Unexpected signal
Significance
The external synchronization input (ESI) port is receiving a synchronization
2
signal but the port is not in the hierarchy list.
Instance/Unit
This alarm is raised against an external synchronization port instance,
reported as
S <slot-no> - 1
Impact
Major alarm.
Consequent action
None.
Possible causes
The ESI port is not in the SETG or ESO hierarchy list.
Corrective actions
Add the ESI port to the hierarchy list.

SYNC
Sync-ESO Source Not Primary
Significance
The source currently selected to provide synchronization is not the primary
source as defined in the ESO hierarchy list.
Note:
• If synchronization source messaging (SSM) is active this alarm is not
raised.
• Selecting a synchronization source using a Forced override does not raise
this alarm.
Instance/Unit
None.
Impact
Critical alarm.
Consequent action
None.
Possible causes
Failure of primary source.
Corrective actions
Investigate primary source for possible faults or synchronization source
switching actions.

SYNC
Sync-Holdover
Significance
This alarm is raised when the NE is operating in holdover mode. This mode is
2
entered when all external synchronization input sources are rejected and the
internal clock is running off historical values (or has just started).
The holdover alarm is not raised if the NE is deliberately configured to run off
the internal oscillator (by a forced command or through an INT entry in the
hierarchy list).
Instance/Unit
This alarm is raised against the NE.
Impact
Critical alarm.
Consequent action
None.
Possible causes
Possible causes for the SYNC-HOLDOVER alarm are:
• Forced switch to a faulty synchronization source.
• All sources on the hierarchy list are faulty and the NE is using the internal
oscillator for synchronization.
Corrective actions
If a forced switch is active, check the status of the synchronization source.
Change the hierarchy list to include a good synchronization source.

SYNC
Sync-Source Not Primary
Significance
The source currently selected to provide synchronization is not the primary
source as defined in the SETG hierarchy list.
Note:
• If synchronization source messaging (SSM) is active this alarm will not be
raised.
• If the current synchronization source was selected by a Forced override,
this alarm is not raised.
Instance/Unit
None.
Impact
Major alarm.
Consequent action
None.
Possible causes
Failure of primary source.
Corrective actions
Investigate primary source for possible faults or synchronization source
switching actions.

SYNC
Sync-External Sync Loss Of Signal
Significance
The signal from the external synchronization input (ESI) on an End of Shelf
2
(EOS) card has failed.
Note: The external source must be in the synchronization hierarchy (or

forced on) for the alarm to be raised.
Instance/Unit
This alarm is raised against an external synchronization port instance,
reported as
S <slot-no> - 1
Impact
Critical alarm
Consequent action
None.
Possible causes
Possible causes for the SYNC-External Loss of Signal alarm are:
• Input connector not properly terminated.
• External synchronization source failure.
• Faulty End of Shelf card.

Corrective actions
Procedure 2-74
SYNC-Ext_Sync_LOS alarm clearing
Step Action
1 Check that the ESI input connector is properly seated.

If the connector is not properly seated, re-insert connector.
If the connector is properly seated, go to step 2.
2 Check that a valid signal is present at the output of the ESI cable.
If a valid signal is not present, check the interconnecting cable and the
external synchronization source.
3 Replace the indicated EOS card. Refer to Maintenance Procedures,
323-1123-547.
—end—

SYNC
Sync-SETG Frequency suspect
Significance
The SETS reports an out of lock condition. This alarm means that either the
2
current synchronization source is out of limits or the SETS is out of lock.
Note: The source must be in the synchronization hierarchy (or forced on)
for the alarm to be raised.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Faulty synchronization source or SETS in the aggregate card.
Corrective actions
Procedure 2-75
SYNC-SETG_frequency_suspect alarm clearing
Step Action
1 Apply a lockout to the indicated source. Refer to Provisioning and Operations

If the alarm clears, the source is faulty.
2 Replace the active aggregate card. Refer to Maintenance Procedures,
323-1123-547.
3 If the alarm is still present, escalate problem or replace subrack.
—end—

SYNC
Sync-Source out of limits
Significance
A port which can be used as a frequency source has a gross frequency offset.
Instance/Unit
This alarm is raised against an input port which is in either of the SETG or
ESO selector Synchronization Source Hierarchies.
Impact
Major alarm.
Consequent action
None.
Possible causes
Corrective actions
Procedure 2-76
SYNC-SOURCE-OUT-OF-LIMITS alarm clearing
Step Action
1 Identify and remove the cause of the frequency errors.

2 Access the ‘Maint/Operations/Sync_source’ submenu by selecting
n Maint m
n Operations o
n Sync_source s
3 Execute the clr_out_of_limits command by selecting
l clr_out_of_limits c
4 Insert the port number of the alarm you wish to clear and select submit.
Confirmation is required
—end—

SYNC
Sync-Lock fail
Significance
This alarm is raised when either the SETG or ESO PLL reports an out-of-lock
2
condition.
Instance/Unit
This alarm is raised against an aggregate card instance, reported as
S <slot-no>
Impact
Critical alarm.
Consequent action
None.
Possible causes
Corrective actions
Procedure 2-77
SYNC-LOCK-FAIL alarm clearing
Step Action
1 Identify and remove the cause of the frequency errors.

2 Access the ‘Maint/Operations/Sync_source’ submenu by selecting
n Maint m
n Operations o
n Sync_source s
3 Execute the clr_out_of_limits command by selecting
l clr_out_of_limits c
4 Insert the port number of the alarm you wish to clear and select submit.
Confirmation is required
—end—

Misc
Qecc Comms Fail
Significance
The NE cannot communicate with the neighbouring NE via the Embedded
Control Channel (ECC).
Instance/Unit
Impact
Critical alarm
Non-traffic affecting.
Inter-site data communications are unavailable.
Consequent action
None.
Possible causes
Possible causes for the Qecc Comms Fail alarm are:
• Loopback present.
• The card carrying the ECC has been unequipped.
When STM-1o tributary cards in a 1+1 MSP association are connected to a

TN-16X multiplexer, the non-active STM-1o port raises a ‘QECC comms
fail’ alarm. This is normal operation and the alarm does not need to be
cleared.

Corrective actions
Procedure 2-78
Qecc_Comms_Fail alarm clearing
Step Action 2
1 Check if a loopback is present. Refer to Network Surveillance Procedures,
323-1123-510.
If a loopback is present, disable the loopback. If the alarm is still present, go
to step 2.
If the alarm has cleared, the alarm clearing procedure is complete.
2 Check if any of the cards in the ECC path have been unequipped.
If the card is unequipped, re-equip it using the CAT. refer to Provisioning and
3 Examine the current Lapd mode.Refer to Provisioning and Operations
If the failed link is in then
Rs mode goto step 4
Ms mode goto step 5
Both goto step 6
Auto goto step 7
4 Switch to Ms mode. Refer to Provisioning and Operations Procedures,

323-1123-310.
5 Switch to Rs mode. Refer to Provisioning and Operations Procedures,
323-1123-310.
6 Perform a status_view command to determine whether Rs or Ms has failed.
Refer to Provisioning and Operations Procedures, 323-1123-310
Goto step 7
—continued—

Procedure 2-78
Qecc_Comms_Fail alarm clearing (continued)
Step Action

—end—

Misc
INT NE-Spi Comms Fail
Significance
A fault has been detected on the internal SPI communications function.
2
Instance/Unit
Impact
Critical alarm
Non-traffic affecting.
Inter-site data communications are unavailable.
Consequent action
None.
Possible causes
Possible causes for the INT NE-Spi-Comms-Fail alarm are:
Corrective actions
Procedure 2-79
Spi-Comms_Fail alarm clearing
Step Action

323-1123-547.
—end—

Misc
EA-Ext inp <1-8>
Significance
A alarm has been received on one of the external alarm inputs.
Instance/Unit
This alarm is raised against an external alarm input instance.
Impact
Critical alarm.
Consequent action
None.
Possible causes
Dependant on the alarm source.
Corrective actions
Investigate the alarm source for the cause of the alarm.

Misc
INT NE-Configuration Corrupt
Significance
The configuration data held in the configuration bank is corrupt and the NE
2
enters detached mode.
This alarm is raised only when one of the following configuration alarms is
raised:
• INT NE-config_all_banks_corrupt
• INT NE-config_available_bank_corrupt
• INT NE-config_validation_error
• INT NE-config_audit_mismatch
• INT NE-config_bp_mismatch
Instance/Unit
Impact
Critical alarm.
Consequent action
None.
Possible causes
Configuration data corrupt.
Corrective actions
Check which of the associated configuration alarms are also present. Perform
the alarm clearing procedures for the associated alarm.

Misc
NE-Lan Alarm
Significance
A fault has been detected on the LAN sub-network.
Note: This alarm is blocked if the LAN service is configured as off or

standby.
Instance/Unit
This alarm is raised against a LEOS port instance, reported as
S 15B - <port-no>
Impact
Critical alarm.
Loss of communication to the EC and to any NEs connected via the local
LAN sub-network.
Consequent action
None.
Possible causes
Possible causes for the NE-Lan alarm are:
• LAN connector not properly terminated.
• Problem on LAN sub-network.
Corrective actions
Check that the LAN connector is properly terminated. If the LAN connector
is properly terminated, investigate the local LAN sub-network.

Misc
NE-Unexpected LAN
Significance
Indicates a LAN is present but the LAN service state is set to Standby
2
(indicating that a LAN is not expected).
Instance/Unit
None.
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the Unexpected LAN alarm are:
• LAN is incorrectly connected.
• System is incorrectly configured.
Corrective actions
If a LAN is expected, reconfigure the system as required (see Provisioning
and Operations Procedures, 323-1123-310).
If a LAN is not expected, remove the LAN connection.

Misc
INT NE-Config bp mismatch
Significance
The serial number of the master aggregate card does not match the serial
number stored in the backplane SIM card. This check occurs during a warm
or cold restart of the master aggregate. The NE enters detached mode
Instance/Unit
Impact
Critical alarm.
Consequent action
None.
Possible causes
The aggregate has been replaced or there is a mismatch in the configuration
data.
Corrective actions
Perform the following procedures (refer to System and Data Administration
Procedures, 323-1123-302):
• Check the configuration and change if necessary.
• Impose the stored configuration. This will;
—write the serial number of the aggregate cards into the SIM card
—take the NE out of detached mode
—remove the alarm

Misc
Ps-power fail
Significance
The power supply to either the Upper or Lower end of shelf cards has failed.
2
Instance/Unit
This alarm is raised against an EOS card instance, reported as
S <slot-no>
Impact
Critical alarm.
Consequent action
None.
Possible causes
Power supply fail
Corrective actions
Check the power connection to the indicated card.
Replace the indicated card. Refer to Maintenance Procedures, 323-1123-547.

Misc
NE-Date time unknown
Significance
This alarm is raised when the real time clock in the NE has no knowledge of
the date and time.
Instance/Unit
None.
Impact
Major alarm.
Consequent action
None.
Possible causes
A loss of power to the NE will cause the contents of the RTC to be lost.
Corrective actions
Set the real time clock. Refer to System and Data Administration Procedures,
323-1123-302.

Misc
Unexpected SW version
Significance
The software version on a tributary or aggregate card does not match the
2
version number in the configuration store.
Instance/Unit
None.
Impact
Minor alarm.
Consequent action
None.
Possible causes
Card installed with incorrect software load.
Corrective actions
Perform a software upgrade on the indicated card as detailed in System and
Data Administration Procedures, 323-1123-302.

Misc
Internal 1 second clock loss of signal
Significance
A card with a missing 1-second input clock will raise this alarm.
Instance/Unit
This alarm is raised against a card instance, reported as
S <slot-no>
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for this alarm are:
• aggregate failure.
• tributary failure.
• Backplane failure.
Corrective actions
Perform a SEMF protection switch. If the alarm persists, replace aggregate or
tributary card (see Provisioning and Operations Procedures, 323-1123-310).

Card
NE-Card Out
Significance
Indicates that the indicated card has been removed from the subrack without
2
unequipping the slot.
Note: When a card is inserted, the NE-Card_Out alarm remains active

until the card is configured in order to suppress other alarms.
Instance/Unit
This alarm is raised against an NE card instance, reported as
S <slot-no>
Impact
Critical alarm
Consequent action
None.
Possible causes
Possible causes for the Card Out alarm are:
• Card removed.
• System incorrectly configured.
• Faulty aggregate card.

Corrective actions
Procedure 2-80
NE-Card_Out alarm clearing
Step Action
1 Check if the card is expected in the indicated slot.

If the card is not expected, go to step 2.
If the card is expected in the indicated slot, check that the card is correctly
installed in the TN-4E. If the alarm still present, go to step 3.
2 Configure the equipment to unequip the indicated slot, see Provisioning and
3 Replace the aggregate card. Refer to Maintenance Procedures,
323-1123-547.
If the alarm is still present, replace original aggregate card and escalate
problem.
—end—

Card
NE-Unexpected Card
Significance
Indicates that a card is present in a slot which is configured as ‘Unequipped’.
2
This alarm is raised approximately 30 seconds after the card is inserted.
Note: When a card is inserted, the Unexpected_Card alarm remains active

until the card is configured, in order to suppress other alarms.
Instance/Unit
S <slot-no>
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the Unexpected Card alarm are:
• Card inserted into wrong slot.

Corrective actions
Procedure 2-81
NE-Unexpected_Card alarm clearing
Step Action
1 Check if the card is expected in indicated slot.

If the card is expected, go to step 2.
If the card is not expected, remove the card from the indicated slot. If alarm
still present, go to step 3
2 Configure the equipment to equip the slot with the correct card type (see
Provisioning and Operations Procedures, 323-1123-310).
If the alarm still present, go to step 3.
3 Replace the aggregate card. Refer to Maintenance Procedures,
323-1123-547.
If the alarm still present, replace original aggregate card and escalate
problem.
—end—

Card
NE-Card Fail
Significance
The aggregate card detects a fault on the indicated card or fails to
2
communicate with the indicated card.
Instance/Unit
S <slot-no>
Impact
Critical alarm.
May be traffic affecting.
Consequent action
None.
Possible causes
Possible causes for the Card Fail alarm are:
• Faulty indicated card.
Corrective actions
Procedure 2-82
NE-Card_Fail alarm clearing
Step Action
1 Check if the alarm is permanently indicated for all cards.

If the alarm is permanently indicated for all cards, replace the active
aggregate card. Refer to the Maintenance Procedures, 323-1123-547. Go to
step 3.
If the alarm is permanently indicated for a single card, go to step 2.
2 Perform a warm restart on the card.
If the alarm is still present, perform a cold restart on the card.
3 Check if alarm is still present.
If the alarm has cleared, the alarm clearing procedure is complete. If the
alarm is still present, escalate problem or replace subrack.
—end—

Card
NE-Card Fault
Significance
Self-diagnosis indicates the card has a fault.
Instance/Unit
S <slot-no>
Impact
Critical alarm.
Traffic is affected if the fault is on an aggregate or tributary card.
Consequent action
None.
Possible causes
Faulty indicated card.
Corrective actions
If the alarm is repeated or persistent, replace indicated card. Refer to the
Maintenance Procedures, 323-1123-547.

Card
NE-Wrong Card
Significance
A card has been inserted into a slot designated for another type of card (slot
2
wrong or card wrong).
Instance/Unit
S <slot-no>
Impact
Critical alarm.
Traffic is affected if traffic card.
Consequent action
None.
Possible causes
Possible causes for the Wrong Card alarm are:
• Wrong card fitted in a slot.
• Card fitted in wrong slot.
Corrective actions
Procedure 2-83
NE-Wrong_Card alarm clearing
Step Action
1 Check what unit should be fitted in the indicated slot.

If the correct unit is not fitted to the slot, remove the current unit and fit the
correct unit. Go to step 2.
If the correct unit is fitted, reconfigure the slot to be equipped with the correct
unit type (see Provisioning and Operations Procedures, 323-1123-310). Go
to step 2.
2 Check if alarm is still present.
—end—

Card
NE-Invt Write Jumper Fitted
Significance
This alarm indicates that a link is present on a card which enables access to
the non-volatile RAM.
Instance/Unit
S <slot-no>
Impact
Major alarm.
Consequent action
None.
Possible causes
Link is present on the card.
Corrective actions
Contact Nortel Networks technical support.

Card
NE-Minor card mismatch
Significance
This alarm occurs when the operator configures a slot for a card type and
2
sub release but inserts a card with a lower sub release.
Instance/Unit
S <slot-no>
Impact
Minor alarm.
Consequent action
None.
Possible causes
Wrong sub release of card in slot
Corrective actions
Replace the card or re-equip the slot for the correct sub-release (see
Provisioning and Operations Procedures, 323-1123-310).

Config
INT NE-Configuration Corrupt Bank
Significance
The configuration data held in the active non volatile configuration bank is
corrupt.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the Configuration Corrupt bank alarm are:
• Non volatile store corruption on the aggregate card.
• Continual cyclic reboots.
Corrective actions
Procedure 2-84
INT-NE_Config_Corrupt_Bank
Step Action
1 Carry out a restore of the configuration bank as detailed in System and Data
Administration Procedures, 323-1123-302.
2 If the alarm is still present, replace the aggregate card. Refer to Maintenance
—end—

Config
INT NE-Configuration All Banks Corrupt
Significance
The configuration data held in both the active and standby non-volatile
2
configuration banks is corrupt.
Instance/Unit
Impact
Major alarm.
Consequent action
The NE enters detached mode.
The following operations are not allowed until the alarm is cleared:
• software upgrade
• configuration changes
• consolidation of the configuration banks
• traffic card provisioning
Possible causes
Possible causes for the Configuration All Banks Corrupt alarm are:
• Non-volatile store corruption on the aggregate card.
Corrective actions
Procedure 2-85
INT-NE_Config_All_Banks_Corrupt
Step Action
1 Carry out a restore of the configuration banks as detailed in System and Data
—end—

Config
INT NE-Configuration Available Bank Corrupt
Significance
This alarm is raised if the data held in the configuration bank is corrupted
during a software upgrade or configuration restore procedure.
Instance/Unit
Impact
Major alarm.
Consequent action
The NE enters detached mode
The following procedures are not allowed until the alarm is cleared:
• software upgrade
• configuration changes
• consolidation of the configuration banks
• a restore of the configuration banks
• traffic card provisioning
Possible causes
Possible causes for the Configuration Available Bank Corrupt alarm are:

Corrective actions
Procedure 2-86
INT NE-Config_Avail_Bank_Corrupt
Step Action 2
1 Display the configuration table status. Access the ‘Admin/cnfg_tbl’ submenu
by selecting
n Admin a
n Cnfg_tbl c
Display the configuration table status by selecting
l View v
2 If the upgrade status is ‘Ready_to_commit’ then go to step 3.

If the upgrade status is ‘Ready_to_activate’ then go to step 4.
3 Execute the Switch to original command by selecting
l Switch_to_original re
A confirmation is required.
4 Execute the backout command by selecting
l Backout bo
5 Restart the software upgrade or configuration restore. Refer to System and

Data Administration Procedures, 313-1123-302.
—end—

Config
INT NE-Configuration Software Mismatch
Significance
The version of software loaded on a card and the version referenced in the
configuration bank are different.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
New card inserted with incorrect software or configuration version.
Corrective actions
Procedure 2-87
INT NE-Cfg_sw_mismatch
Step Action
1 Display the software and configuration table status. Access the ‘Admin/
cnfg_tbl’ submenu by selecting
n Admin a
n Cnfg_tbl c
Display the status by selecting
l View v
2 If the software version is correct carry out step 3. If the software version is
incorrect carry out step 4.
—continued—

Procedure 2-87
INT NE-Cfg_sw_mismatch (continued)
Step Action
3 Consolidate the configuration table. Access the ‘Admin/cnfg_tbl’ submenu by 2

selecting
n Admin a
n Cnfg_tbl c
Consolidate the configuration table status by selecting
l Consolidate c
No confirmation is required.
4 If the alarm is still present, carry out a software download as detailed in
System and Data Administration Procedures, 323-1123-302.
—end—

Config
INT NE-Configuration Audit Mismatch
Significance
A configuration audit indicates that the configuration data in the RAM is
different to the configuration settings on the traffic cards.
Instance/Unit
Impact
Major alarm.
Consequent action
Possible causes
Audit mismatch.
Corrective actions
Procedure 2-88
INT NE-Cfg_Audit_Mismatch
Step Action
1 If the configuration of the traffic cards is correct go to step 2.

2 If the data in the configuration store is correct go to step 3.
3 Manually update the configuration data in the configuration store.
4 Impose the configuration data. Access the ‘Admin/cnfg_tbl’ submenu by
selecting
n Admin a
n Cnfg_tbl c
Execute the impose command by selecting
l Impose_config ic
A confirmation is required.
—end—

Config
INT NE-Configuration Validation Error
Significance
During a restart, a value read from the configuration store is invalid.
2
Instance/Unit
Impact
Major alarm.
Consequent action
Traffic card provisioning is not allowed until the alarm is cleared:
Possible causes
Incorrect software or configuration version.
Corrective actions
Procedure 2-89
INT NE-Cfg_validation_error
Step Action
1 Carry out a restore of the configuration banks as detailed in System and Data
—end—

Config
INT NE-Standby Configuration Software Unstable
Significance
This alarm indicates a problem with the standby software.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Software or configuration problem.
Corrective actions
Perform a backup of the active configuration store to the standby as detailed
in System and Data Administration Procedures, 323-1123-302.

Config
INT NE-Standby Configuration Flash Corrupt
Significance
This alarm indicates a problem with the standby flash memory.
2
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Corruption of the standby non-volatile configuration banks.
Corrective actions

Config
INT NE-Standby Configuration audit mismatch
Significance
The configuration data held in the active non-volatile standby configuration
bank is corrupt.
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Possible causes for the alarm are:
Corrective actions

Config
INT NE-Standby Configuration fail
Significance
The configuration bank on the stand-by aggregate has failed.
2
Instance/Unit
Impact
Major alarm.
Consequent action
None.
Possible causes
Stand-by flash memory is corrupt or the stand-by configuration state is
misaligned with the master aggregate.
Corrective actions

Prot
Equip_Fail
Significance
Raised when a 1+1 protection I/O card fails.
Instance/Unit
This alarm is raised against the working tributary card.
Impact
Major alarm.
Consequent action
None.
Possible causes
Hardware failure on 1+1 protection I/O card.
Corrective actions
Replace the 1+1 protection I/O card. Refer to the Maintenance Procedures,
323-1123-547.

Prot
Equip_Out
Significance
Raised when both the 1+1 working and protection tributary cards detect no
2
connection to the 1+1 protection I/O card.
Instance/Unit
This alarm is raised against the working tributary card.
Impact
Major alarm.
Consequent action
None.
Possible causes
Interface cable between the 1+1 protection I/O card and the tributaries is not
present or is incorrectly connected.
Corrective actions
Check interface cable between the 1+1 protection I/O card and the tributaries.

Prot
Unexpected_Equip
Significance
Raised where the 1+1 I/O card is connected to a tributary card in a protection
slot, but that slot is not in a 1+1 card association.
This alarm is not raised against a card in a working slot.
Instance/Unit
This alarm is raised against a protection tributary card.
Impact
Major alarm.
Consequent action
None.
Possible causes
Card association not made by operator
Corrective actions
Create card association for 1+1 card protection (see Provisioning and

Prot
Cable_Error
Significance
Raised to indicate that a cable fault exists between a tributary slot and a 1+1
2
protection I/O card.
Instance/Unit
This alarm is raised against the working or protection card slot.
Impact
Major alarm.
Consequent action
Protection switch to the other slot in the association.
Possible causes
Fault in the cable between the 1+1 protection I/O card and the tributaries.
The cable from the working or protection card is connected to the wrong port
on the 1+1 protection I/O card.
Corrective actions
Replace the interface cable between the 1+1 protection I/O card and the
tributaries.

Prot
Wrong_Equip
Significance
Raised to indicate a mismatch between a tributary card and a 1+1 protection
I/O card.
Instance/Unit
This alarm is raised against the working or protection card slot.
Impact
Major alarm.
Consequent action
None.
Possible causes
1+1 protection I/O card and the tributaries are not compatible.
Corrective actions
Replace either the 1+1 protection I/O card or the tributaries

MSP
FOP_PAM
Significance
The Failure Of Protocol-Protection Architecture Mismatch alarm raises when
2
the multiplexing equipments at either end of transmission path are using
different protection architectures. For example, the local multiplexer is
operating 1+1 MSP and the remote end is operating 1:N protection.
Instance/Unit
The alarm is raised against bidirectional SDH protection ports.
Impact
Major alarm.
Consequent action
None.
Possible causes
Multiplexing equipment at either end of transmission path are using different
protection architectures.
Corrective actions
Reconfigure equipment to a common protection architecture.

MSP
FOP_SCM
Significance
The Failure Of Protocol-Selector Channel Mismatch alarm is raised to
indicate that a difference exists in the transmitted channel of the K1 byte and
the received channel K2 byte.
Instance/Unit
Impact
Major alarm.
Consequent action
Causes an MSP protection switch.
Possible causes
Possible causes for the FOP_SCM alarm are:
• Indicates a protocol failure.
• Incorrect optical fibre connection between protection and working cards
across the transmission path.
Corrective actions
Ensure optical fibre connections between protection and working cards across
the transmission path are correct.

MSP
FOP_INV
Significance
The Failure Of Protocol-Invalid alarm is raised to indicate that the received
2
K1 byte is invalid.
Instance/Unit
Impact
Major alarm.
Consequent action
This is an signal fail condition so it causes a MSP protection switch.
Possible causes
Possible causes for the FOP_INV alarm are:
• Optical hygiene problem.
Corrective actions
Examine fibre-optic path for hygiene problems and replace local or far end
cards as necessary.

MSP
FOP_TMOUT
Significance
The Failure of protocol-Timeout alarm indicates that the K1 byte has not been
received within the specified 50 ms.
Instance/Unit
Impact
Major Alarm
Consequent action
This is an signal fail condition so it causes a MSP protection switch.
Possible causes
Possible causes for the FOP_TMOUT alarm are:
• Multiplexing equipment at either end of transmission path are using
different protection architectures.
• Incorrect optical fibre connection between protection and working cards
across the transmission path.
Corrective actions
Reconfigure equipment to a common protection architecture or ensure optical
fibre connections between protection and working cards across the
transmission path are correct.
end of chapter

3-1
Index 3- 3
A H
action HP-Excessive errors (EXC) alarm 2-48
log HP-Loss_of_Multiframe (LOM) alarm 2-56
fault clearing 1-2 HPOM-Excessive errors (EXC) alarm 2-71
alarm HP-Path_Label_Mismatch (PLM)
clearing 1-1 alarm 2-59, 2-75
consequent action 1-7 HP-Remote_Defect_Indicator (RDI)
correlation 1-3 alarm 2-54
indications 1-2 HP-Remote_Error_Indicator (REI)
RAU category 1-4 alarm 2-58
severity 1-4 HP-Signal Degrade (DEG) alarm 2-50
AU-Alarm_Indication_Signal (AIS) HP-Signal_Fail (SF) alarm 2-63
alarm 2-45 HP-Trace Identifier Mismatch (TIM) 2-52,
AU-Loss_of_Pointer (LOP) alarm 2-47 2-73
HP-Unequipped alarm 2-61, 2-77
C
Cable_Error alarm 2-173 I
clearing In station (RAU category) 1-6
faultst INT LP-Input Buffer Overflow alarm 2-65,
action log 1-2 2-91
consequent action INT LP-Output Buffer Overflow alarm 2-66,
alarm 1-7 2-93
Critical (alarm severity) 1-6 INT NE-Config_All_Banks_Corrupt
alarm 2-159
D INT NE-Config_Audit_Mismatch
Deferred (RAU category) 1-6 alarm 2-164
INT NE-Config_Available_Bank_Corrupt
alarm 2-160
E INT NE-Config_Bp_Mismatch alarm 2-144
EA-Ext_inp alarm 2-140 INT NE-Config_Corrup_Bank alarm 2-158
Equip_Fail alarm 2-170 INT NE-Config_Corrupt alarm 2-141
Equip_Out alarm 2-171 INT NE-Config_Software_Mismatch
alarm 2-162
F INT NE-Config_Validation_Error
faults alarm 2-165
clearing faults INT NE-Spi_Comms_Fail alarm 2-139
action log 1-2 INT NE-Standby_Config_Audit_Mismatch
alarm 2-168
INT NE-Standby_Config_Fail alarm 2-169

3-2 Index
INT NE-Standby_Config_Flash_Corrupt N
alarm 2-167 NE-Card_Fault alarm 2-154
INT NE-Standby_Config_Sw_Unstable NE-Card_Out alarm 2-149
alarm 2-166 NE-Date_Time_Unknown alarm 2-146
INT TU-Alarm Indication Signal (AIS) NE-Invt_Write_Jumper_Fitted alarm 2-156
alarm 2-81 NE-Lan_Alarm 2-142
INT TU-Loss of Pointer (LOP) alarm 2-82 NE-Unexpected_Card alarm 2-151
NE-Unexpected_LAN alarm 2-143
L NE-Wrong_Card alarm 2-155
LED
card alarms 1-2 O
RAU alarms 1-2 OS alarms 2-11
log OS-Disable_Laser_Shutdown alarm 2-13
action log OS-Laser_Bias_High alarm 2-12
clearing faults 1-2 OS-Laser_Shutdown alarm 2-14
LP-Excessive errors 2-83 OS-Optical_Power_High alarm 2-11
LP-Excessive_Errors (EXC) alarm 2-83
LP-Label Unequipped alarm 2-98, 2-110
LPOM-Excessive_Errors (EXC) alarm 2-104 P
LP-Path Label Mismatch (PLM) alarm 2-86, PPI-Alarm Indication Signal (AIS)
2-108 alarm 2-116
LP-Remote Defect Indicator (RDI) PPI-Excessive errors (EXC) alarm 2-15,
alarm 2-88 2-117
LP-Remote Error Indication (REI) PPI-Loopback On alarm 2-122
alarm 2-90 PPI-Loss Of Frame (LOF) alarm 2-120,
LP-Signal Degrade (DEG) alarm 2-84 2-123
LP-Signal_Fail (SF) alarm 2-95 PPI-Loss Of Multiframe (LOM) alarm 2-121
LP-Trail Indentifier Mismatch (TIM) PPI-Loss Of Signal (LOS) alarm 2-114
alarm 2-96, 2-106 PPI-Signal Degrade (DEG) alarm 2-118
PPI-Transmit Fail (TF) alarm 2-16, 2-112
PPI-Unexpected Signal alarm 2-119
M Prompt (RAU category) 1-6
maintenance PS-Power_Fail alarm 2-145
philosophy 1-1
Major (alarm severity) 1-6
Minor (alarm severity) 1-6 Q
MS-Alarm_Indication_Signal (AIS) Qecc_Comms_Fail alarm 2-136
alarm 2-31
MS-Excessive_Errors (EXC) alarm 2-37 R
MSP FOP_INV alarm 2-177 rack alarm unit (RAU)
MSP FOP_PAM alarm 2-175 alarm category 1-4
MSP FOP_SCM alarm 2-176 alarm indications 1-2
MSP FOP_TMOUT alarm 2-178 RS-Excessive_Errors (EXC) alarm 2-24
MS-Remote_Defect_Indicator (RDI) RS-Loopback_On alarm 2-28
alarm 2-33 RS-Loss_of_Signal (LOS) alarm 2-20
MS-Remote_Error_Indicator (REI) RS-Trace_Identifier_Mismatch (TIM)
alarm 2-35 alarm 2-26
MS-Signal_Degrade (DEG) alarm 2-39 RS-Unexpected_Signal alarm 2-19

Index 3-3
S
Sync-ESO_Source_Not_Primary
alarm 2-128
SYNC-External_Sync_LOS alarm 2-131
Sync-Holdover alarm 2-129
Sync-SETG_Fail alarm 2-126
Sync-SETG_Frequency_Suspect
alarm 2-133
Sync-Source_Not_Primary alarm 2-130
Sync-Unexpected_Signal alarm 2-127 3
T
TU-Alarm_Indication_Signal alarm 2-79
TU-Loss_of_Pointer (LOP) alarm 2-80
U
Unexpected_Equip alarm 2-172
Unexpected_SW_Version alarm 2-147
W
Warning (alarm severity) 1-6
Wrong_Equip alarm 2-174

International Optical Networks
Nortel Networks
Oakleigh Road South
London N11 1HB
So far as Nortel Networks is aware the contents of this document
are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or
undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for
any form of consequential, indirect or special loss, and loss of
data, loss of profits or loss of business opportunity, howsoever
arising and whether sustained by the user of the information
herein or any third party arising out of the contents of this
document.
*
NORTEL NETWORKS, the Nortel Networks logo, the
Globemark, How the World Shares Ideas and Unified Networks
are trademarks of Nortel Networks.
SDH TRANSMISSION
Nortel TN-4XE
Copyright © 1998 - 2000, Nortel Networks, All Rights Reserved.
The copyright of this document is the property of Nortel Networks.
Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or
reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques
available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL:The information
contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel
Networks, the holder shall keep all information contained herein
confidential, shall disclose it only to its employees with a need to
know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses
to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein.
Document Number: 323-1123-543
Product Release Number: Release 3.01
Status: Standard
Date: March 2000
Printed in England

Alrm Clear 4xe31

Uploaded by

Document Information

Original Description:

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

Alrm Clear 4xe31

Uploaded by

Copyright:

Available Formats

323-1123-543

Release 3.01 Standard March 2000

Document Number: 323-1123-543

Copyright © 1998 - 2000 Nortel Networks, All Rights Reserved.

Netscape is a trademark of Netscape Communications Corporation.

Nortel TN-4XE Alarm Clearing Procedures

VT100 is a trademark of Digital Equipment Corporation.

323-1123-543 Release 3.01 Standard

Nortel TN-4XE Alarm Clearing Procedures

323-1123-543 Release 3.01 Standard

Clearing alarms 2-1

Nortel TN-4XE Alarm Clearing Procedures

MS-Quality of service violation (24 hour) 2-42

Release 3.01 Standard

PPI PPI- Transmit-Loss of Frame (T-LOF) 2-123

Nortel TN-4XE Alarm Clearing Procedures

Figure 1-1 RAU indicators on the Upper EOS card 1-3

Release 3.01 Standard

Procedure 2-50 INT-LP-IP-BUFFER alarm clearing 2-92

Nortel TN-4XE Alarm Clearing Procedures

About this document

Nortel TN-4XE Alarm Clearing Procedures

Technical support and information

Nortel Networks provides a comprehensive technical support service for it’s

323-1123-543 Release 3.01 Standard

Product Name Product Type

Section 2 - Standards Applied

Stds Standard Number Edition Amendments Subject of Standard

Section 3 - European Union Directives

Directive Abbreviated Directive Title Stds CE Marking

Section 4 - Authority of Issuer

Declaration Issued By: Peter Schuddeboom John Freebairn

Position of Issuer: VP, ION Product Development Senior Manager, Customer

The maintenance philosophy is to identify the source of a fault without the

Alarms and action logs descriptions are in the System Description,

Nortel TN-4XE Alarm Clearing Procedures

Response to action logs

Often, log messages require no action by the maintenance personnel.

The Network Surveillance Procedures, 323-1123-510 lists and describes logs

Defect detection and alarm reporting

Traffic cards LEDs

EOS cards LEDs

Rack alarm unit (RAU) indications on the subrack

323-1123-543 Release 3.01 Standard

ALARM RAU indicators

Correlation (fault masking)

Each alarm in the correlation process has a position in a correlation hierarchy

Card alarm correlation

Nortel TN-4XE Alarm Clearing Procedures

Equipment Alarms Card Alarms

Card Fault Card Fail Wrong Card Unexpected Card

Any alarm raised on the Card/Slot instance

Traffic and BER alarms correlation

Alarm severity and RAU category

323-1123-543 Release 3.01 Standard

RS TIM MS RDI RS COMMS FAIL MS COMMS FAIL

MS DEG AU LOP FOP_PAM FOP_SCM FOP_INV

HPOM TIM HPOM PLM HPOM UNEQ HP-EXC

INT HP OP BUFF HP RDI HP LOM HP TIM HP PLM HP UNEQ HP DEG

PPI LOF-T HP REI TU LOP

INT TU LOP LPOM EXC

INT TU AIS LPOM TIM LPOM PLM LPOM UNEQ

LP RDI INT LP OP BUFF LP TIM LP PLM LP UNEQ LP DEG