OM4200 Alarm Clearing Procedures

323-1233-543
323-1233-543
SDH TRANSMISSION
Nortel Networks Optical Metro

4200 Multiservice Platform
Alarm Clearing Procedures
Release 4.1 Standard April 2004
SDH TRANSMISSION
Nortel Networks Optical Metro 4200

Multiservice Platform
Document Number: 323-1233-543

Product Release Number: Release 4.1
Status: Standard
Date: April 2004
Copyright © 2004 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.
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, and Unified Networks are trademarks of Nortel Networks.
Netscape is a trademark of Netscape Communications Corporation.

OPTERA is a trademark of Cambrian Systems Inc.
Optical Metro 4200 Alarm Clearing Procedures

iii
Publication history
April 2004
Release 4.1 Standard introduces the following features:
• General robustness improvements
• Connection restriction removal
• Port Alarm Monitoring improvements
November 2002
Release 4 Standard introduces the following features:
• Single fibre working using STM-16o long haul aggregates NTEU25DG
and NTEU25DO
• Ultra long haul STM-16o aggregate cards NTEU25GN and NTEU25GO
• STM-1o long haul tributary card NTEU10AB
• STM-4o long haul tributary card NTEU15AB
• Amplified spans on STM-16 aggregate card NTEU25DO
• Amplified spans on STM-1o and STM-4o long haul tributary cards
NTEU10AB and NTEU15AB
• Intermediate path performance monitoring (IPPM)
May 2002
Release 3.5 Preliminary introduces the following features:
• STM-1e only tributary card NTEU16AA
• Port Alarm Monitoring available on a per port basis, allows all alarms to
be masked or suppressed
• Accomodates up to eight 10/100 Mbit/s Ethernet OPTera Packet Edge
100 (OPE100) cards. Each card gas eight Ethernet ports and two WAN
(POS) ports.
• The OPE100 card provides Ethernet bridging capability to the OM4200
SDH network
March 2002
Release 3.1 Standard introduces the following features:
• Quad STM-1o tributary card, short haul 1310 nm

iv
• 1+1 Multiplex Section Protection for Quad STM-1o

• In-service reconfiguration of STM-1o tributary card to Quad STM-1o
tributary card
• TCP/IP from EC-1 to Head-end multiplexer
and in addition incorporates the following features from Release 3.0
Preliminary B:
• Quad STM-1e tributary card NTEU16QA

• Quad STM-1e Protection I/O card NTEU81QA
• 1+1 Multiplex Section Protection for Quad STM-1e
• 1+1 Card Protection for Quad STM-1e
• VC-4-Nc concatenated payloads
• In-service reconfiguration of STM-1e/140 Mbit/s tributary card to Quad
STM-1e tributary card
February 2001
Release 2 Standard introduces the following OM4200 features:
• STM-4o tributary card, short haul 1310 nm
• Multiplexer Section Protection for STM-4o tributary cards
• Aggregate and Trib to Trib connection
• Intermediate System to Intermediate System Level 2 routing
October 2000
Release 1 Standard introduces the following OM4200 features:
• STM-16o aggregate card, long haul 1539 nm and short haul 1310 nm
• STM-1o tributary card, short haul 1310 nm with two STM-1 ports
• STM-1e/140Mbit/s, single channel, tributary card
• Three channel, 34/45Mbit/s PDH electrical tributary card
• 32 channel, 2Mbit/s PDH electrical tributary cards (75 ohm and 120 ohm)
• Multiplex section protection for STM-1 tributary cards and STM-16
aggregate cards
• 1+1 protection for 34/45Mbit/s and STM-1e/140Mbit/s tributaries
• Performance monitoring to G.826
• SETS (synchronisation function) and SEMF (Shelf Controller function)
redundancy
• VC-4, VC-3 and VC-12 connections with path protection
323-1233-543 Release 4.1 Standard

v
Contents
About this document xxix
Introduction 1-1
Card LEDs 1-3
Rack alarm unit (RAU) indications on the subrack 1-3
Card alarm correlation 1-4
Traffic and BER alarms correlation 1-5
Alarm severity states 1-7
RAU categories 1-7
Port Alarm Monitoring 1-8
Clearing alarms 2-1
OS-Optical Power High 2-12

Significance 2-12
Instance/Unit 2-12
Impact 2-12
Consequent Action 2-12
Possible causes 2-12
Corrective actions 2-12
OS-Disabled Laser Shutdown 2-13

Significance 2-13
Instance/Unit 2-13
Impact 2-13
OS-Laser Shutdown 2-14

Significance 2-14
Instance/Unit 2-14
Impact 2-14
ES-Coded mark inversion violation 2-15

Significance 2-15
Instance/Unit 2-15
Impact 2-15

vi Contents
ES-Transmit Fail (TF) 2-17

Significance 2-17
Instance/Unit 2-17
Impact 2-17
ES-Code violation quality of service violation

(15 minute) 2-18
Significance 2-18
Instance/Unit 2-18
Impact 2-18

(24 hour) 2-19
Significance 2-19
Instance/Unit 2-19
Impact 2-19
RS-Unexpected signal 2-20

Significance 2-20
Instance/Unit 2-20
Impact 2-20
RS-Loss of Signal (LOS) 2-21

Significance 2-21
Instance/Unit 2-21
Impact 2-21
RS-Loss of Frame (LOF) 2-23

Significance 2-23
Instance/Unit 2-23
Impact 2-23
RS-Trace Identifier Mismatch (TIM) 2-25

Significance 2-25

Contents vii
Instance/Unit 2-25
Impact 2-25
RS-Loopback On 2-27
Significance 2-27
Instance/Unit 2-27
Impact 2-27
RS-Quality of service violation (15 minute) 2-28

Significance 2-28
Instance/Unit 2-28
Impact 2-28
RS-Quality of service violation (24 hour) 2-29

Significance 2-29
Instance/Unit 2-29
Impact 2-29
MS-Alarm Indication Signal (AIS) 2-30

Significance 2-30
Instance/Unit 2-30
Impact 2-30
MS-Remote Defect Indicator (RDI) 2-32

Significance 2-32
Instance/Unit 2-32
Impact 2-32
MS-Remote Error Indicator (REI) 2-34

Significance 2-34
Instance/Unit 2-34
Impact 2-34
MS-Excessive errors (EXC) 2-36

viii Contents
Significance 2-36
Instance/Unit 2-36
Impact 2-36
MS-Signal Degrade (DEG) 2-38

Significance 2-38
Instance/Unit 2-38
Impact 2-38
MS-Quality of service violation (15 minute) 2-40

Significance 2-40
Instance/Unit 2-40
Impact 2-40
MS-Quality of service violation (24 hour) 2-41

Significance 2-41
Instance/Unit 2-41
Impact 2-41
MS-Far end quality of service violation (15 minute) 2-42

Significance 2-42
Instance/Unit 2-42
Impact 2-42
MS-Far end quality of service violation (24 hour) 2-43

Significance 2-43
Instance/Unit 2-43
Impact 2-43
AU-Alarm Indication Signal (AIS) 2-44

Significance 2-44
Instance/Unit 2-44
Impact 2-44

Contents ix
AU-Loss of Pointer (LOP) 2-46

Significance 2-46
Instance/Unit 2-46
Impact 2-46
HP-Excessive errors (EXC) 2-47

Significance 2-47
Instance/Unit 2-47
Impact 2-47
HP-Signal Degrade (DEG) 2-49

Significance 2-49
Instance/Unit 2-49
Impact 2-49
HP-Trace Identifier Mismatch (TIM) 2-51

Significance 2-51
Instance/Unit 2-51
Impact 2-51
HP-Remote Defect Indicator (RDI) 2-53

Significance 2-53
Instance/Unit 2-53
Impact 2-53
HP-Loss of Multiframe (LOM) 2-55

Significance 2-55
Instance/Unit 2-55
Impact 2-55
HP-Remote Error Indicator (REI) 2-57

Significance 2-57
Instance/Unit 2-57
Impact 2-57

x Contents
HP-Payload Label Mismatch (PLM) 2-59

Significance 2-59
Instance/Unit 2-59
Impact 2-59
HP-Unequipped (UNEQ) 2-61

Significance 2-61
Instance/Unit 2-61
Impact 2-61
HP-Signal Fail (SF) 2-63

Significance 2-63
Instance/Unit 2-63
Impact 2-63
INT-HP-Input Buffer Overflow 2-65

Significance 2-65
Instance/Unit 2-65
Impact 2-65
INT HP-Output Buffer Overflow 2-67

Significance 2-67
Instance/Unit 2-67
Impact 2-67
HP-Quality of service violation (15 minute) 2-69

Significance 2-69
Instance/Unit 2-69
Impact 2-69
HP-Quality of service violation (24 hour) 2-70

Significance 2-70
Instance/Unit 2-70
Impact 2-70

Contents xi
HP-Far end quality of service violation (15 minute) 2-71

Significance 2-71
Instance/Unit 2-71
Impact 2-71
HP-Far end quality of service violation (24 hour) 2-72

Significance 2-72
Instance/Unit 2-72
Impact 2-72
HPOM quality of service violation

(15 minute) 2-73
Significance 2-73
Instance/Unit 2-73
Impact 2-73

(24 hour) 2-74
Significance 2-74
Instance/Unit 2-74
Impact 2-74
HPOM-far end quality of service violation (15 minute) 2-75

Significance 2-75
Instance/Unit 2-75
Impact 2-75
HPOM-far end quality of service violation

(24 hour) 2-76
Significance 2-76
Instance/Unit 2-76
Impact 2-76
HPOM-Excessive errors (EXC) 2-77

Significance 2-77
Instance/Unit 2-77

xii Contents
Impact 2-77
HPOM-Trace Identifier Mismatch (TIM) 2-79

Significance 2-79
Instance/Unit 2-79
Impact 2-79
HPOM-Payload Label Mismatch (PLM) 2-81

Significance 2-81
Instance/Unit 2-81
Impact 2-81
HPOM-Unequipped (UNEQ) 2-83

Significance 2-83
Instance/Unit 2-83
Impact 2-83
TU-Alarm Indication Signal (AIS) 2-85

Significance 2-85
Instance/Unit 2-85
Impact 2-85
TU-Loss of Pointer (LOP) 2-86

Significance 2-86
Instance/Unit 2-86
Impact 2-86
INT-TU-Alarm Indication Signal (AIS) 2-87

Significance 2-87
Instance/Unit 2-87
Impact 2-87
INT-TU-Loss of Pointer (LOP) 2-88

Significance 2-88

Contents xiii
Instance/Unit 2-88
Impact 2-88
LP-Excessive errors (EXC) 2-89

Significance 2-89
Instance/Unit 2-89
Impact 2-89
LP-Signal Degrade (DEG) 2-91

Significance 2-91
Instance/Unit 2-91
Impact 2-91
LP-Payload Label Mismatch (PLM) 2-93

Significance 2-93
Instance/Unit 2-93
Impact 2-93
LP-Remote Defect Indicator (RDI) 2-95

Significance 2-95
Instance/Unit 2-95
Impact 2-95
LP-Remote Error Indication (REI) 2-97

Significance 2-97
Instance/Unit 2-97
Impact 2-97
INT-LP-Input Buffer Overflow 2-98

Significance 2-98
Instance/Unit 2-98
Impact 2-98
INT LP-Output Buffer Overflow 2-100

xiv Contents
Significance 2-100
Instance/Unit 2-100
Impact 2-100
LP-Signal Fail (SF) 2-102

Significance 2-102
Instance/Unit 2-102
Impact 2-102
LP-Trail Identifier Mismatch (TIM) 2-103

Significance 2-103
Instance/Unit 2-103
Impact 2-103
LP-Label Unequipped 2-105

Significance 2-105
Instance/Unit 2-105
Impact 2-105
LP-Quality of service violation (15 minute) 2-107

Significance 2-107
Instance/Unit 2-107
Impact 2-107
LP-Quality of service violation (24 hour) 2-108

Significance 2-108
Instance/Unit 2-108
Impact 2-108
LP-Far end quality of service violation (15 minute) 2-109

Significance 2-109
Instance/Unit 2-109
Impact 2-109

Contents xv
LP-Far end quality of service violation (24 hour) 2-111

Significance 2-111
Instance/Unit 2-111
Impact 2-111
LPOM - quality of service violation

(15 minute) 2-112
Significance 2-112
Instance/Unit 2-112
Impact 2-112

(24 hour) 2-113
Significance 2-113
Instance/Unit 2-113
Impact 2-113
LPOM-Excessive Errors (EXC) 2-114

Significance 2-114
Instance/Unit 2-114
Impact 2-114
LPOM-Trail Identifier Mismatch (TIM) 2-116

Significance 2-116
Instance/Unit 2-116
Impact 2-116
LPOM-Payload Label Mismatch (PLM) 2-118

Significance 2-118
Instance/Unit 2-118
Impact 2-118
LPOM-Label Unequipped (UNEQ) 2-120

Significance 2-120
Instance/Unit 2-120
Impact 2-120

xvi Contents

PPI-Transmit Fail (TF) 2-122

Significance 2-122
Instance/Unit 2-122
Impact 2-122
PPI-Loss Of Signal (LOS) 2-124

Significance 2-124
Instance/Unit 2-124
Impact 2-124
PPI-Alarm Indication Signal (AIS) 2-126

Significance 2-126
Instance/Unit 2-126
Impact 2-126
PPI-Excessive errors (EXC) 2-127

Significance 2-127
Instance/Unit 2-127
Impact 2-127
PPI-Signal Degrade (DEG) 2-128

Significance 2-128
Instance/Unit 2-128
Impact 2-128
PPI-Unexpected Signal 2-129

Significance 2-129
Instance/Unit 2-129
Impact 2-129
PPI-Loss of Frame (LOF) 2-130

Significance 2-130
Instance/Unit 2-130

Contents xvii
Impact 2-130
PPI-Loss of Multiframe (LOM) 2-131

Significance 2-131
Instance/Unit 2-131
Impact 2-131
PPI-Loopback On 2-132
Significance 2-132
Instance/Unit 2-132
Impact 2-132
PPI- Transmit-Loss of Frame (T-LOF) 2-133

Significance 2-133
Instance/Unit 2-133
Impact 2-133
PPI-Code violation Quality of service violation

(15 minute) 2-134
Significance 2-134
Instance/Unit 2-134
Impact 2-134
PPI-Code violation-Quality of service violation

(24 hour) 2-135
Significance 2-135
Instance/Unit 2-135
Impact 2-135
Sync-SETG Fail 2-136

Significance 2-136
Instance/Unit 2-136
Impact 2-136

xviii Contents
Sync-Unexpected signal 2-137

Significance 2-137
Instance/Unit 2-137
Impact 2-137
Sync-ESO Source Not Primary 2-138

Significance 2-138
Instance/Unit 2-138
Impact 2-138
Sync-SETG Holdover 2-139

Significance 2-139
Instance/Unit 2-139
Impact 2-139
Sync-Source Not Primary 2-140

Significance 2-140
Instance/Unit 2-140
Impact 2-140
Sync-External Sync Loss Of Signal 2-141

Significance 2-141
Instance/Unit 2-141
Impact 2-141
Sync-Source out of limits 2-143

Significance 2-143
Instance/Unit 2-143
Impact 2-143
Qecc Comms Fail 2-144

Significance 2-144
Instance/Unit 2-144
Impact 2-144

Contents xix
INT NE-Spi Comms Fail 2-147

Significance 2-147
Instance/Unit 2-147
Impact 2-147
EA-Ext inp <1-8> 2-148

Significance 2-148
Instance/Unit 2-148
Impact 2-148
EA-Ext out <1-5> 2-149

Significance 2-149
Instance/Unit 2-149
Impact 2-149
INT NE-Configuration Corrupt 2-150

Significance 2-150
Instance/Unit 2-150
Impact 2-150
NE-Lan Alarm 2-151

Significance 2-151
Instance/Unit 2-151
Impact 2-151
NE-Unexpected LAN 2-152

Significance 2-152
Instance/Unit 2-152
Impact 2-152
INT NE-Config bp mismatch 2-153

Significance 2-153
Instance/Unit 2-153
Impact 2-153

xx Contents
Ps-power fail 2-154

Significance 2-154
Instance/Unit 2-154
Impact 2-154
NE-Date time unknown 2-155

Significance 2-155
Instance/Unit 2-155
Impact 2-155
Unexpected SW version 2-156

Significance 2-156
Instance/Unit 2-156
Impact 2-156
Internal 1 second clock loss of signal 2-157

Significance 2-157
Instance/Unit 2-157
Impact 2-157
NE-Card Out 2-158

Significance 2-158
Instance/Unit 2-158
Impact 2-158
NE-Unexpected Card 2-160

Significance 2-160
Instance/Unit 2-160
Impact 2-160
INT-NE-HBEAT_Missing 2-162
Significance 2-162
Instance/Unit 2-162
Impact 2-162

Contents xxi
NE-Card Fault 2-163

Significance 2-163
Instance/Unit 2-163
Impact 2-163
NE-Wrong Card 2-164

Significance 2-164
Instance/Unit 2-164
Impact 2-164
NE-Invt Write Jumper Fitted 2-165

Significance 2-165
Instance/Unit 2-165
Impact 2-165
NE-Minor card mismatch 2-166

Significance 2-166
Instance/Unit 2-166
Impact 2-166
INT NE-Configuration Corrupt Bank 2-167

Significance 2-167
Instance/Unit 2-167
Impact 2-167
INT NE-Configuration All Banks Corrupt 2-168

Significance 2-168
Instance/Unit 2-168
Impact 2-168
INT NE-Configuration Available Bank Corrupt 2-169

Significance 2-169
Instance/Unit 2-169
Impact 2-169

xxii Contents
INT NE-Configuration Software Mismatch 2-171

Significance 2-171
Instance/Unit 2-171
Impact 2-171
INT NE-Configuration Audit Mismatch 2-173

Significance 2-173
Instance/Unit 2-173
Impact 2-173
INT NE-Configuration Validation Error 2-175

Significance 2-175
Instance/Unit 2-175
Impact 2-175
INT NE-Standby Configuration Software Unstable 2-176

Significance 2-176
Instance/Unit 2-176
Impact 2-176
INT NE-Standby Configuration Flash Corrupt 2-177

Significance 2-177
Instance/Unit 2-177
Impact 2-177
INT NE-Standby Configuration audit mismatch 2-178

Significance 2-178
Instance/Unit 2-178
Impact 2-178
INT NE-Standby Configuration fail 2-179

Significance 2-179
Instance/Unit 2-179
Impact 2-179

Contents xxiii
Equip_Fail 2-180
Significance 2-180
Instance/Unit 2-180
Impact 2-180
Equip_Out 2-181
Significance 2-181
Instance/Unit 2-181
Impact 2-181
Unexpected_Equip 2-182
Significance 2-182
Instance/Unit 2-182
Impact 2-182
Cable_Error 2-183
Significance 2-183
Instance/Unit 2-183
Impact 2-183
Wrong_Equip 2-184
Significance 2-184
Instance/Unit 2-184
Impact 2-184
FOP_PAM 2-185
Significance 2-185
Instance/Unit 2-185
Impact 2-185
FOP_SCM 2-186
Significance 2-186
Instance/Unit 2-186
Impact 2-186

xxiv Contents
FOP_INV 2-187
Significance 2-187
Instance/Unit 2-187
Impact 2-187
FOP_TMOUT 2-188
Significance 2-188
Instance/Unit 2-188
Impact 2-188
NE_Config_Bp_Mismatch 2-189
Significance 2-189
Instance/Unit 2-189
Impact 2-189
NE_Cfg_Corrupt_Bank 2-190
Significance 2-190
Instance/Unit 2-190
Impact 2-190
NE_Cfg_All_Banks_Corrupt 2-191
Significance 2-191
Instance/Unit 2-191
Impact 2-191
NE_Cfg_Validation_Err 2-192
Significance 2-192
Instance/Unit 2-192
Impact 2-192
NE_Cfg_SW_Mismatch 2-193
Significance 2-193
Instance/Unit 2-193
Impact 2-193

Contents xxv
VC-EDD 2-194
Significance 2-194
Instance/Unit 2-194
Impact 2-194
HP-SIM 2-195
Significance 2-195
Instance/Unit 2-195
Impact 2-195
INT-NE-IP_Subnet_Unknown 2-196
Significance 2-196
Instance/Unit 2-196
Impact 2-196
2-197
Amplifier alarm conditions 2-197
Corrective action 2-197
Index 3-1
Figures
Figure 1-1 RAU indicators on the Upper EOS card 1-4
Figure 1-2 Card Alarm Correlation hierarchy 1-5
Figure 1-3 Traffic and BER alarm correlation hierarchy 1-6
Figure 1-4 Hierarchy of alarm correlation for PDH traffic 1-7
Tables
Table 2-1 Possible alarm instances 2-11
Table 2-2 Optical amplifier alarms 2-197
Procedures
Procedure 2-1 Es-cmi-violation alarm clearing 2-16
Procedure 2-2 ES_TF alarm clearing 2-17
Procedure 2-3 Es_cv_qosv_15M alarm clearing 2-18
Procedure 2-4 ES-CV-QOSV-24H alarm clearing 2-19
Procedure 2-5 Rs-los alarm clearing 2-22
Procedure 2-6 Rs_lof alarm clearing 2-24
Procedure 2-7 Rs-tim alarm clearing 2-26
Procedure 2-8 Rs_qosv_15M alarm clearing 2-28
Procedure 2-9 Rs_qosv_24H alarm clearing 2-29
Procedure 2-10 MS-AIS alarm clearing 2-31
Procedure 2-11 MS-RDI alarm clearing 2-33
Procedure 2-12 MS-REI alarm clearing 2-35
Procedure 2-13 MS-EXC alarm clearing 2-37

xxvi Contents
Procedure 2-14 MS_DEG alarm clearing 2-39

Procedure 2-15 Ms_qosv_15M alarm clearing 2-40
Procedure 2-16 Ms_qosv_24H alarm clearing 2-41
Procedure 2-17 Ms_fe_qosv_15M alarm clearing 2-42
Procedure 2-18 Ms_fe_qosv_24H alarm clearing 2-43
Procedure 2-19 AU-AIS alarm clearing 2-45
Procedure 2-20 AU-LOP alarm clearing 2-46
Procedure 2-21 HP-EXC alarm clearing 2-48
Procedure 2-22 HP-DEG alarm clearing 2-50
Procedure 2-23 HP-TIM alarm clearing 2-52
Procedure 2-24 HP-RDI alarm clearing 2-54
Procedure 2-25 HP-LOM alarm clearing 2-56
Procedure 2-26 HP-REI alarm clearing 2-58
Procedure 2-27 HP-PLM alarm clearing 2-60
Procedure 2-28 HP-UNEQ alarm clearing 2-62
Procedure 2-29 HP-SF alarm clearing 2-64
Procedure 2-30 INT-HP-IP-BUFFER alarm clearing 2-66
Procedure 2-31 INT-HP-OP-BUFFER alarm clearing 2-68
Procedure 2-32 Hp_qosv_15M alarm clearing 2-69
Procedure 2-33 Hp_qosv_24H alarm clearing 2-70
Procedure 2-34 Hp_fe_qosv_15M alarm clearing 2-71
Procedure 2-35 Hp_fe_qosv_24H alarm clearing 2-72
Procedure 2-36 HPOM_QOSV_15M alarm clearing 2-73
Procedure 2-37 HPOM_QOSV_24H alarm clearing 2-74
Procedure 2-38 HPOM-FE_QOSV_15M alarm clearing 2-75
Procedure 2-39 HPOM_FE_QOSV_24H alarm clearing 2-76
Procedure 2-40 HPOM-EXC alarm clearing 2-78
Procedure 2-41 HPOM-TIM alarm clearing 2-80
Procedure 2-42 HPOM-PLM alarm clearing 2-82
Procedure 2-43 HPOM-UNEQ alarm clearing 2-84
Procedure 2-44 TU-AIS alarm clearing 2-85
Procedure 2-45 TU-LOP alarm clearing 2-86
Procedure 2-46 INT-TU-AIS alarm clearing 2-87
Procedure 2-47 INT-TU-LOP alarm clearing 2-88
Procedure 2-48 LP-EXC alarm clearing 2-90
Procedure 2-49 LP-DEG alarm clearing 2-92
Procedure 2-50 LP-PLM alarm clearing 2-94
Procedure 2-51 LP-RDI alarm clearing 2-96
Procedure 2-52 LP-REI alarm clearing 2-97
Procedure 2-53 INT-LP-IP-BUFFER alarm clearing 2-99
Procedure 2-54 INT-LP-OP-BUFFER alarm clearing 2-101
Procedure 2-55 LP-SF alarm clearing 2-102
Procedure 2-56 LP-TIM alarm clearing 2-104
Procedure 2-57 LP-UNEQ alarm clearing 2-106
Procedure 2-58 Lp_qosv_15M alarm clearing 2-107
Procedure 2-59 Lp_qosv_24H alarm clearing 2-108
Procedure 2-60 Hp_fe_qosv_15M alarm clearing 2-110
Procedure 2-61 Lp_fe_qosv_24H alarm clearing 2-111
Procedure 2-62 LPOM_QOSV_15M alarm clearing 2-112
Procedure 2-63 LPOM_QOSV_24H alarm clearing 2-113
Procedure 2-64 LPOM-EXC alarm clearing 2-115
Procedure 2-65 LPOM-TIM alarm clearing 2-117
Procedure 2-66 LPOM-PLM alarm clearing 2-119
Procedure 2-67 LPOM-UNEQ alarm clearing 2-121
Procedure 2-68 PPI-TF alarm clearing 2-123

Contents xxvii
Procedure 2-69 PPI-LOS alarm clearing 2-125

Procedure 2-70 PPI-EXC alarm clearing 2-127
Procedure 2-71 PPI-DEG alarm clearing 2-128
Procedure 2-72 PPI-UNEXP_SIGNAL alarm clearing 2-129
Procedure 2-73 PPI-LOF alarm clearing 2-130
Procedure 2-74 PPI-LOM alarm clearing 2-131
Procedure 2-75 PPI-T-LOF alarm clearing 2-133
Procedure 2-76 PPI_CV_qosv_15M alarm clearing 2-134
Procedure 2-77 PPI_CV_qosv_24H alarm clearing 2-135
Procedure 2-78 SYNC-SETG_Fail alarm clearing 2-136
Procedure 2-79 SYNC-Ext_Sync_LOS alarm clearing 2-142
Procedure 2-80 SYNC-SOURCE-OUT-OF-LIMITS alarm clearing 2-143
Procedure 2-81 Qecc_Comms_Fail alarm clearing 2-145
Procedure 2-82 Spi-Comms_Fail alarm clearing 2-147
Procedure 2-83 NE-Card_Out alarm clearing 2-159
Procedure 2-84 NE-Unexpected_Card alarm clearing 2-161
Procedure 2-85 INT-NE-HBEAT_Missing alarm clearing 2-162
Procedure 2-86 NE-Wrong_Card alarm clearing 2-164
Procedure 2-87 INT-NE_Config_Corrupt_Bank 2-167
Procedure 2-88 INT-NE_Config_All_Banks_Corrupt 2-168
Procedure 2-89 INT NE-Config_Avail_Bank_Corrupt 2-170
Procedure 2-90 INT NE-Cfg_sw_mismatch 2-171
Procedure 2-91 INT NE-Cfg_Audit_Mismatch 2-174
Procedure 2-92 INT NE-Cfg_validation_error 2-175

xxix
About this document

This document contains procedures to locate and clear alarm indications on
the Optical Metro 4200 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-1233-090
• System Description, 323-1233-100
• Software and Hardware Description, 323-1233-101
• Installation Procedures, 323-1233-201
• Provisioning and Operations Procedures, 323-1233-310
• Network Surveillance Procedures, 323-1233-510
• Maintenance Procedures, 323-1233-547
• EC-1 User Procedures, 323-1091-402

xxx
Technical support and information

As far as Nortel Networks knows, the information in this document is correct.
If, however, you discover any errors or have comments about the
arrangement of the content, send details by email to:
IONNTPS@nortelnetworks.com
Nortel Networks provides a full technical support service for its customers.
The Nortel Networks Service Desk can be called at any time on the following
numbers:
Within Europe: Freephone 00800 8008 9009
Outside of Europe: +44 20 8920 4618
As an option, you can contact technical support through the Nortel Networks
web site:
www.nortelnetworks.com
and by selecting Customer Support/help/contact/global
EMC/Safety conformance
This product/product family complies with the essential protection re-
quirements 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: 7
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

Optical Metro 4150 STM4/16 Add Drop SDH Multiplexer system;
Optical Metro 4200 permissable configurations which use subrack
assembly (NTEU70AA) and 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 300 386-2 1997 Telecom Network Equipment:
Product Family Standard
2 EN 60950 1992 1,2,3 & 4 Safety of IT equipment
2 EN 60825-1 1994 11 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,2 n/a
92/31/EEC Amendment to EMC Directive 1,2 n/a
93/68/EEC CE Marking Amending Directive n/a n/a
Section 4 - Authority of Issuer

Declaration Issued By: Stephen Lusty John Freebairn
Position of Issuer: Belfast Lab Leader Leader, 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 NE and the Element Controller (EC-1) or CAT. The NE 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-1233-100.
Alarm clearing
To locate and clear a fault in a NE 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-1233-090.

1-2 Introduction
CAUTION
Risk of traffic interruption
The 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.
4. Some of the alarm clearing procedures in Chapter 2 require an internal

loopback to be applied on an STM-N optical port. If it is not possible to
apply an internal loopback, then apply an extenal physical loopback to the
port using an optical patch cord. For the STM-16 optical ports on the
STM-16 aggregate cards, ensure that a 15dB optical attenuator is inserted
between the transmit and receive connectors.
CAUTION
Risk of optical overload and damage to equipment
For STM-16 Long Haul and Short Haul aggregate cards
external loopback connections, ensure that the received
optical power does not exceed the optical overload level, by
installing a 15dB optical attenuator between the transmit
output and receive input.
Response to action logs

Action logs are information messages that the Network Element or the EC
generate for a span of control that includes the 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-1233-510 lists and describes logs

in detail.
Temporary alarms while provisioning connections

When connections are initially made, temporary alarms will occur. These
alarms are raised because it is not possible to set-up two connections at
exactly the same time.
When one connection is established before the other, the first connection
raises a temporary alarm. The alarm clears once the second connection is
established and carrying clean traffic.
The nature of alarms being raised depends upon the connections and card
types used during set-up.

Introduction 1-3
Defect detection and alarm reporting 1

The NE 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-1233-101.
Traffic cards LEDs

The LEDs on the traffic cards are:
• the Fail LED (red) indicates a card fault, 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.
Note: This is not the case if the card is providing protection in a 1+1 or
MSP configuration.
• 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.

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

When the NE 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.

Introduction 1-5
Figure 1-2
Card Alarm Correlation hierarchy
1
Equipment Alarms Card Alarms
Card Fault Card Fault 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 all alarms except OS-Optical_
Power_High and PS-Power Fail. If the operator changes the RAU category
for an alarm the alarm severity also changes automatically.

1-6 Introduction
Figure 1-3
Traffic and BER alarm correlation hierarchy
RS LOS RS UNEXP SGNL
ES CMI
RS LOF
RS TIM MS RDI QECC COMMS FAIL
MS AIS
MS REI
MS EXC
MS DEG AU LOP FOP_PAM FOP_SCM FOP_INV FOP_TMOUT
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

= HP-LOM masks VC-12 TU alarms

Introduction 1-7
Figure 1-4
Hierarchy of alarm correlation for PDH traffic
1
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
fault 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.

1-8 Introduction
Port Alarm Monitoring

The Port Alarm Monitoring feature, which is available on a per port basis,
allows all alarms to be masked, or suppressed. For further details on this
feature refer to Chapter 7 ’Alarm Management Procedures’, of the
Provisioning & Operations (323-1233-310) handbook.
Consequent actions and alarms

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 (PPS)
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 for the alarm type instance
• the alarm type consequent action is enabled
• the NE wide alarm type consequent action is enabled
Refer to Provisioning and Operations Procedures, 323-1233-310 for the
procedures to configure consequent actions.
Details of the consequent actions for each alarm are in Chapter 2.

2-1
2
Clearing alarms 2-
This chapter describes how to locate and clear alarms on the NE subrack.
Note: Some of the alarm clearing procedures that follow require a

loopback to be carried out as part of the Corrective Actions. Do not apply
a loopback for a tributary selected as the active synchronisation source
otherwise the multiplexer will lose synchronisation.
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-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-17
es-code violation-quality of service es_cv_qosv_15M 2-18

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

violation 24 hour

2-2 Clearing alarms
Regenerator section alarms
RS-Unexpected signal Rs_unexp_signal 2-20
RS-Loss of Signal (LOS) Rs_los 2-21
RS-Loss of Frame (LOF) Rs_lof 2-23
RS-Trace Identifier Mismatch (TIM) Rs_tim 2-25
RS-Loopback On Rs_loopback_on 2-27
RS-quality of service violation 15 minute RS_qosv_15M 2-28
RS-quality of service violation 24 hour RS_qosv_24H 2-29
Note: The RS-Loss of Signal (LOS) alarm can be masked using the Port
Alarm Monitoring feature. For details on this feature refer to Chapter 7 of
the Provisioning and Operations Procedures, 323-1233-310 handbook.
Multiplexer section alarms
MS-Alarm Indication Signal (AIS) Ms_ais 2-30
MS-Remote Defect Indicator (RDI) Ms_rdi 2-32
MS-Remote Error Indicator (REI) Ms_rei 2-34
MS-Excessive errors (EXC) Ms_exc 2-36
MS-Signal Degrade (DEG) Ms_deg 2-38
MS-quality of service violation 15 minute Ms_qosv_15M 2-40
MS-quality of service violation 24 hour Ms_qosv_24H 2-41
MS-far end quality of service violation 15 Ms_fe_qosv_15M 2-42

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

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

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

2
HP-Signal Degrade (DEG) Hp_deg 2-49
HP-Trace Identifier Mismatch (TIM) Hp_tim 2-51
HP-Remote Defect Indicator (RDI) Hp_rdi 2-53
HP-Loss of Multiframe (LOM) Hp_lom 2-55
HP-Remote Error Indicator (REI) Hp_rei 2-57
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-67
HP-quality of service violation 15 minute Hp_qosv_15M 2-69
HP-quality of service violation 24 hour Hp_qosv_24H 2-70
HP-far end quality of service violation 15 Hp_ fe_qosv_15M 2-71

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

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

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

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

hour

Clearing alarms 2-5
Low order path alarms with overhead monitoring
LPOM-Excessive Errors (EXC) Lpom_exc 2-114

2
LPOM-Trail Identifier Mismatch (TIM) Lpom_tim 2-116
LPOM-Payload Label Mismatch (PLM) Lpom_plm 2-118
LPOM-Unequipped (UNEQ) Lpom_uneq 2-120
PDH physical interface alarms
PPI-Transmit Fail (TF) Ppi_tf 2-122
PPI-Loss Of Signal (LOS) Ppi_los 2-124
PPI-Alarm Indication Signal (AIS) Ppi_ais 2-126
PPI-Excessive errors (EXC) Ppi_exc 2-127
PPI-Signal Degrade (DEG) Ppi_deg 2-128
PPI-Unexpected Signal Ppi_unexp_signal 2-129
PPI-Loss of Frame (LOF) Ppi_lof 2-130
PPI-Loss of Multiframe (LOM) Ppi_lom 2-131
PPI-Loopback On Ppi_loopback_on 2-132
PPI-Loss of Frame - transmit (T-LOF) Ppi_lof_T 2-133
PPI-code violation-quality of service Ppi_cv_qosv_15M 2-134

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

violation 24 hour

2-6 Clearing alarms
Synchronization alarms
Sync-SETG Fail Sync_setg_fail 2-136
Sync-Unexpected signal Sync_unexp_signal 2-137
Sync-ESO Source Not Primary Sync_eso_src_not_primary 2-138
Sync-SETG Holdover Sync_setg_holdover 2-139
Sync-Source Not Primary Sync_src_not_primary 2-140
Sync-External Sync Loss Of Signal Sync_ext_sync_los 2-141
Sync-Source out of limits Sync_source_out _of_limits 2-143

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

2
Misc INT NE-Spi Comms Fail Int_ne_spi_comms_fail 2-147
Misc EA-Ext inp <1-8> Ea_ext_inp 2-148
Misc EA-Ext out <1-5> Ea_ext_out 2-149
Misc INT NE-Configuration Corrupt Int_ne_config_corrupt 2-150
Misc NE-Lan Alarm Ne_lan_alarm 2-151
Misc NE-Unexpected LAN Ne_unexpected_lan 2-152
Misc INT NE-Config bp mismatch Int_ne_config_bp_mismatch 2-153
Misc Ps-power fail Ps_power_fail 2-154
Misc NE-Date time unknown Ne_date_time_unknown 2-155
Misc Unexpected SW version Unexp_sw_version 2-156
Misc Internal 1 second clock loss of Int_ne_1s_clk_los 2-157

signal
Card alarms
Card NE-Card Out Ne_card_out 2-158
Card NE-Unexpected Card Ne_unexpected_card 2-160
Card INT-NE-HBEAT-Missing INT_Ne_HBEAT_Missing 2-162
Card NE-Card Fault Ne_card_fault 2-163
Card NE-Wrong Card Ne_wrong_card 2-164
Card NE-Invt Write Jumper Fitted Ne_invt_wri_jumper_fitted 2-165
Card NE-Minor card mismatch Ne_minor_card_mismatch 2-166

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

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

Corrupt
Config INT NE-Configuration Available Int_ne_cfg_avail_bank_corrupt 2-169

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

Mismatch
Config INT NE-Configuration Audit Int_ne_cfg_audit_mismatch 2-173

Mismatch
Config INT NE-Configuration Validation Int_ne_cfg_validation_error 2-175

Error
Config INT NE-Standby Configuration Int_ne_stdby_cfg_sw_unstab 2-176

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

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

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

fail

Clearing alarms 2-9
1+1 Card Protection alarms
Equipment fail PROT_Equip_Fail 2-180

2
Equipment Out PROT_Equip_Out 2-181
Unexpected Equipped PROT_Unexpected_Equip 2-182
Cable error PROT_Cable_Error 2-183
Wrong equipment PROT_Wrong_Equip 2-184
Multiplex section protection alarms
Protection scheme mismatch MSP_FOP_PAM 2-185
Channel mismatch MSP_FOP_SCM 2-186
Invalid K bytes (Invalid command) MSP_FOP_INV 2-187
Invalid K bytes (timeout) MSP_FOP_TMOUT 2-189
OPE100 card alarms
Wrong slot, or shelf NE_Config_Bp_Mismatch 2-189
Config.cfg file corrupt NE_Cfg_Corrupt_Bank 2-190
Configuration corrupt NE_Cfg_All_Banks_Corrupt 2-191
Invalid parameters entered NE_Cfg_Validation_Err 2-192
Invalid command entered NE_Cfg_SW_Mismatch 2-193
Excessive differential delay VC-EDD 2-194
HP - sequence identifier mismatch HP-SIM 2-195
Unknown subnet INT-NE-IP_Subnet_Unknown 2-196

2-10 Clearing alarms
Optical amplifier alarms
LED LCD
PSU off off 2-197
PWR red PWR fail 2-197
LOS red LOS ON 2-197
FIB red FIB open 2-197
Tint red Tint FAIL 2-197
Tint yellow Tint FAIL 2-197
Tlas red Tlas FAIL (2-197
Tlas yellow Tlas FAIL 2-197
Idrv yellow ldrv ON 2-197
FPA green OK (2-197
Config yellow - 2-197

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

tributary (STM-1e mode)
Quad-STM-1e 1 to 4, 11 to 14 1 to 4 1 111 to 373
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 - -
STM-1e tributary 1 to 4, 11 to 14 1 - -
OPE100 tributary 1 to 4, 11 to 14 ??? ??? ???
UEOS 15A 1 - -
LEOS (LAN) 15B 1 or 2 - -
LEOS (Synchronization) 15B 1 - -

OS
OS-Optical Power High
Significance
The laser or its related control loop has failed. The optical power output has
exceeded the nominal limit by +4dB or greater (i.e. Optical Power High).
Instance/Unit
This alarm is reported against an optical port instance as
S <slot-no> - <port-no>
For details of valid arguments see Table 2-1 on page 2-11
Impact
Critical alarm
Loss of traffic output. If far end has ALS,received traffic will also be lost.
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
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.
Possible causes
Faulty STM-N optical aggregate or optical 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-1233-547.

OS
OS-Disabled Laser Shutdown
Significance 2
The automatic laser shutdown (ALS) function is disabled on all ports of
indicated PIU.
Instance/Unit
This alarm is reported against an optical port instance as
Impact
This alarm is reported against an optical port; however, the ALS function is
enabled or disabled on a card basis.
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-1233-101 for the position of the links on the cards.

OS
OS-Laser Shutdown
Significance
This alarm is reported when the laser on the specified optical port has been
shutdown by the automatic laser shutdown (ALS) circuit.
Instance/Unit
This alarm is reported against an optical port instance, as
Impact
Critical alarm
Loss of traffic output.

Temporary traffic hit on protected paths.
Consequent Action
None.
Possible causes
Possible causes for the OS-Laser shutdown alarm are:
• RS_LOS alarm.
• Faulty STM-N optical aggregate or optical 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 STM-N optical
aggregate or optical tributary card. Refer to the Maintenance Procedures,
323-1233-547.

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

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.
AIS is injected downstream
Protection switch on protected paths
PM event
Possible causes
Possible causes for the Es_cmi_violation alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty STM-1e 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, STM-1e or Quad-STM-1e tributary
card. Refer to the Equipment Maintenance Procedures, 323-1233-547 for
details.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—

ES
ES-Transmit Fail (TF)
Significance 2
The STM-1e tributary output signal has fallen below a pre-defined threshold.
Instance/Unit

Impact
Critical Alarm
Loss of traffic output
Consequent Action
None.
Possible causes
Possible causes for the ES-TF alarm are:
• Cable fault.
• Faulty STM-1e tributary card.
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, STM-1e or Quad-STM-1e tributary
card. Refer to the Equipment Maintenance Procedures, 323-1233-547 for
replacement procedures.
If the alarm is still present, escalate problem.
—end—

ES
(15 minute)
Significance
The Es_cv_qosv_15M alarm is reported 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:
• Faulty electrical tributary card.
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)
2
Significance
The Es_cv_qosv_24H alarm is reported 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:
• Faulty electrical tributary card.
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
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
not been configured for a connection.
Instance/Unit
Impact
Major alarm.
Consequent Action
None.
Possible causes
Incorrect fibre or cable connection.
Incorrect traffic connection
Faulty 2 Mbit/s, 34/45 M/bits or 140 Mbit/s tributary card.
Corrective actions
Configure the STM-1 port as detailed in Provisioning and Operations

RS
RS-Loss of Signal (LOS)
Significance 2
The indicated card detects the loss of the received signal.
Note: The RS-Loss of Signal (LOS) alarm can be masked using the Port
Alarm Monitoring feature. For details on this feature refer to the
Provisioning & Operations (323-1233-310) handbook.
Instance/Unit
Impact
Critical alarm
Loss of received traffic and AIS injected.

Consequent Action
AIS is injected downstream.
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, cable or connectors.
• Faulty local STM-N optical aggregate, optical tributary or SDH elecrical
tributary.
• Faulty far end STM-N optical aggregate, optical tributary or SDH elecrical
tributary.

Corrective actions
Procedure 2-5
Rs-los alarm clearing
Step Action
1 Perform a ‘Local’ loopback on the indicated port (see Network Surveillance

Procedures, 323-1233-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 3.
2 Replace the local STM-N card. Refer to the Maintenance Procedures,
323-1233-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-1233-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-1233-547.
6 On optical cards, clean the receive optical connections at the local STM-N
optical aggregate or optical tributary, refer to Maintenance Procedures,
323-1233-547. Verify that the received optical power is in the correct range.
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 STM-N
323-1233-547. Verify that the transmit optical power at the far STM-N optical
aggregate or optical tributary is in the correct range.
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 2
The frame alignment algorithm has detected loss of frame alignment.
Instance/Unit
This alarm is reeported against a port instance as
Impact
Critical alarm
Traffic is replaced by AIS.

If entered in the synchronization source hierarchy list, this port will be

marked unavailable for synchronization.
Consequent Action
Synchronisation switch if the port was the current synchronisation source.
Protection switch to protected paths.
PM event.
Possible causes
Possible causes for the Rs_lof alarm are:
• Faulty optical fibre or cable.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end local STM-N optical aggregate, optical tributary or SDH
electrical tributary card.

Corrective actions
Procedure 2-6
Rs_lof alarm clearing
Step Action
1 If the indicated STM-N optical aggregate, optical or SDH electrical tributary

port provides the current synchronization source, ensure the NE has
switched from this port as a source.
2 Perform a loopback on the ‘Local’ card (see Network Surveillance
Procedures, 323-1233-510).
If the alarm is still present, remove the loopback and go to step 3.
If the alarm clears, remove the loopback and go to step 4.
Replace the local card. Refer to the Maintenance Procedures, 323-1233-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-1233-547.
6 On optical cards, clean the receive optical connections at the local STM-N
323-1233-547. Verify that the received optical power is in the correct range.
If the received optical power is not within range, go to step 7.
optical fibre. Use appropriate methods to isolate and repair a fibre fault.
—end—

RS
RS-Trace Identifier Mismatch (TIM)
Significance 2
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 reported
until four successive occurrences of the string mismatch.
Instance/Unit
Impact
Major alarm
If consequent actions are switched on then traffic is replaced by AIS.
Consequent Action
AIS is injected downstream
Possible causes
Possible causes for the Rs-tim alarm are:
• Incorrect fibre or cable connection setup.
• Path trace settings incorrect (i.e. receive string or far end transmit string).
• Cyclic redundancy check (CRC) settings incorrect.
• Faulty STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• If intermittent or transient events, the cause could be errors in signal.
• Faulty single fibre working span.

Corrective actions
Procedure 2-7
Rs-tim alarm clearing
Step Action
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-1233-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-1233-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-1233-547.
—end—

RS
RS-Loopback On
Significance 2
This alarm indicates that an internal local or remote loopback is present at the
indicated port.
Instance/Unit
Impact
Minor alarm.
Possible loss of communication to mux.
Possible TIM.
Possible synchronisation source switch.
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 reported to indicate that an active BBE, ES, SES
or UAS performance monitoring point threshold has been exceeded 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.
• RS_LOS, RS_LOF or ES_CMI alarm.
Corrective actions
Procedure 2-8
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 2
The Rs_qosv_24H alarm is reported to indicate that an active BBE, ES, SES
24 hour monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Rs_qosv_24H alarm are:
• RS_LOS, RS_LOF or ES_CMI alarm.
Corrective actions
alarm.
Procedure 2-9
Rs_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Rs_los or Rs_lof alarm. Identify and remove the
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
indicates a failure at the far multiplexer. The alarm is reported when there are
three successive occurrences of AIS.
Instance/Unit
Impact
Minor alarm.
Traffic is affected on unprotected paths.
Temporary traffic hit on protected paths during switch.
Consequent Action
AIS is inserted downstream.
Resulting alarm
MS-RDI alarm is reported at the remote (source) multiplexer if RDI is “on”
for reporting (default is “off”).
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-10
MS-AIS alarm clearing
Step Action 2
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, a switch occurs
to an alternative source.
3 Set RS-TIM “off” then perform loopback
4 Perform a ‘Local’ loopback on the local card (see Network Surveillance
Procedures, 323-1233-510).
If the alarm is still present, remove the ‘Local’ loopback and go to step 5.
If the alarm clears, remove the ‘Local’ loopback and go to step 6.
5 Replace the local card. Refer to Maintenance Procedures, 323-1233-547.
6 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
—end—

MS
MS-Remote Defect Indicator (RDI)
Significance
An MS Remote Defect Indicator has been detected in the K2 bytes of the MS
overhead. This indicates that the far multiplexer has detected a fault in its
incoming signal. The alarm is reported 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:
• RS-LOS, RS-LOF, RS-TIM or MS-EXC at the far multiplexer resulting in
an MS-AIS.
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.

Corrective actions
Procedure 2-11
MS-RDI alarm clearing
Step Action 2
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)
indicates that the bit errors received at the far end multiplexer exceed the
configured threshold.
Instance/Unit
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the MS-REI alarm are:
• MS-DEG or MS-EXC alarms at the far multiplexer.
tributary card.
tributary card.

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

MS
MS-Excessive errors (EXC)
Significance
An MS Excessive Bit Error alarm is reported when the BER of the BIP-24N
error 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).
RDI sent upstream.
Possible causes
Possible causes for the MS-EXC alarm are:
• Faulty optical fibre, cable or connections.
tributary card.
tributary card.

Corrective actions
Procedure 2-13
MS-EXC alarm clearing
Step Action 2
Procedures, 323-1233-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’
6 On optical cards, clean the receive optical connections at the local aggregate
or optical tributary, refer to Maintenance Procedures, 323-1233-547. Verify
that the received optical power is in the correct range.
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 STM-N optical aggregate or optical tributary.
aggregate oroptical tributary is in the correct range.
optical fibre. Use appropriate methods to isolate and repair fibre fault.
—end—

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

Consequent Action
None.
Resulting alarm
Possible HP-REI or LP-REI alarms reported at an HP source.
Possible causes
Possible causes for the MS-DEG alarm are:
• Faulty optical fibre, cable or connections.
tributary card.
tributary card.

Corrective actions
Procedure 2-14
MS_DEG alarm clearing
Step Action 2
Procedures, 323-1233-510).
alternative source.
4 Set RS-TIM “off” then perform loopback
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’
7 On optical cards, clean the receive optical connections at the local aggregate
or optical tributary, refer to Maintenance Procedures, 323-1233-547. Verify
that the received optical power is in the correct range.
If the received optical power is within range, go to step 8.
If the received optical power is not within range, clean the receive optical
connections at the local STM-N optical aggregate or optical 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 reported to indicate that an active BBE, ES, SES
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Ms_qosv_15M alarm are:
• RS_LOS, RS_LOF, ES_CMI, MS-AIS, MS-EXC or MS-DEG alarm.
Corrective actions
Procedure 2-15
Ms_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ms-ais, Ms-exc, Ms-deg
or Es-cmi. 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 2
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Ms_qosv_24H alarm are:
• RS_LOS, RS_LOF, ES_CMI, MS-AIS, MS-EXC or MS-DEG alarm.
Corrective actions
alarm.
Procedure 2-16
Ms_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ms-ais or Ms-exc,
Ms-deg or Es-cmi. 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—

MS
MS-Far end quality of service violation (15 minute)
Significance
Instance/Unit

Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Ms_fe_qosv_15M alarm are:
• RDI or REI received from the far multiplexer.
tributary card.
tributary card.
Corrective actions
Procedure 2-17
Ms_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Ms_rdi, Ms_rei alarm. Identify and remove the
2 Check for the presence of B2 bit errors at the far mux. Identify and remove the
cause of 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 2
The Ms_fe_qosv_24H alarm is reported to indicate that any BBE, ES, SES,
Instance/Unit

Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Ms_fe_qosv_24H alarm are:
• MS-RDI or MS-REI received from the far multiplexer.
tributary card.
tributary card.
Corrective actions
alarm.
Procedure 2-18
Ms_fe_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Ms_rdi, Ms_rei alarm. Identify and remove the
2 Check for the presence of B2 bit errors at the far mux. Identify and remove the
cause of these errors.
—end—

AU
AU-Alarm Indication Signal (AIS)
Significance
An AIS has been detected in the H1 and H2 bytes indicating a failure in the
upstream path.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Minor alarm.
Traffic is replaced by AIS downstream on protected paths.

Consequent Action
RDI is injected upstream.
A protection switch occurs at PPS protected VC-4 connections.
Possible causes
Possible causes for the AU-AIS alarm are:
• Upstream alarms which inject AIS.
tributary card.
tributary card.

Corrective actions
Procedure 2-19
AU-AIS alarm clearing
Step Action 2
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-1233-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-1233-547.
—end—

AU
AU-Loss of Pointer (LOP)
Significance
The pointer value in the H1 and H2 bytes is invalid for three consecutive
frames.
Instance/Unit
This alarm is reported against a high order path instance, reported as
Impact
Critical alarm.
Traffic downstream is replaced by AIS.

Consequent Action
A protection switch on protected paths.

Resulting alarms
Transmission of HP-RDI in the return path.
Possible causes
Faulty STM-N optical aggregate, optical tributary or SDH electrical tributary
card.
Corrective actions
Procedure 2-20
AU-LOP alarm clearing
Step Action
1 If the indicated card provides the current synchronization source, switch to an

323-1233-547.
—end—

HP
HP-Excessive errors (EXC)
Significance 2
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 reported.
Instance/Unit
Impact
Critical alarm.
Downstream traffic is replaced by AIS.
Temporary traffic hit, but on low order paths.
Consequent Action
Path protection switch.
PM event.
Resulting alarms
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.
tributary card.
tributary card.

Corrective actions
Procedure 2-21
HP-EXC alarm clearing
Step Action

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-1233-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-1233-547.
—end—

HP
HP-Signal Degrade (DEG)
Significance 2
Signal degrade is an intermediate alarm which informs the operator that
signal quality has declined. 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
reported.
If signal quality continues to decline the HP-EXC alarm threshold will be

crossed.
Instance/Unit
This alarm is reported against a high order path instance, reported as
Impact
Major alarm.
Bit errors in traffic.
Consequent Action
None
Possible causes
Possible causes for the HP-DEG alarm are:
tributary card.
tributary card.

Corrective actions
Procedure 2-22
HP-DEG alarm clearing
Step Action

Procedures, 323-1233-510).
323-1233-547.
5 Replace the appropriate card. Refer to Maintenance Procedures,
323-1233-547.
—end—

HP
HP-Trace Identifier Mismatch (TIM)
Significance 2
The VC-4 path trace feature allows the operator to specify a trace identifier at
the start of the SDH path and an expected identifier at the end of the SDH
path. In the event the expected trace identifier not matching the transmitted
identifier, the HP-TIM alarm is reported.
Instance/Unit
Impact
Major alarm.
Consequent Action
PM event.
Possible causes
Possible causes for the HP-TIM alarm are:
• Incorrect connection.
• Path trace settings incorrect (i.e. expected receive string or far end transmit
string).

Corrective actions
Procedure 2-23
HP-TIM alarm clearing
Step Action

2 Check the connections have been provisioned correctly. Refer to Provisioning
and Operations Procedures, 323-1233-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-1233-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 2
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 reported 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, HP_EXC, HP_TIM, HP_PLM or
HP_UNEQ alarm at far multiplexer.
• Faulty far end or near end aggregate, Quad STM-1o, STM-1o, STM-4o
tributary or SDH electrical tributary card.

Corrective actions
Procedure 2-24
HP-RDI alarm clearing
Step Action
1 Check far multiplexer for cause of alarm (AU_AIS,AU_LOP,

HP_LOM,HP_EXC, HP_TIM, HP_PLM or HP_UNEQ 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 2
When the VC-4 contains multiframe TU-12 payloads. The H4 byte indicates
that the frame within the multiframe carried is the current VC-4. Loss of
multiframe alignment is indicated if three consecutive out of sequence H4
bytes are received. Alignment is regained if two consecutive in sequence H4
bytes are received.
Instance/Unit
Impact
Major alarm.

Consequent Action
Possible causes
Possible causes for the HP_LOM alarm are:
tributary card.
tributary card.

Corrective actions
Procedure 2-25
HP-LOM alarm clearing
Step Action

Procedures, 323-1233-510).
‘Local’ loopback. Goto step 2.
loopback. Goto step 3.
—end—

HP
HP-Remote Error Indicator (REI)
Significance 2
The BER derived from 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 bit errors in the VC-4 path.
Instance/Unit
Impact
Major alarm.
Errored traffic is received at NE.
Consequent Action
None.
Possible causes
Possible causes for the HP-REI alarm are:
• Bit errors on transmission path from the NE.
• Faulty remote STM-N optical aggregate, optical tributary or SDH electrical
tributary card.

Corrective actions
Procedure 2-26
HP-REI alarm clearing
Step Action
1 Check remote multiplexer for cause of errors.

If the cause is 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 2
The value of the VC-4 signal label code in the C2 byte does not correspond
with the expected value.
Instance/Unit
Impact
Major alarm.
Consequent Action
PM event.
Possible causes
Possible causes for the HP-PLM alarm are:
• Incorrect connection setup.
• Settings incorrectly set during configuration (i.e. expected receive string or
far end transmit string).
• If intermittent or transient events, errors in the signal.

Corrective actions
Procedure 2-27
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-1233-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 2
The value of the VC-4 path signal label code in the C2 byte indicates
unequipped (when unequipped was not the expected C2 byte. This alarm is
reported when five successive string mismatches occur.
Instance/Unit
Impact
Major alarm.
Traffic is affected if incorrect connection (wrong traffic).
Consequent Action
PM event.
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-28
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 2
The HP Signal Fail alarm is reported if both paths of a VC-4 protected
connection fail.
Instance/Unit
Impact
Critical alarm.
Traffic is affected.
Consequent Action
None.
Possible causes
Possible causes for the HP-SF alarm are:
• Incorrect connections.
• Faulty far end card.
• Any permutation of HPOM-TIM, HPOM-EXC, HPOM-UNEQ,
HPOM-PLM or AU-AIS on both paths.

Corrective actions
Procedure 2-29
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 2
The INT-HP-IP-BUFFER is reported if the input buffer for the high order
(VC-4) PDH mapper overflows.
Instance/Unit
Impact
Major alarm
Traffic is replaced by AIS downstream.
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.
• Synchronization problem in the network (e.g. timing loop).

Corrective actions
Procedure 2-30
INT-HP-IP-BUFFER alarm clearing
Step Action
1 Check for timing loops in the synchronization for the network.

a. Check that synchronization is set up according to the network
synchronization plan.
b. Check if a synchronization source switch has caused a timing loop.
If the alarm is still present go to step 3.
2 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 3.
3 Replace the indicated 140 Mbit/s tributary card. Refer to the Maintenance
Procedures, 323-1233-547, for replacement procedures.
—end—

HP
INT HP-Output Buffer Overflow
Significance 2
The INT-HP-OP-BUFFER is reported if the output buffer for the 140M bit/s
desynchronizer overflows.
Instance/Unit
This alarm is reported against a high order port instance as
S <slot-no> - <port-no> - J<AU-4>.
Impact
Major alarm
Consequent Action
The ongoing payload is filled with ‘all ones’.
Possible causes
Possible causes for the INT-HP-OP-BUFFER alarm are:
• Transient changes in the payload bit rate.

Corrective actions
Procedure 2-31
INT-HP-OP-BUFFER alarm clearing
Step Action

2 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.
3 Replace the indicated 140 Mbit/s tributary card. Refer to Maintenance
—end—

HP
HP-Quality of service violation (15 minute)
Significance
The Hp_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
2
or UAS performanance monitoring threshold has been exceeded within a 15
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Hp_qosv_15M alarm are:
• RS_LOS, RS_LOF, ES_CMI, MS_AIS, MS_EXC, MS_DEG,
INT_AU_AIS, INT_AU_LOP, HP_LOM, HP_TIM, HP_PLM or
HP_EXC alarm.
Corrective actions
Procedure 2-32
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 reported to indicate that any BBE, ES, SES or
UAS performanance monitoring point threshold has been exceeded within a
Instance/Unit
This alarm is reported against a high order path instanced as
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Hp_qosv_24H alarm are:
Corrective actions
alarm.
Procedure 2-33
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 2
The Hp_fe_qosv_15M alarm is reported to indicate that any BBE, ES, SES or
UAS performanance monitoring point threshold has been exceeded within a
Instance/Unit

Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Hp_fe_qosv_15M alarm are:
• HP-RDI or HP-REI alarm from the far multiplexer.
tributary card card.
tributary card.
Corrective actions
Procedure 2-34
Hp_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ms-ais or Ms-exc,
Ms-deg or Es-cmi. Identify and remove the cause of this alarm.
these errors.
—end—

HP
HP-Far end quality of service violation (24 hour)
Significance
The HP_fe_qosv_24H alarm is reported 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 HP_fe_qosv_24H alarm are:
tributary card.
tributary card.
Corrective actions
alarm.
Procedure 2-35
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
the cause of these errors.
3 The Hp_fe_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—

HPOM
(15 minute)
2
Significance
The HPOM_QOSV_15M alarm is reported to indicate that any BBE, ES,
SES, UAS active performance monitoring threshold has been broken within a
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The HPOM_QOSV_15M alarm are:
• Faulty tributary card.
Corrective actions
Procedure 2-36
HPOM_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 HPOM_Violation alarm. Identify and remove
3 The HPOM_QOSV_15M alarm clears after the next 15 minute monitoring
period.
—end—

HPOM
(24 hour)
Significance
The HPOM_QOSV_24H alarm is reported to indicate that any BBE, ES,
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The HPOM_QOSV_24H alarm are:
Corrective actions
Procedure 2-37
HPOM_QOSV_24H alarm clearing
Step Action
of this alarm.
2 Check for the presence of the HPOM_Violation alarm. Identify and remove
3 The HPOM_QOSV_24H alarm clears after the next 24 hour monitoring
period.
—end—

HPOM
HPOM-far end quality of service violation (15 minute)
Significance 2
The HPOM-FE_QOSV_15M alarm is reported to indicate that any BBE, ES,
Instance/Unit

Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the HPOM-FE_QOSV_15M alarm are:
tributary card.
tributary card.
Corrective actions
alarm.
Procedure 2-38
HPOM-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
3 The HPOM-FE_QOSV_15M alarm clears after the current 15 minute
monitoring period.
—end—

HPOM
HPOM-far end quality of service violation
(24 hour)
Significance
The HPOM_FE_QOSV_24H alarm is reported to indicate that any BBE, ES,
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The HPOM_FE_QOSV_24H alarm are:
Corrective actions
Procedure 2-39
HPOM_FE_QOSV_24H alarm clearing
Step Action
of this alarm.
2 Check for the presence of the HPOM_FE_Violation alarm. Identify and
remove the cause of this alarm.
3 The HPOM_FE_QOSV_24H alarm clears after the next 24 hour monitoring
period.
—end—

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

alarm is non-intrusively monitored at all intermediate NEs whereas the
HP-EXC is monitored from a terminated connection.
Instance/Unit
Impact
Critical alarm.
Tempoary traffic hit on protected paths.
Bit errors on unprotected paths.
Consequent Action
Possible causes
Possible causes for the HPOM-EXC alarm are:
tributary card.
tributary card.

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

Procedures, 323-1233-510).
323-1233-547.
—end—

HPOM
HPOM-Trace Identifier Mismatch (TIM)
Significance 2
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 the expected trace identifier not matching the
transmitted identifier, the HP-TIM alarm is reported.
The HPOM-TIM alarm is similar to the HP-TIM alarm. The HPOM-TIM

HP-TIM is monitored from a terminated connection.
Instance/Unit
Impact
Major alarm.
Risk of receivng wrong traffic for unprotected connections
Tempoary traffic hit on protected connections.
Consequent Action
Possible causes
Possible causes for the HPOM-TIM alarm are:
• Path trace settings incorrect (i.e. receive string or far end transmit string).

Corrective actions
Procedure 2-41
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 2
The value of the VC-4 signal label code in the C2 byte does not correspond
with the expected value.
The HPOM-PLM alarm is similar to the HP-PLM alarm. The HPOM-PLM

HP-PLM is monitored from a terminated connection.
Instance/Unit
Impact
Major alarm.
Bit errors on unprotected paths
Consequent Action
Protection switch, if configured “on”.
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-42
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-1233-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 2
The value of the VC-4 path signal label code in the C2 byte indicates
unequipped (when unequipped was not the expected C2 byte. This alarm is
reported 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 at all intermediate NEs
whereas the HP-UNEQ is monitored from a terminated connection.
Instance/Unit
Impact
Major alarm.
Traffic is affected if incorrect connection (wrong traffic).
Consequent Action
Protection switch, if configured “on”.
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-43
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)

2
Significance
An AIS has been detected in the TU pointer bytes.
Instance/Unit
This alarm is reported against a low order path instance as
S <slot-no> - <port-no> - J<AU-4> - K<klm>
Impact
Minor alarm
Traffic is replaced by AIS downstream on protected paths.
Consequent Action
A protection switch occurs at PPS protected VC-4 connections.
Possible causes
AIS being generated by another multiplexer on the network.
Corrective actions
Procedure 2-44
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 has been invalid for three consecutive frames.
Instance/Unit
S <slot-no> - <port-no> - J<VC-4> - K<klm>
Impact
Critical alarm
Consequent Action
A protection switch occurs on protected paths.
Possible causes
Faulty aggregate or tributary card.
Corrective actions
Procedure 2-45
TU-LOP alarm clearing
Step Action
1 Check that the correct network settings have been made. Refer to
Provisioning and Operations Procedures, 323-1233-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 2
INT-TU-AIS is reported where the AIS has been detected in the pointer bytes
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 reported against a PDH port instance 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-46
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-1233-547.
—end—

TU
INT-TU-Loss of Pointer (LOP)
Significance
INT-TU-LOP is reported 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 reported 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-47
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-1233-547.
—end—

LP
LP-Excessive errors (EXC)
Significance 2
The BER of the VC-12 path status byte (V5) has exceeded the configured
threshold. This alarm is observed at the termination of the Low order
container.
Instance/Unit
This alarm is reported against a port instance, reported as
Impact
Critical alarm
Traffic is affected on the outgoing signal.
Consequent Action
AIS is injected.
RDI is injected in the return path.
Possible causes
Possible causes for the LP-EXC alarm are:
• Line errors.
• Faulty 2 Mbit/s tributary or 34/45 M/bit/s tributary.
tributary card.

Corrective actions
Procedure 2-48
LP-EXC alarm clearing
Step Action
1 Check upstream for Lpom alarms (it may be necessary to set reporting to
“monitor”. 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 Maintenance Procedures,
323-1233-547.
4 Restore to the old configuration.
—end—

LP
LP-Signal Degrade (DEG)
Significance 2
The LP-DEG alarm is reported 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
Impact
Major alarm.
Bit errors on downstream traffic.
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-49
LP-DEG alarm clearing
Step Action
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-1233-547.
3 Restore to the old configuration.
4 Replace upstream traffic cards.
—end—

LP
LP-Payload Label Mismatch (PLM)
Significance 2
The value of the VC-3/VC-12 signal label does not correspond with the
expected value. This alarm is reported at a path termination point, subsequent
to a protection switch.
Instance/Unit
Impact
Major alarm
Traffic downstream is replaced by AIS
Consequent Action
If configured on:
• AIS is injected downstream.
• RDI is injected upstream.
• PM event.
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-50
LP-PLM alarm clearing
Step Action
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’.
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
Maintenance Procedures, 323-1233-547, for replacement procedures.
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-1233-547 for replacement procedures.
—end—

LP
LP-Remote Defect Indicator (RDI)
Significance 2
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:
• If alarm reported 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 reported for one tributary only, TU-AIS, TU-LOP, INT-TU-AIS,
INT-TU-LOP, LP-PLM, LP-EXC, LP-UNEQ or LP-TIM alarm present at
far path termination.

Corrective actions
Procedure 2-51
LP-RDI alarm clearing
Step Action
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 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 2
The REI bit (bit 3 in the V5 byte) is set. This indicates that the far end
multiplexer has detected bit errors in the VC-12. The BER calculated from an
accumulation of the values in REI is above the configured threshold
indicating that the far end has had bit errors in its received signal.
Instance/Unit

Impact
Major alarm.
Errors in the received traffic.
Consequent Action
None.
Possible causes
Bit errors observed at path far end.
Corrective actions
Procedure 2-52
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.
2 Replace the local tributary card. Refer to the Equipment Maintenance
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 reported if the input buffer for the low order
(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.

Corrective actions
Procedure 2-53
INT-LP-IP-BUFFER alarm clearing
Step Action 2
2 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 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 3.
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 4
3 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 reported if the output buffer for the low order
(VC-12, VC-3) desynchronizer overflows.
Instance/Unit
Impact
Major alarm
Downstream traffic is replaced by AIS on unprotected paths.
Consequent Action
AIS injected downstream.
Possible causes
Possible causes for the INT-LP-OP-BUFF alarm are:
• Transient changes in the received payload bit rate.

Corrective actions
Procedure 2-54
INT-LP-OP-BUFFER alarm clearing
Step Action
2
2 Check if the INT-LP-OP_BUFFER alarm is present on more than one of the 2
Mbit/s tributary ports.
If the INT-LP-OP_BUFFER alarm is only present on one tributary port, go to
step 3.
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 4
If the INT-LP-OP_BUFFER alarm is present on all the tributary ports on more
than one 2Mbit/s cards, go to step 3.
3 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 reported if both paths in a protected VC-12 or
VC-3 connection fail.
Instance/Unit
This alarm is reported against a port instanced as
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Upstream fault in both traffic paths.
Corrective actions
Procedure 2-55
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
2
The VC-12 and VC-3 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
reported. This alarm is detected at a path termination.
Instance/Unit
Impact
Major alarm
Consequent Action
PM event.
Possible causes
Possible causes for the LP-TIM alarm are:
• Incorrect configuration of far end or near end path string.

Corrective actions
Procedure 2-56
LP-TIM alarm clearing
Step Action
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.
3 Replace the local tributary card. Refer to the Maintenance Procedures,
323-1233-547, for replacement procedures.
—end—

LP
LP-Label Unequipped
Significance
2
The LP-UNEQ value of the VC-12 or VC-3 payload signal label indicates
unequipped (no traffic in payload) when unequipped is not the expected
payload label.
Instance/Unit
This alarm is reported against a port instanceas
Impact
Major alarm
Consequent Action
If configured on:
• AIS is injected downstream.
• RDI is injected upstream.
• PM event.
AIS injected downstream.
RDI is injected upstream
PM event.
Possible causes
Possible causes for the LP-UNEQ alarm are:

Corrective actions
Procedure 2-57
LP-UNEQ alarm clearing
Step Action
value of ‘0’.
go to step 3.
3 Replace the local tributary card. Refer to the Maintenance Procedures,
323-1233-547 for replacement procedures.
—end—

LP
LP-Quality of service violation (15 minute)
Significance
The Lp_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
2
or UAS performanance monitoring point threshold has been exceeded within
a 15 minute monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Lp_qosv_15M alarm are:
• RS_LOS, RS_LOF, ES_CMI, TU_AIS, TU-LOP, LP_TIM, LP_EXC,
LP_UNEQ, LP_DEG or INT_LO_BUFFER_OVERFLOW alarms.
Corrective actions
Procedure 2-58
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, LP-UNEQ, LP-DEG,
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 reported to indicate that an active BBE, ES, SES
or UAS performanance point monitoring threshold has been exceeded 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:
• Errored input signal.
Corrective actions
Procedure 2-59
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, LP-UNEQ, LP-DEG,
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 2
The Lp_fe_qosv_15M alarm is reported to indicate that an active BBE, ES,
SES or UAS performance monitoring point threshold has been exceeded at
the far end within a 15 minute monitoring period.
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Lp_fe_qosv_15M alarm are:
• RDI or REI received from the far multiplexer.
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary, or SDH
electrical tributary card.

Corrective actions
Procedure 2-60
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 B3 bit errors (for VC-3) or V5 bit errors (for VC-12).
Identify and remove the cause of these errors.
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 2
The LP_fe_qosv_24H alarm is reported to indicate that an active BBE, ES,
SES or UAS performanance monitoring point threshold has been exceeded at
the far end within a 24 hour monitoring period.
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
Procedure 2-61
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
(15 minute)
Significance
The LPOM_QOSV_15M alarm is reported to indicate that any BBE, ES,
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The LPOM_QOSV_15M alarm are:
Corrective actions
Procedure 2-62
LPOM_QOSV_15M alarm clearing
Step Action
of this alarm.
2 Check for the presence of the LPOM_Violation alarm. Identify and remove the
3 The LPOM_QOSV_15M alarm clears after the next 15 minute monitoring
period.
—end—

LPOM
(24 hour)
2
Significance
The LPOM_QOSV_24H alarm is reported to indicate that any BBE, ES, SES,
Instance/Unit
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The LPOM_QOSV_24H alarm are:
Corrective actions
Procedure 2-63
LPOM_QOSV_24H alarm clearing
Step Action
of this alarm.
2 Check for the presence of the LPOM_Violation alarm. Identify and remove the
3 The LPOM_QOSV_24H alarm clears after the next 24 hour monitoring
period.
—end—

LPOM
LPOM-Excessive Errors (EXC)
Significance
The LPOM-EXC is reported when the BER of the VC-12 path status byte
(V5) or VC-3 (B3) 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 detected at a terminated connection at the
termination point.
Instance/Unit
Impact
Critical alarm
Bit errors on protected paths.
Consequent Action
A traffic protection switch occurs.
Possible causes
Possible causes for the LPOM-EXC alarm are:
• Errors on network.
• Faulty STM-N optical aggregate, optical tributary or SDH electrical
tributary card.

Corrective actions
Procedure 2-64
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-1233-547. Restore to the old configuration.
—end—

LPOM
LPOM-Trail Identifier Mismatch (TIM)
Significance
The VC-12 or VC-3 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
reported.
The LPOM-TIM alarm is similar to the LP-TIM alarm. The LPOM-TIM

LP-TIM is monitored from a terminated connection.
Instance/Unit
Impact
Major alarm
Risk of receiving wrong traffic on unprotected paths.
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.
• Faulty 34/45 Mbit/s tributary.

Corrective actions
Procedure 2-65
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.
3 Replace the local 2 Mbit/s (or 34/45 Mbit/s) tributary card. Refer to the
Maintenance Procedures, 323-1233-547, for replacement procedures.
4 Replace the far 2 Mbit/s (or 34/45 Mbit/s) card. Refer to the Maintenance
—end—

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

LPOM-UNEQ, LPOM-EXC, LPOM-PLM alarm is non-intrusively
monitored at all intermediate NEs whereas the LP-PLM is detected at a
terminated connection.
Note: The reporting of this alarm can be enabled/disabled.

Instance/Unit
Impact
Major alarm
Bit errors on traffic on unprotected paths.
Temporary traffic hit on unprotected paths.
Consequent Action
Protection switch.
Possible causes
Possible causes for the LPOM-PLM alarm are:

Corrective actions
Procedure 2-66
LPOM-PLM alarm clearing
Step Action 2
value of ‘0’.
procedure to view and change connections.
go to step 3.
3 Replace the local 2 Mbit/s tributary card. Refer to the Maintenance
4 Replace the far 2 Mbit/s card. Refer to the Maintenance Procedures,
—end—

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

LPOM-UNEQ, LPOM-TIM, LPOM-EXC, LPOM-PLM alarm is
non-intrusively monitored whereas the LP-UNEQ is monitored from a
terminated connection.
Instance/Unit
Impact
Major alarm
Consequent Action
Possible causes
Possible causes for the LPOM-UNEQ alarm are:
• Faulty 34/45 Mbit/s tributary.

Corrective actions
Procedure 2-67
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.
3 Replace the local 2 Mbit/s tributary card. Refer to the Maintenance
4 Replace the far 2 Mbit/s card. Refer to the Maintenance 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-68
PPI-TF alarm clearing
Step Action 2
1 Ensure that the 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
2 Check the far end equipment for a short circuit.
If the alarm clears, the alarm clearing procedure is complete. If the alarm is
3 Replace the indicated tributary card. Refer to the Maintenance Procedures,
—end—

PPI
PPI-Loss Of Signal (LOS)
Significance
The PPI-LOS is reported where the loss of a PDH input signal is detected.
Instance/Unit
Impact
Critical alarm.
Loss of receive traffic.
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-69
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 reported 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 Maintenance Procedures,
—end—

PPI
PPI-Alarm Indication Signal (AIS)
Significance
The PPI-AIS alarm is reported 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 2
The PPI-EXC alarm is reported when HDB3 or B3ZS code violations exceed
the threshold in a PDH signal.
Instance/Unit
Impact
Critical alarm.
Consequent Action
AIS is injected downtream.
Possible causes
Possible causes for the PPI-EXC alarm are:
Corrective actions
Procedure 2-70
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 reported when HDB3 or B3ZS 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.
Traffic is affected.
Consequent Action
None.
Possible causes
Possible causes for the PPI-DEG alarm are:
• Errored input signals.
Corrective actions
Procedure 2-71
PPI-DEG alarm clearing
Step Action
1 Investigate preceding equipment and cables for cause of errors.

—end—

PPI
PPI-Unexpected Signal
Significance 2
The PPI-UNEXP_SIGNAL alarm is reported where a signal is connected to a
2 Mbit/s, 34/45 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 traffic connection configuration.
• Faulty 2 Mbit/s, 34/45 Mbit/s or 140 Mbit/s tributary card.
Corrective actions
Procedure 2-72
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 or fibre connections to ensure that the cables are connected to
the correct input terminations.
If the cable connections are incorrect, re-connect 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 reported when a PDH port indicates that signal
framing information cannot be recovered in the receive path. This alarm will
ony be reported if the input port is configured to framed or multi-framed.
Instance/Unit
Impact
Major alarm.
Loss of traffic.
Consequent Action
None.
Possible causes
Possible causes for the PPI-LOF alarm are:
Corrective actions
Procedure 2-73
PPI-LOF alarm clearing
Step Action
1 Investigate preceding equipment and cables for cause of errors.

2 Carry out a local loopback to prove the Rx port is functioning.
—end—

PPI
PPI-Loss of Multiframe (LOM)
Significance 2
The PPI-LOM alarm is reported where a 2 Mbit/s PDH port reports that
signal 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-74
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
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

PPI
PPI- Transmit-Loss of Frame (T-LOF)
Significance 2
The PPI-LOF-T alarm is reported where a 140 Mbit/s PDH port reports that
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-LOF-T alarm are:
• Output cable fault.
Corrective actions
Procedure 2-75
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 reported to indicate that any BBE, ES, SES,
Instance/Unit
This alarm is reported as

Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the PPI_CV_qosv_15M alarm are:
Corrective actions
Procedure 2-76
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 reported to indicate that any BBE, ES, SES,
UAS active performanance monitoring threshold has been broken within a 24
Instance/Unit
This alarm is reported against a port instance, as
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the PPI_CV_qosv_24H alarm are:
Corrective actions
Procedure 2-77
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 reported against an aggregate card instance 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-78
SYNC-SETG_Fail alarm clearing
Step Action
1 Replace the indicated aggregate card. Refer to Maintenance Procedures,

323-1233-547.
2 If the alarm is still present, escalate problem.
—end—

SYNC
Sync-Unexpected signal
Significance 2
The external synchronization input (ESI) port is receiving a synchronization
signal but the port is not in the hierarchy list.
Instance/Unit
This alarm is reported against an external synchronization port instance as
S <slot-no>
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 or remove external synchronisation
signal.

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.
• If synchronization source messaging (SSM) is active this alarm is not
reported.
• Selecting a synchronization source using a Forced or Manual 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-SETG Holdover
Significance 2
This alarm is reported when the NE is operating in holdover mode. This mode
is 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 reported 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 reported against the NE.
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Possible causes for the SYNC_SETG_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 or manual overide 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.
• If synchronization source messaging (SSM) is active this alarm will not be
reported.
• If the current synchronization source was selected by a Forced or Manual
override, this alarm is not reported.
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 2
The signal from the external synchronization input (ESI) on an End of Shelf
(EOS) card has failed.
Note: The external source must be in the synchronization hierarchy (or

forced on or manual override) for the alarm to be reported.
Instance/Unit
This alarm is reported against an external synchronization port instance,
reported as
S <slot-no>
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-79
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-1233-547.
—end—

SYNC
Sync-Source out of limits
Significance 2
A port which can be used as a frequency source has a gross frequency offset.
Instance/Unit
This alarm is reported 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
Faulty synchronization source or SETS in the aggregate card.
Corrective actions
Note: Allow 5 minutes to elapse before attempting to clear the alarm.
Procedure 2-80
SYNC-SOURCE-OUT-OF-LIMITS alarm clearing
Step Action
1 Identify and remove the cause of the frequency errors.
—end—

Misc
Qecc Comms Fail
Significance
The NE cannot communicate over any specific link 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.
tributary card.
tributary card.
When optical tributary cards in a 1+1 MSP association are connected to a

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

Corrective actions
Procedure 2-81
Qecc_Comms_Fail alarm clearing
Step Action 2
1 Check if a loopback is present. Refer to Network Surveillance Procedures,
323-1233-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-1233-310.
5 Switch to Rs mode. Refer to Provisioning and Operations Procedures,
323-1233-310.
6 Perform a status_view command to determine whether Rs or Ms has failed.
Refer to Provisioning and Operations Procedures, 323-1233-310.
Go to step 7
—continued—

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

—end—

Misc
INT NE-Spi Comms Fail
Significance 2
A fault has been detected on the internal SPI communications function.
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:
tributary card.
tributary card.
Corrective actions
Procedure 2-82
Spi-Comms_Fail alarm clearing
Step Action

323-1233-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 reported 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
EA-Ext out <1-5>
Significance 2
An alarm has been received on one of the external alarm outputs.
Note: More than one alarm type can map to activate an external alarm
signal; however a single alarm type cannot.
Instance/Unit
This alarm is reported against an external alarm output instance.
Impact
Depends on the alarm type and mapping.
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
enters detached mode.
This alarm is reported only when one of the following configuration alarms is
reported:
• 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 2
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 reported 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
(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-1233-310).
If a LAN is not expected, remove the LAN connection.

Misc
INT NE-Config bp mismatch
Significance 2
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
Loss of tributary traffic output
Critical alarm.
Consequent Action
If alarm is raised against the Master SEMF the Network Element enters
detached mode.
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-1233-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.
Instance/Unit
This alarm is reported against an EOS card instance 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-1233-547.

Misc
NE-Date time unknown
Significance 2
This alarm is reported 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-1233-302.

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

Misc
Internal 1 second clock loss of signal
Significance 2
A card with a missing 1-second input clock will raise this alarm.
Instance/Unit
This alarm is reported against a card instance 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-1233-310).

Card
NE-Card Out
Significance
Indicates that the indicated card has been removed from the shelf without
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 reported against an NE card instance 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-83
NE-Card_Out alarm clearing
Step Action 2
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 NE. If the alarm still present, go to step 3.
2 Configure the equipment to unequip the indicated slot, see Provisioning and
3 Peform a warm restart on the master aggregate card, see System and Data
Administration Procedures, 323-1233-302.
4 Peform a manual SEMF protection switch on the master aggregate card, see
If the alarm has cleared, go to step 5
If the alarm is still present escalate the problem.
5 Replace the aggregate card. Refer to Maintenance Procedures,
323-1233-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’.
This alarm is reported 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.
• Faulty aggregate card.

Corrective actions
Procedure 2-84
NE-Unexpected_Card alarm clearing
Step Action 2
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-1233-310).
If the alarm still present, go to step 3.
3 Peform a warm restart on the master aggregate card, see System and Data
4 Peform a manual SEMF protection switch on the master aggregate card, see
If the alarm has cleared, go to step 5
If the alarm is still present escalate the problem.
5 Replace the aggregate card. Refer to Maintenance Procedures,
323-1233-547.
If the alarm is still present, replace original aggregate card and escalate
problem.
—end—

Card
INT-NE-HBEAT_Missing
Significance
The aggregate card detects a fault on the indicated card or fails to
communicate with the indicated card.
Instance/Unit
S <slot-no>
Impact
Critical alarm.
May be traffic affecting.
Consequent Action
None.
Possible causes
Possible cause for the INT-NE-HBEAT_Missing alarm is a faulty indicated
card.
Corrective actions
Procedure 2-85
INT-NE-HBEAT_Missing 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-1233-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.
—end—

Card
NE-Card Fault
Significance 2
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-1233-547.

Card
NE-Wrong Card
Significance
A card has been inserted into a slot designated for another type of card (slot
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-86
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, use inventory to determine what card
is inserted. 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-1233-310). Go
to step 2.
2 Check if alarm is still present.
—end—

Card
NE-Invt Write Jumper Fitted
Significance 2
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
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-1233-310).

Config
INT NE-Configuration Corrupt Bank
Significance 2
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-87
INT-NE_Config_Corrupt_Bank
Step Action
1 Carry out a restore of the configuration bank as detailed in System and Data
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
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-88
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 2
This alarm is reported 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 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-89
INT NE-Config_Avail_Bank_Corrupt
Step Action
1 Display the configuration table status. Access the ‘Admin/cnfg_tbl’ submenu

by entering
Admin ↵ a↵
Cnfg_tbl ↵ c↵
Display the configuration table status by entering
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 entering
Switch_to_original ↵ so ↵
A confirmation is required.
4 Execute the backout command by entering
Backout ↵ b↵
5 Restart the software upgrade or configuration restore. Refer to System and

Data Administration Procedures, 323-1233-302.
—end—

Config
INT NE-Configuration Software Mismatch
Significance 2
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-90
INT NE-Cfg_sw_mismatch
Step Action
1 Display the software and configuration table status. Access the ‘Admin/
cnfg_tbl’ submenu by entering
Admin ↵ a↵
Cnfg_tbl ↵ c↵
Display the status by entering

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-90
INT NE-Cfg_sw_mismatch (continued)
Step Action
3 Consolidate the configuration table. Access the ‘Admin/cnfg_tbl’ submenu by

entering
Admin ↵ a↵
Cnfg_tbl ↵ c↵
Consolidate the configuration table status by entering
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-1233-302.
—end—

Config
INT NE-Configuration Audit Mismatch
Significance 2
A configuration audit indicates that the configuration data in the RAM is
different to the configuration settings on the traffic cards.
Note: The audit mismatch alarm is reported if an audit of the Config on

the standby returns with a difference between the Config stores on the
aggregates. An audit may not be carried out for up to 45 minutes after the
card has restarted. As a consequence, the alarm may not be reported
immediately the card is installed in the multiplexer.
Instance/Unit
Impact
Major alarm.
Consequent Action
Possible causes
Audit mismatch.

Corrective actions
Procedure 2-91
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
entering
Admin ↵ a↵
Cnfg_tbl ↵ c↵
Execute the impose command by entering
Impose_config ↵ ic ↵
A confirmation is required.
—end—

Config
INT NE-Configuration Validation Error
Significance 2
During a restart, a value read from the configuration store is invalid.
Instance/Unit
Impact
Major alarm.
Consequent Action
If alarm is raised against the Master SEMF the Network Element enters
detached mode.
Traffic card provisioning is not allowed until the alarm is cleared.
Possible causes
Incorrect software or configuration version.
Corrective actions
Procedure 2-92
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-1233-302.

Config
INT NE-Standby Configuration Flash Corrupt
Significance 2
This alarm indicates a problem with the standby flash memory.
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 standby aggregate active non-volatile
configuration bank is corrupt (it does not match the configuration data held in
the master aggregate active non-volatile configuration bank).
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 2
The configuration bank on the stand-by aggregate has failed.
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
Reported when a 1+1 protection I/O card fails.
Instance/Unit
This alarm is reported 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-1233-547.

Prot
Equip_Out
Significance 2
Reported when both the 1+1 working and protection tributary cards detect no
connection to the 1+1 protection I/O card.
Instance/Unit
This alarm is reported 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
Reported 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 reported against a card in a working slot.
Instance/Unit
This alarm is reported 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 2
Reported to indicate that a cable fault exists between a tributary slot and a 1+1
protection I/O card.
Instance/Unit
This alarm is reported 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
Reported to indicate a mismatch between a tributary card and a 1+1
protection
I/O card.
Instance/Unit
This alarm is reported 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 2
The Failure Of Protocol-Protection Architecture Mismatch alarm raises when
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 reported 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 reported 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 2
The Failure Of Protocol-Invalid alarm is reported to indicate that the received
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.
tributary card.
tributary card.
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

OPE100 Card
NE_Config_Bp_Mismatch
Significance 2
Existing SDH connections have been affected by the card being inserted into
either the wrong slot, or wrong shelf.
Instance/Unit
S <slot-no>
For details of valid arguments see Table 2-1.
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Config_Bp_Mismatch alarm are:
• The MAC address of the shelf recorded in the last successful boot does
not match the current shelf MAC address.
• The slot number of the last successful boot does not match the current slot
number.
Corrective actions
To correct the MAC address/slot number mismatch alarm, you must either:
• put the card in to the last booted shelf, or
• login within reduced mode and type the "proceed" command.
Refer to the OPTera Packet Edge 100 DCLI Command Specification
document for details on how to perform the "proceed" command..
Access is limited to rwa users as they have the greatest access rights to
diagnose card faults.

OPE100 Card
NE_Cfg_Corrupt_Bank
Significance
Configuration of card could not be obtained during start-up.
Instance/Unit
S <slot-no>
Impact
Major, deferred alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_Corrupt_Bank alarm are:
• The config.cfg file is corrupt.
• The config.cfg file is absent, and the $temp$.cfg file is corrupt.
Corrective actions
As access is denied, use the reduced mode password to access the system and
repair the config.cfg file.

OPE100 Card
NE_Cfg_All_Banks_Corrupt
Significance 2
During boot-up of card, configuration could not be read.
Instance/Unit
S <slot-no>
Impact
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_All_Banks_Corrupt alarm are:
• The config.cfg file is corrupt or absent.
• The $temp$.cfg file is corrupt or absent.
Corrective actions

OPE100 Card
NE_Cfg_Validation_Err
Significance
An invalid parameter exists on the config.cfg or $temp$.cfg file.
Instance/Unit
S <slot-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_Validation_Err alarm are:
• The config.cfg file contains invalid parameters.
• The $temp$.cfg file contains invalid parameters.
Corrective actions

OPE100 Card
NE_Cfg_SW_Mismatch
Significance 2
An invalid command exists on the config.cfg or $temp$.cfg file.
Instance/Unit
S <slot-no>
Impact
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_SW_Mismatch alarm are:
• The config.cfg file contains invalid commands, or is absent.
• The $temp$.cfg file contains invalid commands, or is absent.
Corrective actions

OPE100 Card
VC-EDD
Significance
An occurence of this alarm will mean that all traffic has stopped.
Instance/Unit
S <slot-no> - <port-no> - J<AU-4> - k<VC-3>
k<VC-12>

Impact
Minor alarm
Consequent Action
None.
Possible causes
Possible cause for the VC-EDD (Excessive Differential Delay) alarm is a very
long delay in one of the containers arriving.
If there are only 2 VCs concatenated then all traffic will be lost. However, if
there are more than 2 VCs concatenated then the card will grey-out the
delayed VC. This results in traffic flowing with lower bandwidth.
Corrective actions
Investigate cause of delay.

OPE100 Card
HP-SIM
Significance 2
An occurence of this alarm will mean that all traffic has stopped. It cannot be
protected against by protection switching or grey-out and is therefore
extremely serious.
Instance/Unit

Impact
Minor alarm
Consequent Action
None
Possible causes
Possible causes for the HP-SIM (Sequence Identifier Mismatch) alarm are:
• One of the VCs could contain incorrect information, therefore all other
VCs are invalid.
• The bit sequence may have been altered by 3rd party vendor
• If there are more than 2 VCs concatenated, then the alarm will be raised
against the High Order Path Instance (J#). The card will grey-out the VC
that is out of sequence and traffic will flow, with lower bandwidth.
Corrective actions
This transient alarm should be corrected after the protection mechanism,
possibly from another alarm, is initiated.

OPE100 Card
INT-NE-IP_Subnet_Unknown
Significance
This alarm is only relevant when there are OPE100 cards present. This alarm
will not stop IP traffic on the OPE100 card, or SDH traffic.
Instance/Unit
This alarm is NE wide and so it does not relate to a given port. It is only raised
if there is an OPE100 card in the shelf.
Impact
Minor alarm
Consequent Action
None.
Possible causes
The OPE100 card’s IP subnet information has not been provisioned. The IP
subnet address, configured via the ~c o ip s command, must be forwarded to
all OPE100 cards in the shelf.
If a new shelf is configured without an IP subnet address, then this alarm is

raised to indicate that the OPE100 cards are present in the shelf without that
address.
Corrective actions
This alarm is cleared when a valid subnet and mask for the shelf has been
configured. The occurrence of this alarm means that the OPE100 cards can
not be managed over the OSI network, but can still be managed over any
existing TCP/IP network.

Optical amplifier alarms
Amplifier alarm conditions 2

Table 2-2 details the alarms of the optical amplifier.
Table 2-2 Optical amplifier alarms
Alarm LED TIA/EIA 232 Relay Cause

RS485
PSU off - Major & Supply failure

Minor
PWR red (AS) PWR Major Optical output out of limits

(LS[1,2]) PWR
LOS red (AS) LOS Major Optical input too low
FIB red (AS) FIB Major Fiber interlock open
Tint red (AS) TINT Major Internal temperature exceeded

absolute limits
Tint yellow (AS) TINT Minor Internal temperature outside

preset limits
Tlas red (LS[1,2]) TLAS Major Laser temperature exceeded

absolute limits
Tlas yellow (LS[1,2]) TINT Minor Lasertemperature outside preset

limits
Idrv yellow (LS[1,2]) IDRV Minor Laser drive current outside

preset limts
FPA green (AS) FPA - Front Panel Access permitted
Config yellow - - Configuration menu on LCD

entered
Corrective action
Technical assistance must be obtained from Nortel Networks for any optical
amplifier alarm.

3-1
Index 3- 3
A action log 1-2
action
log H
fault clearing 1-2 HP-Excessive errors (EXC) alarm 2-47
alarm HP-Loss_of_Multiframe (LOM) alarm 2-55
clearing 1-1 HPOM_FE_QOSV_15M 2-76
consequent action 1-8 HPOM_QOSV_15M 2-73, 2-74
correlation 1-4 HPOM-Excessive errors (EXC) alarm 2-77
indications 1-3 HPOM-FE_QOSV_24H alarm 2-75
RAU category 1-5 HP-Path_Label_Mismatch (PLM)
severity 1-5 alarm 2-59, 2-81
alarms HP-Remote_Defect_Indicator (RDI)
port alarm monitoring 1-8, 2-2, 2-21 alarm 2-53
AU-Alarm_Indication_Signal (AIS) HP-Remote_Error_Indicator (REI)
alarm 2-44 alarm 2-57
AU-Loss_of_Pointer (LOP) alarm 2-46 HP-Signal Degrade (DEG) alarm 2-49
HP-Signal_Fail (SF) alarm 2-63
C HP-SIM
OPE100 card 2-195
Cable_Error alarm 2-183
clearing HP-Trace Identifier Mismatch (TIM) 2-51,
faultst 2-79
action log 1-2 HP-Unequipped alarm 2-61, 2-83
consequent action
alarm 1-8 I
Critical (alarm severity) 1-7 In station (RAU category) 1-7
INT LP-Input Buffer Overflow alarm 2-65,
D 2-98
INT LP-Output Buffer Overflow alarm 2-67,
Deferred (RAU category) 1-7
2-100
INT NE-Config_All_Banks_Corrupt
E alarm 2-168
EA-Ext_inp alarm 2-148 INT NE-Config_Audit_Mismatch
EA-Ext_out alarm 2-149 alarm 2-173
Equip_Fail alarm 2-180 INT NE-Config_Available_Bank_Corrupt
Equip_Out alarm 2-181 alarm 2-169
INT NE-Config_Bp_Mismatch alarm 2-153
F INT NE-Config_Corrup_Bank alarm 2-167
faults INT NE-Config_Corrupt alarm 2-150
clearing faults

3-2 Index
INT NE-Config_Software_Mismatch MSP FOP_PAM alarm 2-185

alarm 2-171 MSP FOP_SCM alarm 2-186
INT NE-Config_Validation_Error MSP FOP_TMOUT alarm 2-188
alarm 2-175 MS-Remote_Defect_Indicator (RDI)
INT NE-Spi_Comms_Fail alarm 2-147 alarm 2-32
INT NE-Standby_Config_Audit_Mismatch MS-Remote_Error_Indicator (REI)
alarm 2-178 alarm 2-34
INT NE-Standby_Config_Fail alarm 2-179 MS-Signal_Degrade (DEG) alarm 2-38
INT NE-Standby_Config_Flash_Corrupt
alarm 2-177 N
INT NE-Standby_Config_Sw_Unstable NE_Cfg_All_Banks_Corrupt
alarm 2-176 OPE100 card 2-191
INT TU-Alarm Indication Signal (AIS) NE_Cfg_Corrupt_Bank
alarm 2-87 OPE100 card 2-190
INT TU-Loss of Pointer (LOP) alarm 2-88 NE_Cfg_SW_Mismatch
INT-NE-IP_Subnet_Unknown OPE100 card 2-193
OPE100 card 2-196, 2-197 NE_Cfg_Validation_Err
OPE100 card 2-192
L NE_Config_Bp_Mismatch
LED OPE100 card 2-189
card alarms 1-3 NE-Card_Fault alarm 2-163
RAU alarms 1-3 NE-Card_Out alarm 2-158
log NE-Date_Time_Unknown alarm 2-155
action log NE-Invt_Write_Jumper_Fitted alarm 2-165
clearing faults 1-2 NE-Lan_Alarm 2-151
LP-Excessive errors 2-89 NE-Unexpected_Card alarm 2-160
LP-Excessive_Errors (EXC) alarm 2-89 NE-Unexpected_LAN alarm 2-152
LP-Label Unequipped alarm 2-105, 2-120 NE-Wrong_Card alarm 2-164
LPOM_QOSV_15M 2-112, 2-113
LPOM-Excessive_Errors (EXC) alarm 2-114 O
LP-Path Label Mismatch (PLM) alarm 2-93, OS alarms 2-12
2-118 OS-Disable_Laser_Shutdown alarm 2-13
LP-Remote Defect Indicator (RDI) OS-Laser_Shutdown alarm 2-14
alarm 2-95 OS-Optical_Power_High alarm 2-12
LP-Remote Error Indication (REI)
alarm 2-97
LP-Signal Degrade (DEG) alarm 2-91 P
LP-Signal_Fail (SF) alarm 2-102 Port Alarm Monitoring
LP-Trail Indentifier Mismatch (TIM) Monitoring
alarm 2-103, 2-116 port alarms 1-8, 2-2, 2-21
PPI-Alarm Indication Signal (AIS)
alarm 2-126
M PPI-Excessive errors (EXC) alarm 2-15,
maintenance 2-127
philosophy 1-1 PPI-Loopback On alarm 2-132
Major (alarm severity) 1-7 PPI-Loss Of Frame (LOF) alarm 2-130,
Minor (alarm severity) 1-7 2-133
MS-Alarm_Indication_Signal (AIS) PPI-Loss Of Multiframe (LOM) alarm 2-131
alarm 2-30 PPI-Loss Of Signal (LOS) alarm 2-124
MS-Excessive_Errors (EXC) alarm 2-36 PPI-Signal Degrade (DEG) alarm 2-128
MSP FOP_INV alarm 2-187

Index 3-3
PPI-Transmit Fail (TF) alarm 2-17, 2-122

PPI-Unexpected Signal alarm 2-129
Prompt (RAU category) 1-7
PS-Power_Fail alarm 2-154
Q
Qecc_Comms_Fail alarm 2-144
R
Rack alarm unit (RAU) 3
alarm category 1-5
rack alarm unit (RAU)
alarm indications 1-3
RS-Loopback_On alarm 2-27
RS-Loss_of_Signal (LOS) alarm 2-21
RS-Trace_Identifier_Mismatch (TIM)
alarm 2-25
RS-Unexpected_Signal alarm 2-20
S
Sync-ESO_Source_Not_Primary
alarm 2-138
SYNC-External_Sync_LOS alarm 2-141
Sync-Holdover alarm 2-139
Sync-SETG_Fail alarm 2-136
Sync-Source_Not_Primary alarm 2-140
Sync-Unexpected_Signal alarm 2-137
T
TU-Alarm_Indication_Signal alarm 2-85
TU-Loss_of_Pointer (LOP) alarm 2-86
U
Unexpected_Equip alarm 2-182
Unexpected_SW_Version alarm 2-156
V
VC-EDD
OPE100 card 2-194
W
Warning (alarm severity) 1-7
Wrong_Equip alarm 2-184

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 Networks
Optical Metro 4200
Copyright © 2004, 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-1233-543
Product Release Number: Release 4.1
Status: Standard
Date: April 2004
Printed in England

OM4200 Alarm Clearing Procedures

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

OM4200 Alarm Clearing Procedures

Transféré par

Droits d'auteur :

Formats disponibles

323-1233-543

Nortel Networks Optical Metro

Nortel Networks Optical Metro 4200

Document Number: 323-1233-543

Copyright © 2004 Nortel Networks, All Rights Reserved

Netscape is a trademark of Netscape Communications Corporation.

Optical Metro 4200 Alarm Clearing Procedures

Alarm Clearing Procedures

• 1+1 Multiplex Section Protection for Quad STM-1o

• Quad STM-1e tributary card NTEU16QA

323-1233-543 Release 4.1 Standard

Clearing alarms 2-1

OS-Optical Power High 2-12

OS-Disabled Laser Shutdown 2-13

OS-Laser Shutdown 2-14

ES-Coded mark inversion violation 2-15

Optical Metro 4200 Alarm Clearing Procedures

Corrective actions 2-16

ES-Transmit Fail (TF) 2-17

ES-Code violation quality of service violation

ES-Code violation quality of service violation

RS-Unexpected signal 2-20

RS-Loss of Signal (LOS) 2-21

RS-Loss of Frame (LOF) 2-23

RS-Trace Identifier Mismatch (TIM) 2-25

323-1233-543 Release 4.1 Standard

RS-Quality of service violation (15 minute) 2-28

RS-Quality of service violation (24 hour) 2-29

MS-Alarm Indication Signal (AIS) 2-30

MS-Remote Defect Indicator (RDI) 2-32

MS-Remote Error Indicator (REI) 2-34

MS-Excessive errors (EXC) 2-36

Optical Metro 4200 Alarm Clearing Procedures

MS-Signal Degrade (DEG) 2-38

MS-Quality of service violation (15 minute) 2-40

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

MS-Far end quality of service violation (15 minute) 2-42

MS-Far end quality of service violation (24 hour) 2-43

AU-Alarm Indication Signal (AIS) 2-44

323-1233-543 Release 4.1 Standard

AU-Loss of Pointer (LOP) 2-46

HP-Excessive errors (EXC) 2-47

HP-Signal Degrade (DEG) 2-49

HP-Trace Identifier Mismatch (TIM) 2-51

HP-Remote Defect Indicator (RDI) 2-53

HP-Loss of Multiframe (LOM) 2-55

HP-Remote Error Indicator (REI) 2-57

Optical Metro 4200 Alarm Clearing Procedures

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

HP-Quality of service violation (15 minute) 2-69

HP-Quality of service violation (24 hour) 2-70

323-1233-543 Release 4.1 Standard

HP-Far end quality of service violation (15 minute) 2-71

HP-Far end quality of service violation (24 hour) 2-72

HPOM quality of service violation

HPOM quality of service violation

HPOM-far end quality of service violation (15 minute) 2-75

HPOM-far end quality of service violation

HPOM-Excessive errors (EXC) 2-77

Optical Metro 4200 Alarm Clearing Procedures