Вы находитесь на странице: 1из 208

323-1123-543

SDH TRANSMISSION

Nortel TN-4XE

Alarm Clearing Procedures

Release 3.01 Standard March 2000

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

SDH TRANSMISSION

Nortel TN-4XE

Alarm Clearing Procedures

Document Number: 323-1123-543 Product Release Number: Release 3.01 Status: Standard Date: March 2000

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

Printed in England

The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTEL NETWORKS CONFIDENTIAL:The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

*NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are trademarks of Nortel Networks.

Netscape is a trademark of Netscape Communications Corporation. OPTERA is a trademark of Cambrian Systems Inc.

ii

VT100 is a trademark of Digital Equipment Corporation. Unix and the X device are trademarks of The Open Group RS-232 is a trademark of the Electronic Industries Association CNet is a trademark of CNet Technology Inc Ethernet is a trademark of Xerox Corporation

iii

Publication history

March 2000

Release 3 Standard introduces the following TN-4XE features:

• Three channel, 34/45Mbit/s PDH electrical tributary card

• 1+1 card protection for 34/45Mbit/s and STM-1e/140Mbit/s tributaries

• Multiplex section protection for STM-1 tributary cards and STM-4 aggregate cards

July 1999

Release 2.2 Standard introduces the following TN-4XE features:

 

SETS (synchronisation function) and SEMF (Shelf Controller function) redundancy

STM-1e/140 Mbit/s, single channel, tributary card

Performance monitoring to G.826

New connection types (unprotected PDH tributary to tributary, time slot interchange on aggregate to aggregate)

February 1999

Release 2.1 Standard introduces the following TN-4XE features:

Engineering Order Wire card

STM-4o optical aggregate long haul 1550 nm

Rack fan tray

December 1998

Release 2.0 Standard introduces the following TN-4XE features:

• Up to eight 2 Mbit/s PDH electrical tributary cards (75 ohm and 120 ohm) each with 32 ports

• New connection types (tributary to tributary, ring to ring, dual tributary to aggregate)

• Installation in 19 inch (482 mm) equipment rack

iv

June 1998

Release 1 Standard introduces the following TN-4XE features:

• SDH add drop multiplexer architecture

• STM-4o optical aggregate short haul 1310 nm

• Up to eight STM-1 optical tributaries short haul 1310 nm with two ports

• VC-12, VC-3 and VC-4 connectivity

• Sub-network connection protection and path protection

• Management from the EC-1 or CAT with HTML browser interface

end of chapter

v

Contents

About this document

 

xi

Associated documents

xi

Introduction

1-1

Maintenance philosophy

 

1-1

Alarm clearing

1-1

Response to action logs

 

1-2

Defect detection and alarm reporting

1-2

Card LEDs

1-2

Rack alarm unit (RAU) indications on the subrack

1-2

Correlation (fault masking)

1-3

Alarm severity and RAU category

1-4

Alarm severity states

1-6

RAU categories

1-6

Consequent actions and alarms

1-7

Clearing alarms

 

2-1

Alarm instances

2-10

 

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

vi

Contents

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

Contents

vii

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

Index

3-1

Figures

viii

Contents

Figure 1-1

RAU indicators on the Upper EOS card

1-3

Figure 1-2

Card Alarm Correlation hierarchy

1-4

Figure 1-3

Traffic and BER alarm correlation hierarchy Hierarchy of alarm correlation for PDH traffic

1-5

Figure 1-4

Procedures

Procedure 2-1

Es-cmi-violation alarm clearing

2-15

Procedure 2-2

ES_TF alarm clearing

2-16

Procedure 2-3

Es_cv_qosv_15M alarm clearing

2-17

2-18

Procedure 2-4

ES-CV-QOSV-24H alarm clearing

Procedure 2-5

Rs-los alarm clearing

2-21

Procedure 2-6

Rs_lof alarm clearing

2-23

Procedure 2-7

Rs-exc alarm clearing

2-25

Procedure 2-8

Rs-tim alarm clearing

2-27

Procedure 2-9

Rs_qosv_15M alarm clearing

2-29

2-30

Procedure 2-10

Rs_qosv_24H alarm clearing

Procedure 2-11

MS-AIS alarm clearing

2-32

Procedure 2-12

MS-RDI alarm clearing

2-34

Procedure 2-13

MS-REI alarm clearing

2-36

Procedure 2-14

MS-EXC alarm clearing

2-38

Procedure 2-15

MS_DEG alarm clearing

2-40

Procedure 2-16

Ms_qosv_15M alarm clearing

2-41

2-42

Procedure 2-17

Ms_qosv_24H alarm clearing

Procedure 2-18

Ms_fe_qosv_15M alarm clearing

2-43

Procedure 2-19

Ms_fe_qosv_24H alarm clearing

2-44

Procedure 2-20

AU-AIS alarm clearing

2-46

Procedure 2-21

AU-LOP alarm clearing

2-47

Procedure 2-22

HP-EXC alarm clearing

2-49

Procedure 2-23

HP-DEG alarm clearing

2-51

Procedure 2-24

HP-TIM alarm clearing

2-53

Procedure 2-25

HP-RDI alarm clearing

2-55

Procedure 2-26

HP-LOM alarm clearing

2-57

Procedure 2-27

HP-REI alarm clearing

2-58

Procedure 2-28

HP-PLM alarm clearing

2-60

Procedure 2-29

HP-UNEQ alarm clearing

2-62

Procedure 2-30

HP-SF alarm clearing

2-64

Procedure 2-31

INT-HP-IP-BUFFER alarm clearing

2-65

Procedure 2-32

INT-HP-OP-BUFFER alarm clearing

2-66

Procedure 2-33

Hp_qosv_15M alarm clearing

2-67

2-68

Procedure 2-34

Hp_qosv_24H alarm clearing

Procedure 2-35

Hp_fe_qosv_15M alarm clearing

2-69

Procedure 2-36

Hp_fe_qosv_24H alarm clearing

2-70

Procedure 2-37

HPOM-EXC alarm clearing

2-72

2-74

Procedure 2-38

HPOM-TIM alarm clearing

Procedure 2-39

HPOM-PLM alarm clearing

2-76

2-78

Procedure 2-40

HPOM-UNEQ alarm clearing

Procedure 2-41

TU-AIS alarm clearing

2-79

Procedure 2-42

TU-LOP alarm clearing

2-80

Procedure 2-43

INT-TU-AIS alarm clearing

2-81

2-82

Procedure 2-44

INT-TU-LOP alarm clearing

Procedure 2-45

LP-EXC alarm clearing

2-83

Procedure 2-46

LP-DEG alarm clearing

2-85

Procedure 2-47

LP-PLM alarm clearing

2-87

Procedure 2-48

LP-RDI alarm clearing

2-89

Procedure 2-49

LP-REI alarm clearing

2-90

Contents

ix

Procedure 2-50

INT-LP-IP-BUFFER alarm clearing

2-92

Procedure 2-51

INT-LP-OP-BUFFER alarm clearing

2-94

Procedure 2-52

LP-SF alarm clearing

2-95

2-97

Procedure 2-53

LP-TIM alarm clearing

Procedure 2-54

LP-UNEQ alarm clearing

2-99

Procedure 2-55

Lp_qosv_15M alarm clearing

2-100

2-101

Procedure 2-56

Lp_qosv_24H alarm clearing

Procedure 2-57

Hp_fe_qosv_15M alarm clearing

2-102

2-103

Procedure 2-58

Lp_fe_qosv_24H alarm clearing

Procedure 2-59

LPOM-EXC alarm clearing

2-105

2-107

2-109

Procedure 2-60

LPOM-TIM alarm clearing

Procedure 2-61

LPOM-PLM alarm clearing

Procedure 2-62

LPOM-UNEQ alarm clearing

2-111

Procedure 2-63

PPI-TF alarm clearing

2-113

2-115

2-117

2-118

Procedure 2-64

PPI-LOS alarm clearing

Procedure 2-65

PPI-EXC alarm clearing

Procedure 2-66

PPI-DEG alarm clearing

Procedure 2-67

PPI-UNEXP_SIGNAL alarm clearing

2-119

Procedure 2-68

PPI-LOF alarm clearing

2-120

2-121

2-123

Procedure 2-69

PPI-LOM alarm clearing

Procedure 2-70

PPI-T-LOF alarm clearing

Procedure 2-71

PPI_CV_qosv_15M alarm clearing

2-124

Procedure 2-72

PPI_CV_qosv_24H alarm clearing

2-125

Procedure 2-73

SYNC-SETG_Fail alarm clearing

2-126

Procedure 2-74

SYNC-Ext_Sync_LOS alarm clearing

2-132

Procedure 2-75

SYNC-SETG_frequency_suspect alarm clearing

2-133

2-134

Procedure 2-76

SYNC-SOURCE-OUT-OF-LIMITS alarm clearing

Procedure 2-77

SYNC-LOCK-FAIL alarm clearing

2-135

Procedure 2-78

Qecc_Comms_Fail alarm clearing

2-137

Procedure 2-79

Spi-Comms_Fail alarm clearing

2-139

 

Procedure 2-80

NE-Card_Out alarm clearing

2-150

Procedure 2-81

NE-Unexpected_Card alarm clearing

2-152

Procedure 2-82

NE-Card_Fail alarm clearing

2-153

Procedure 2-83

NE-Wrong_Card alarm clearing

2-155

 

Procedure 2-84

INT-NE_Config_Corrupt_Bank 2-158

Procedure 2-85

INT-NE_Config_All_Banks_Corrupt 2-159

 

Procedure 2-86

INT NE-Config_Avail_Bank_Corrupt

2-161

Procedure 2-87

INT NE-Cfg_sw_mismatch

2-162

Procedure 2-88

INT NE-Cfg_Audit_Mismatch

2-164

2-165

Procedure 2-89

INT NE-Cfg_validation_error

xiii

About this document

This document contains procedures to locate and clear alarm indications on the TN-4XE subrack.

Audience

This document is intended for use by the following people:

• field maintenance personnel

• maintenance engineers

• system test engineers

• network administrators

Associated documents

The following documents are referred to in this document:

Documentation overview and safety, 323-1123-090

System Description, 323-1123-100

Software and Hardware Description, 323-1123-101

Installation Procedures, 323-1123-201

Provisioning and Operations Procedures, 323-1123-310

Network Surveillance Procedures, 323-1123-510

Maintenance Procedures, 323-1123-547

• EC-1 User Procedures, 323-1091-402

xiv

Technical support and information

So far as Nortel Networks is aware the information in this document is correct. If, however, you discover any errors or have comments regarding the presentation of the content, please send details by email to:

IONNTPS@nortelnetworks.com

Nortel Networks provides a comprehensive technical support service for it’s customers. The Nortel Networks Service Desk may be contacted between the hours of 08:30 and 17:00, Monday to Friday (UK local time), using the following FAX or telephone numbers:

United Kingdom

Freephone:

0800 626 881

Telephone:

0208 361 4693

FAX:

0208 945 3456

International

Telephone:

+44 208 361 4693

FAX:

+44 208 945 3456

EMC conformance

This product/product family complies with the essential protection requirements of the EMC Directive 89/336/EEC as

This product/product family complies with the essential protection requirements of the EMC Directive 89/336/EEC as amended by 92/31/EEC, when it is properly installed and maintained and when it is used for the purposes for which it is intended.

Code: EDEU0001 Issue: 2 Template: v5;970307 Declaration of Conformity Suppliers Name & Address: Nortel Networks,

Code: EDEU0001

Issue: 2

Template: v5;970307

Declaration of Conformity

Suppliers Name & Address:

Nortel Networks, of Doagh Road, Newtownabbey, County Antrim, Northern Ireland, BT36 6XA

We hereby declare that the products identified in Section 1 comply with the standards listed in Section 2 and fulfil our obligations under the EU Directives listed in Section 3.

Section 1 - Products Covered

Product Name

Product Type

TN-4XE

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

Section 2 - Standards Applied

The Product described above is in conformity with the following standards:

Stds

Standard Number

Edition

Amendments

Subject of Standard

Ref

1

EN 55022

1995

 

Emissions from IT Equipment

1

EN 50082-1

1992

 

Generic Immunity

2

EN 60950

1992

1,2,3 & 4

Safety of IT equipment

2

EN 60825-1

1994

1

Safety of Laser Products

Section 3 - European Union Directives

Directive

Abbreviated Directive Title

Stds

CE Marking

Number

Ref

Information

(if applicable)

89/336/EEC

EMC Directive

1

n/a

92/31/EEC

Amendment to EMC Directive

n/a

n/a

93/68/EEC

CE Marking Amending Directive

n/a

n/a

Section 4 - Authority of Issuer

Declaration Issued By:

Peter Schuddeboom

Position of Issuer:

Signed:

Date:

VP, ION Product Development

of Issuer: Signed: Date: VP, ION Product Development John Freebairn Senior Manager, Customer Satisfaction &

John Freebairn

Senior Manager, Customer Satisfaction & Quality

Senior Manager, Customer Satisfaction & Quality The instructions for installation, use and maintenance form

The instructions for installation, use and maintenance form part of the product compliance and must be observed.

1

1-1

Introduction

1-

Maintenance philosophy

This section describes the maintenance method for locating and clearing alarm indications.

The maintenance philosophy is to identify the source of a fault without the need for difficult on-site maintenance. At all times, the maintenance procedures try to prevent interrupting traffic.

Procedures to locate faults use all the indications and techniques provided by the TN-4XE and the Element Controller (EC-1) or CAT. TN-4XE has failure indicator lamps on the hardware and also has alarm or action log reports on the user interface.

Alarms and action logs descriptions are in the System Description,

323-1123-100.

Alarm clearing

To locate and clear a fault in a TN-4XE continue as follows:

1 Use the EC to open the Alarm Monitor tool. View the active alarm summaries in the EC’s span of control (see Element Controller, User Procedures, 323-1091-402). From the active alarm list, identify the NE on which the highest severity alarm has occurred.

2 Log in to the NE and clear the alarms one channel and one direction at a time, starting with the highest-severity alarm. If required, send a person to the NE site to do maintenance procedures and card replacement.

3 Refer to Chapter 2 for detailed step-by-step procedures for clearing alarms.

WARNING Safety guidelines Refer to safety information in Documentation Overview and Safety , 323-1123-090.

WARNING

Safety guidelines

Refer to safety information in Documentation Overview and Safety, 323-1123-090.

1-2

Introduction

CAUTION Risk of traffic interruption The TN-4XE Network Element is a high capacity system. Be

CAUTION

Risk of traffic interruption

The TN-4XE Network Element is a high capacity system. Be careful not to interrupt traffic or perform any task without a valid reason. Where possible reroute the traffic through another path before replacing any traffic-carrying circuit pack.

Response to action logs

TN-4XE action logs are information messages that the Network Element or the EC generate for a span of control that includes the TN-4XE NE.

Often, log messages require no action by the maintenance personnel. However, some logs provide additional information for identified alarms or trouble conditions.

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

Defect detection and alarm reporting

The TN-4XE subrack provides local alarm indications to aid identifying the source of a problem.

Card LEDs All cards have several light-emitting diodes (LEDs) on the faceplates as an aid to fault finding. Card LED descriptions are in the Software and Hardware Description, 323-1123-101.

Traffic cards LEDs The LEDs on the traffic cards are:

the Fail LED (red) indicates a card fail, power fail or watchdog timer fail

the Active LED (green) indicates that the card is in service. Do not remove the card while this LED is on.

the LOS LED (yellow) indicates a loss of signal

EOS cards LEDs The two colour Fail LED on the EOS cards indicates:

red, a firmware, LAN or low voltage failure has occurred

yellow, a fail on the -48V supply has occurred

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

Introduction

1-3

Figure 1-1 RAU indicators on the Upper EOS card

1

 
FAIL

FAIL

 

ACK ALARM

ACK ALARM  
 
 
 

ALARM

RAU indicators

  FAIL   ACK ALARM     ALARM RAU indicators REC ATT NPUT    

REC ATT

NPUT

NPUT    
   

Correlation (fault masking)

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

Each alarm in the correlation process has a position in a correlation hierarchy which defines the masking relationship between alarms. An alarm raised at any point in the hierarchy blocks reporting of alarms which are lower in the hierarchy.

Also, if a defect occurs, the multiplexer can report a low severity alarm before a higher severity alarm. To make sure operators view only higher severity alarm reports, the software applies a fault masking check period before reporting the alarm.

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

1-4

Introduction

Figure 1-2 Card Alarm Correlation hierarchy

Equipment Alarms Card Alarms Card Fault Card Fail Wrong Card Unexpected Card
Equipment Alarms
Card Alarms
Card Fault
Card Fail
Wrong Card
Unexpected Card

Any alarm raised on the Card/Slot instance

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

Alarm severity and RAU category

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

The operator can change the RAU category for each alarm. If the operator changes the RAU category for an alarm the alarm severity also changes automatically.

Introduction

1-5

Figure 1-3 Traffic and BER alarm correlation hierarchy

1

RS LOS RS UNEXP SGNL ES CMI RS LOF RS TIM MS RDI RS COMMS
RS LOS
RS UNEXP SGNL
ES CMI
RS LOF
RS TIM
MS RDI
RS COMMS FAIL
MS COMMS FAIL
MS AIS
MS REI
MS EXC
MS DEG
AU LOP
FOP_PAM
FOP_SCM
FOP_INV
AU AIS
HPOM EXC
HPOM TIM
HPOM PLM
HPOM UNEQ
HP-EXC
HP DEG
INT HP OP BUFF
HP RDI
HP LOM
HP TIM
HP PLM
HP UNEQ
PPI LOF-T
HP REI
TU LOP
TU AIS
INT TU LOP
LPOM EXC
LPOM TIM
LPOM PLM
INT TU AIS
LPOM UNEQ
LP EXC
LP RDI
INT LP OP BUFF
LP TIM
LP UNEQ
LP DEG
LP PLM
LP-REI

= Consequent Action configuration dependent

= Masked if TU type is TU-1

1-6

Introduction

Figure 1-4 Hierarchy of alarm correlation for PDH traffic

PPI LOS PPI UNEXP SGNL PPI EXC PPI DEG PPI AIS INT LP IP BUFF
PPI LOS
PPI UNEXP SGNL
PPI EXC
PPI DEG
PPI AIS
INT LP IP BUFF
INT HP IP BUFF
PPI LOF
PPI LOM

Alarm severity states The following list details the different alarm severity states:

Critical alarm- a failure which disables or decreases the quality of services provided by the network. Optical line failures and service-carrying card failures are examples of critical alarms.

Major alarm- a failure which decreases the quality of services provided by the network, but not to the same degree as a Critical failure. RS-TIM is an example of a major alarm.

Minor alarm- a failure in the network or a failure which does not decrease the quality of service provided by the network. AIS and protected card failures are examples of minor alarms.

Warning alarm- shown by the CAT or Element Controller but does not provide card, subrack, or rack alarm indications or extensions. A warning alarm indicates a condition exists that requires action.

RAU categories Each alarm severity (except warning) matches a rack alarm unit category:

• Prompt maintenance alarm (Critical alarm) - an alarm that requires immediate action at all times. Generally, this alarm passes to a maintenance/control point when the station is without an operator.

• Deferred maintenance alarm (Major alarm) - an alarm that does not require immediate action outside normal hours. Generally, this alarm passes to a maintenance/control point when the station is without an operator.

• In Station maintenance alarm (Minor alarm) - an alarm that does not require action outside normal hours.

Introduction

1-7

Consequent actions and alarms

1

Consequent actions are events which occur as a result of a traffic or BER alarm to indicate the condition of the received signal. There are three main consequent actions:

• AIS indication (internal to the multiplexer)

• Remote defect indication (RDI) or remote error indication (REI) inserted on the return path overhead

• an SNC-P or path protection switch

The operator can configure consequent actions on or off for the complete NE or for each alarm type. For a consequent action to be enabled all the following conditions must be true:

• the feature is enabled (for example Path Trace)

• alarm reports are set to On or Monitor

• the consequent actions are enabled for the NE

• the consequent action is enabled for the alarm type

Refer to Provisioning and Operations Procedures, NTP 323-1123-310 for the procedures to configure consequent actions.

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

end of chapter

of the consequent actions for each alarm are in Chapter 2. end of chapter Nortel TN-4XE

2-1

2

Clearing alarms

2-

This chapter describes how to locate and clear alarms on the TN-4XE subrack.

To locate and clear a specific alarm, refer to the following procedures.

Optical system alarms

Alarm

Displayed as

Page

OS-Optical Power High

Os_optical_power_high

2-11

OS-Laser Bias High

Os_laser_bias_high

2-12

OS-Disabled Laser Shutdown

Os_dis_laser shutdown

2-13

OS-Laser Shutdown

Os_laser_shutdown

2-14

Electrical section alarms

Alarm

Displayed as

Page

es-coded mark inversion violation

es_cmi_violation

2-15

es-transmit fail

es_tf

2-16

es-code violation-quality of service violation 15 minute

es_cv_qosv_15M

2-17

es-code violation-quality of service violation 24 hour

es_cv_qosv_24H

2-18

2-2

Clearing alarms

Regenerator section alarms

Alarm

Displayed as

Page

RS-Unexpected signal

Rs_unexp_signal

2-19

RS-Loss of Signal (LOS)

Rs_los

2-20

RS-Loss of Frame (LOF)

Rs_lof

2-22

RS-Excessive errors (EXC)

Rs_exc

2-24

RS-Trace Identifier Mismatch (TIM)

Rs_tim

2-26

RS-Loopback On

Rs_loopback_on

2-28

RS-quality of service violation 15 minute

RS_qosv_15M

2-29

RS-quality of service violation 24 hour

RS_qosv_24H

2-30

Multiplexer section alarms

Alarm

Displayed as

Page

MS-Alarm Indication Signal (AIS)

Ms_ais

2-31

MS-Remote Defect Indicator (RDI)

Ms_rdi

2-33

MS-Remote Error Indicator (REI)

Ms_rei

2-35

MS-Excessive errors (EXC)

Ms_exc

2-37

MS-Signal Degrade (DEG)

Ms_deg

2-39

MS-quality of service violation 15 minute

Ms_qosv_15M

2-41

MS-quality of service violation 24 hour

Ms_qosv_24H

2-42

MS-far end quality of service violation 15 minute

Ms_fe_qosv_15M

2-43

MS-far end quality of service violation 24 hour

Ms_fe_qosv_24H

2-44

Administrative Unit alarms

Alarm

Displayed as

Page

AU-Alarm Indication Signal (AIS)

Au_ais

2-45

AU-Loss of Pointer (LOP)

Au_lop

2-47

Clearing alarms

2-3

Higher order path alarms

Alarm

Displayed as

Page

HP-Excessive errors (EXC)

Hp_exc

2-48

HP-Signal Degrade (DEG)

Hp_deg

2-50

HP-Trace Identifier Mismatch (TIM)

Hp_tim

2-52

HP-Remote Defect Indicator (RDI)

Hp_rdi

2-54

HP-Loss of Multiframe (LOM)

Hp_lom

2-56

HP-Remote Error Indicator (REI)

Hp_rei

2-58

HP-Payload Label Mismatch (PLM)

Hp_plm

2-59

HP-Unequipped (UNEQ)

Hp_uneq

2-61

HP-Signal Fail (SF)

Hp_sf

2-63

Internal high order input buffer overflow

Int_hp_ip_buffer

2-65

Internal high order output buffer overflow

Int_hp_op_buffer

2-66

HP-quality of service violation 15 minute

Hp_qosv_15M

2-67

HP-quality of service violation 24 hour

Hp_qosv_24H

2-68

HP-far end quality of service violation 15 minute

Hp_ fe_qosv_15M

2-69

HP-far end quality of service violation 24 hour

Hp_fe_qosv_24H

2-70

Higher order path alarms with overhead monitoring

 

Alarm

Displayed as

Page

HPOM-Excessive errors (EXC)

Hpom_exc

2-71

HPOM-Trail Identifier Mismatch (TIM)

Hpom_tim

2-73

HPOM-Payload Label Mismatch (PLM)

Hpom_plm

2-75

HPOM-Unequipped (UNEQ)

Hpom_uneq

2-77

2

2-4

Clearing alarms

Transport unit alarms

Alarm

Displayed as

Page

TU-Alarm Indication Signal (AIS)

Tu_ais

2-71

TU-Loss of Pointer (LOP)

Tu_lop

2-79

INT-TU-Alarm Indication Signal (AIS)

Int_tu_ais

2-81

INT-TU-Loss of Pointer (LOP)

Int_tu_lop

2-82

Low order path alarms

Alarm

Displayed as

Page

LP-Excessive errors (EXC)

Lp_exc

2-83

LP-Signal Degrade (DEG)

Lp_deg

2-84

LP-Payload Label Mismatch (PLM)

Lp_plm

2-86

LP-Remote Defect Indicator (RDI)

Lp_rdi

2-88

LP-Remote Error Indication (REI)

Lp_rei

2-90

INT-LP-Input Buffer Overflow

Lp_lp_buffer

2-91

INT LP-Output Buffer Overflow

Lp_op_buffer

2-93

LP-Signal Fail (SF)

Lp_sf

2-95

LP-Trail Identifier Mismatch (TIM)

Lp_tim

2-96

LP-Label Unequipped

Lp_uneq

2-98

LP-quality of service violation 15 minute

Lp_qosv_15M

2-100

LP-quality of service violation 24 hour

Lp_qosv_24H

2-101

LP-far end quality of service violation 15 minute

Lp_fe_qosv_15M

2-102

LP-far end quality of service violation 24 hour

Lp_fe_qosv_24H

2-103

Low order path alarms with overhead monitoring

 

Alarm

Displayed as

Page

LPOM-Excessive Errors (EXC)

Lpom_exc

2-104

Clearing alarms

2-5

Alarm

Displayed as

Page

LPOM-Trail Identifier Mismatch (TIM)

Lpom_tim

2-106

LPOM-Payload Label Mismatch (PLM)

Lpom_plm

2-108

LPOM-Unequipped (UNEQ)

Lpom_uneq

2-110

PDH physical interface alarms

Alarm

Displayed as

Page

PPI-Transmit Fail (TF)

Ppi_tf

2-112

PPI-Loss Of Signal (LOS)

Ppi_los

2-114

PPI-Alarm Indication Signal (AIS)

Ppi_ais

2-116

PPI-Excessive errors (EXC)

Ppi_exc

2-117

PPI-Signal Degrade (DEG)

Ppi_deg

2-118

PPI-Unexpected Signal

Ppi_unexp_signal

2-119

PPI-Loss of Frame (LOF)

Ppi_lof

2-120

PPI-Loss of Multiframe (LOM)

Ppi_lom

2-121

PPI-Loopback On

Ppi_loopback_on

2-122

PPI-Loss of Frame - transmit (T-LOF)

Ppi_T_lof

2-123

PPI-code violation-quality of service violation 15 minute

Ppi_cv_qosv_15M

2-124

PPI-code violation-quality of service violation 24 hour

Ppi_cv_qosv_24H

2-125

2

2-6

Clearing alarms

Synchronization alarms

Alarm

Displayed as

Page

Sync-SETG Fail

Sync_setg_fail

2-126

Sync-Unexpected signal

Sync_unexp_signal

2-127

Sync-ESO Source Not Primary

Sync_eso_src_not_primary

2-128

Sync-Holdover

Sync_holdover

2-129

Sync-Source Not Primary

Sync_src_not_primary

2-130

Sync-External Sync Loss Of Signal

Sync_ext_sync_los

2-131

Sync-SETG Frequency suspect

Sync_frequency_suspect

2-133

Sync-Source out of limits

Sync_source_out _of_limits

2-134

Sync-Lock fail

Sync_lock_fail

2-135

Clearing alarms

2-7

Miscellaneous alarms

Alarm

Displayed as

Page

Qecc Comms Fail

Qecc_comms_fail

2-136

Misc INT NE-Spi Comms Fail

Int_ne_spi_comms_fail

2-139

Misc EA-Ext inp <1-8>

Ea_ext_inp

2-140

Misc INT NE-Configuration Corrupt

Int_ne_config_corrupt

2-141

Misc NE-Lan Alarm

Ne_lan_alarm

2-142

Misc NE-Unexpected LAN

Ne_unexpected_lan

2-143

Misc INT NE-Config bp mismatch

Int_ne_config_bp_mismatch

2-144

Misc Ps-power fail

Ps_power_fail

2-145

Misc NE-Date time unknown

Ne_date_time_unknown

2-146

Misc Unexpected SW version

Unexp_sw_version

2-147

Misc Internal 1 second clock loss of signal

Int_ne_1s_clk_los

2-148

Card alarms

Alarm

Displayed as

Page

Card NE-Card Out

Ne_card_out

2-149

Card NE-Unexpected Card

Ne_unexpected_card

2-151

Card NE-Card Fail

Ne_card_fail

2-153

Card NE-Card Fault

Ne_card_fault

2-154

Card NE-Wrong Card

Ne_wrong_card

2-155

Card NE-Invt Write Jumper Fitted

Ne_invt_wri_jumper_fitted

2-156

Card NE-Minor card mismatch

Ne_minor_card_mismatch

2-157

2

2-8

Clearing alarms

Configuration alarms

Alarm

Displayed as

Page

Config INT NE-Configuration Corrupt Bank

Int_ne_cfg_corrupt_bank

2-158

Config INT NE-Configuration All Banks Corrupt

Int_ne_cfg_all_banks_corrupt

2-159

Config INT NE-Configuration Available Bank Corrupt

Int_ne_cfg_avail_bank_corrupt

2-160

Config INT NE-Configuration Software Mismatch

Int_ne_cfg_sw_mismatch

2-162

Config INT NE-Configuration Audit Mismatch

Int_ne_cfg_audit_mismatch

2-164

Config INT NE-Configuration Validation Error

Int_ne_cfg_validation_error

2-165

Config INT NE-Standby Configuration Software Unstable

Int_ne_stdby_cfg_sw_unstab

2-166

Config INT NE-Standby Configuration Flash Corrupt

Int_ne_stdby_flash_crpt

2-167

Config INT NE-Standby Configuration Audit Mismatch

Int_ne_stdby_Cfg_Audit_Mism

2-168

atch

Config INT NE-Standby Configuration fail

Int_ne_stdby_cfg_fail

2-169

Clearing alarms

2-9

1+1 Card Protection alarms

Alarm

Displayed as

Page

Equipment fail

Equip_Fail

2-170

Equipment Out

Equip_Out

2-171

Unexpected Equipped

Unexpected_Equip

2-172

Cable error

Cable_Error

2-173

Wrong equipment

Wrong_Equip

2-174

Multiplex section protection alarms

Alarm

Displayed as

Page

Protection scheme mismatch

FOP_PAM

2-175

Channel mismatch

FOP_SCM

2-176

Invalid K bytes (Invalid command)

FOP_INV

2-177

Invalid K bytes (timeout)

FOP_TMOUT

2-178

2

2-10

Clearing alarms

Alarm instances

The following table details the alarm instances that are valid for each card type in a TN-4XE.

Table 2-1 Possible alarm instances

Card

<Slot-no>

<Port>

J<VC-4>

<KLM>

aggregate

6,8

1 1 to 4

 

111

to 373

STM-1o tributary

1 to 4, 11 to 14

1 or 2

1

111

to 373

STM-1e/140 Mbit/s tributary (STM-1e mode)

1 to 4, 11 to 14

1

1

111

to 373

STM-1e/140 Mbit/s tributary (140 Mbit/s mode)

1 to 4, 11 to 14

1

-

-

STM-1e/140 Mbit/s I/O card

2, 5, 10, 11,

1-

 

-

12

34/45 Mbit/s tributary (34 Mbit/s mode)

1 to 4, 11 to 14

1 to 3

-

-

34/45 Mbit/s tributary (45 Mbit/s mode)

1 to 4, 11 to 14

1 to 3

-

-

34/45 Mbit/s I/O card

2, 5, 10, 11,

1-

 

-

12

2 Mbit/s tributary

1

to 4, 11 to 14

1

to 32

- -

 

UEOS

15A

1

- -

 

LEOS (LAN)

15B

1

or 2

- -

 

LEOS (Synchronization)

15B

1

- -

 

Clearing alarms

2-11

OS OS-Optical Power High

Significance The laser or its related control loop has failed. As a result the optical power output exceeds the nominal limit by +4dB or greater (i.e. Optical Power High).

2

Note: This alarm also provides a hardwired Metallic Alarm signal to the RAU. The alarm does not respond to the Receive Attention button on the UEOS card.

Instance/Unit The multiplexer raises this alarm on an optical port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic hit on unprotected paths. Protection switch on protected paths.

Consequent action The laser is shutdown. This is a safety feature, although the laser output is still within the standard safe range.

Note: The laser shutdown is latched, the laser will remain off until the card is reseated or a cold restart is performed.

Resulting alarms

None

Possible causes Faulty aggregate card or STM-1o tributary card.

Corrective actions Re-seat the indicated card.

Switch off and restore power to the multiplexer.

If the alarm is still present replace the card. Refer to the Maintenance Procedures, 323-1123-547.

2-12

Clearing alarms

OS OS-Laser Bias High

Significance The laser bias current exceeds the nominal limits. This indicates that the laser performance has degraded and that the laser is nearing it’s end-of-life.

Instance/Unit This alarm is raised against an optical port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic on unprotected paths is affected. Temporary traffic hit on protected paths.

Consequent action None.

Possible causes Ageing of the laser on the indicated optical port.

Corrective actions Replace the indicated aggregate card or STM-1 tributary card. Refer to the Maintenance Procedures, 323-1123-547.

Clearing alarms

2-13

OS OS-Disabled Laser Shutdown

Significance The automatic laser shutdown (ALS) function is disabled on the indicated optical port.

2

Note: This alarm is raised against an optical port; however, the ALS function is enabled or disabled on a card basis.

Instance/Unit This alarm is raised against an optical port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Minor alarm.

Does not affect traffic.

Consequent action Automatic laser shutdown will not operate on the indicated port.

Possible causes The automatic laser shutdown (ALS) function has been disabled.

Corrective actions This alarm is only cleared when ALS is enabled. ALS is enabled by removing a plug-in link on the appropriate card. Refer to the Software and Hardware Description, 323-1123-101 for the position of the links on the cards.

2-14

Clearing alarms

OS OS-Laser Shutdown

Significance This alarm is raised when the laser on the specified optical port is shutdown by the automatic laser shutdown (ALS) circuit.

Instance/Unit This alarm is raised against an optical port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic is affected on unprotected paths. Temporary traffic hit on protected paths.

Consequent action None.

Possible causes Possible causes for the OS-Laser shutdown alarm are:

• RS_LOS alarm.

• Faulty aggregate or STM-1o tributary.

Corrective actions If the RS_LOS alarm is present, perform the alarm clearing procedures for that alarm.

If the RS_LOS alarm is not present, replace the indicated aggregate or STM-1o tributary. Refer to the Maintenance Procedures, 323-1123-547.

Clearing alarms

2-15

ES ES-Coded mark inversion violation

Significance The Es_cmi_violation alarm is raised when CMI violations exceed the threshold in an STM-1e signal.

2

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic is affected on unprotected paths. Temporary traffic hit on protected paths.

Consequent action If this port is the synchronization source for the multiplexer then a synchronization switch occurs. If the port is in the synchronization source hierarchy list, then the port is marked not available for synchronization.

Possible causes Possible causes for the Es_cmi_violation alarm are:

• Excessive attenuation in cable.

• Errored input signal

• Faulty STM-1e/140 Mbit/s tributary card.

Corrective actions

Procedure 2-1 Es-cmi-violation alarm clearing

Step

Action

1

Investigate preceding STM-1e equipment and cable for cause of errors.

If errors are intermittent, most likely cause is cabling and the connectors. If no errors from preceding equipment, go to step 2.

2

Replace the indicated STM-1e/140 Mbit/s tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547 for details.

If the alarm clears, the alarm clearing procedure is complete. If the alarm is still present, escalate the problem or replace subrack.

—end—

2-16

Clearing alarms

ES ES-Transmit Fail (TF)

Significance The STM-1e tributary output signal has fallen below a predefined threshold.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical Alarm

Loss of STM-1e traffic output

Consequent action None.

Possible causes Possible causes for the ES-TF alarm are:

• Cable fault.

• Faulty STM-1e/140 Mbit/s 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 still present, go to step 3.

3

Replace the indicated STM-1e/140 Mbit/s tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547, for replacement procedures.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

—end—

Clearing alarms

2-17

ES ES-Code violation quality of service violation (15 minute)

2

Significance The Es_cv_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAS active performance monitoring threshold has been broken within a 15 minute monitoring period.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Minor Alarm

Consequent action None.

Possible causes Possible causes for the The Es_cv_qosv_15M alarm are:

• Excessive attenuation in cable.

• Errored input signal

• Faulty STM-1e/140 Mbit/s 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—

2-18

Clearing alarms

ES ES-Code violation quality of service violation (24 hour)

Significance The Es_cv_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAS active performance monitoring threshold has been broken within a 24 hour monitoring period.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Minor Alarm

Consequent action None.

Possible causes Possible causes for the Es_cv_qosv_24H alarm are:

• Excessive attenuation in cable.

• Errored input signal

• Faulty STM-1e/140 Mbit/s 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 the cause of this alarm.

3

The Es_cv_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—

Clearing alarms

2-19

RS RS-Unexpected signal

Significance Indicates that an optical signal is present at a specified port, but the port has not been configured to receive the connection.

2

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Major alarm.

Does not affect traffic.

Consequent action None.

Possible causes Incorrect configuration of connections.

Corrective actions Configure the STM1 port as detailed in Provisioning and Operations Procedures, 323-1123-310.

2-20

Clearing alarms

RS RS-Loss of Signal (LOS)

Significance The indicated card detects the loss of the received signal.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic is affected on unprotected paths. Temporary traffic hit on protected paths.

Consequent action AIS is injected on the MS overhead of the transmitted path.

On optical cards, the laser is shut down by the ALS circuit (if ALS is enabled).

If this port is used as the synchronization source a synchronization switch occurs. If entered in the synchronization source hierarchy list, this port will be marked unavailable for synchronization.

Resulting alarm OS_laser_shutdown, Ms_ais alarms.

Possible causes Possible causes for the Rs-los alarm are:

• Faulty optical fibre or cable.

• Faulty local aggregate, STM-1o tributary or STM-1e tributary.

• Faulty far end aggregate, STM-1o tributary or STM-1e tributary.

Clearing alarms

2-21

Corrective actions

Procedure 2-5 Rs-los alarm clearing

Step

Action

2

1

Perform a ‘Local’ loopback on the indicated port (see Network Surveillance Procedures, 323-1123-510).

If the alarm is still present, remove the loopback and go to step 2.

If the alarm clears, remove the loopback and go to step 4.

2

Replace the local STM-N card. Refer to the Maintenance Procedures,

323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

3

If the far end port provides the current synchronization source, switch to an alternative source.

4

Perform a ‘Local’ loopback on the appropriate far end port (see Network Surveillance Procedures, 323-1123-510).

If a Rs_los alarm is present at the far multiplexer, remove the ‘Local’ loopback and go to step 5.

If a Rs_los alarm is not present at the far multiplexer, remove the ‘Local’ loopback and go to step 6.

5

Replace the far end STM-N card. Refer to the Maintenance Procedures,

323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

6

On optical cards, clean the receive optical connections at the local aggregate or STM-1o tributary and verify that the received optical power is in the correct range. Refer to Maintenance Procedures, 323-1123-547.

If the received optical power is not within range, go to step 7.

7

On optical cards, clean the transmit optical connections at the far aggregate or STM-1o tributary and verify that the transmit optical power at the far aggregate or STM-1o tributary is in the correct range. Refer to Maintenance Procedures, 323-1123-547.

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—

2-22

Clearing alarms

RS RS-Loss of Frame (LOF)

Significance The frame alignment algorithm detects loss of frame alignment (loss of framing pattern in the A1 and A2 bytes of the section overhead for three consecutive frames).

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic is affected on unprotected paths. Temporary traffic hit on protected paths.

Consequent action AIS is injected on the MS overhead of the transmitted path.

If entered in the synchronization source hierarchy list, this port will be marked unavailable for synchronization.

Resulting alarms

Ms_ais alarm.

Possible causes Possible causes for the Rs_lof alarm are:

• Faulty optical fibre or cable.

• Faulty local aggregate, STM-1o tributary or STM-1e tributary.

• Faulty far end aggregate, STM-1o tributary or STM-1e tributary.

Clearing alarms

2-23

Corrective actions

Procedure 2-6 Rs_lof alarm clearing

Step

Action

2

1

If the indicated STM-4o,STM-1o or STM-1e port provides the current synchronization source, switch to an alternative synchronization source.

2

Perform a loopback on the ‘Local’ card (see Network Surveillance Procedures, 323-1123-510).

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

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

3

Perform a ‘Local’ loopback on the appropriate far end card (see Network Surveillance Procedures, 323-1123-510).

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’ loopback and go to step 6.

4

If the far end port provides the current synchronization source, switch to an alternative source.

5

Replace the far end card. Refer to the Maintenance Procedures,

323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

6

On optical cards, clean the receive optical connections at the local aggregate or STM-1o tributary and verify that the received optical power is in the correct range. Refer to Maintenance Procedures, 323-1123-547.

If the received optical power is not within range, go to step 7.

7

On optical cards, clean the transmit optical connections at the far aggregate or STM-1o tributary and verify that the transmit optical power at the far aggregate or STM-1o tributary is in the correct range. Refer to Maintenance Procedures, 323-1123-547.

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—

2-24

Clearing alarms

RS RS-Excessive errors (EXC)

Significance The error rate of the BIP-8 error check (B1 overhead byte) exceeds the configured threshold.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Critical alarm

Traffic is affected on unprotected paths. Temporary traffic hit on protected paths.

Consequent action AIS is injected on the MS overhead of the transmitted path (the consequent action is configurable - default to off).

If entered in the synchronization source hierarchy list, this port will be marked unavailable for synchronization.

Possible causes Possible causes for the RS-EXC alarm are:

• Faulty optical fibre or connections.

• Faulty local aggregate or STM-1o tributary.

• Faulty far end aggregate or STM-1o tributary.

Clearing alarms

2-25

Corrective actions

Procedure 2-7 Rs-exc alarm clearing

Step

Action

2

1

If the indicated port provides the current synchronization source, switch to an alternative source.

2

Perform a ‘Local’ loopback on the local card (see Network Surveillance Procedures, 323-1123-510).

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

3

Replace the local card. Refer to the Maintenance Procedures, 323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

4

If the far end port provides the current synchronization source, switch to an alternative source.

5

Perform a ‘Local’ loopback on the appropriate far end card (see Network Surveillance Procedures, 323-1123-510).

If a Rs_exc alarm is present at the far multiplexer, remove the ‘Local’ loopback and go to step 6.

If a Rs_exc alarm is not present at the far multiplexer, remove the ‘Local’ loopback and go to step 7.

6

Replace the far end card. Refer to the Maintenance Procedures,

323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

7

On optical cards, clean the receive optical connections at the local aggregate or STM-1o tributary and verify that the received optical power is in the correct range. Refer to Maintenance Procedures, 323-1123-547.

If the received optical power is not within range, go to step 8.

8

On optical cards, clean the transmit optical connections at the far aggregate or STM-1o tributary and verify that the transmit optical power at the far aggregate or STM-1o tributary is in the correct range. Refer to Maintenance Procedures, 323-1123-547.

If the transmit optical power is not within range, go to step 6.

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—

2-26

Clearing alarms

RS RS-Trace Identifier Mismatch (TIM)

Significance This alarm indicates that the received STM path trace string in the J0 byte of the RS overhead does not match the expected string. The alarm is not raised until four successive occurrences of the string mismatch.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Major alarm

Consequent action The received STM signal is set to AIS before further processing (the consequent action is configurable - the default is off).

Resulting alarm MS_AIS if the consequent action is on.

Possible causes Possible causes for the Rs-tim alarm are:

• Incorrect connection setup.

• Path trace settings incorrect (i.e. receive string or far end transmit string).

• Cyclic redundancy check (CRC) settings incorrect.

• Faulty aggregate, STM-1o tributary or STM-1e tributary.

• If intermittent or transient events, errors in signal.

Clearing alarms

2-27

Corrective actions

Procedure 2-8 Rs-tim alarm clearing

Step

Action

2

1

Check that the correct connections have been made.

If the connections are incorrect, reconnect as required.

If the connections are correct, go to step 2.

2

Check the system path trace and CRC settings at both ends.

To view, and if necessary correct, the settings refer to the Provisioning and Operations Procedures, 323-1123-310.

If settings are correct, go to step 3.

3

At the local multiplexer, replace the appropriate aggregate or tributary card. Refer to the Maintenance Procedures, 323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, go to step 4.

4

At the far multiplexer, replace the appropriate aggregate or tributary card. Refer to the Maintenance Procedures, 323-1123-547.

If the alarm clears, the alarm clearing procedure is complete.

If the alarm is still present, escalate problem or replace subrack.

—end—

2-28

Clearing alarms

RS RS-Loopback On

Significance This alarm indicates that an internal local or remote loopback is present at the indicated port.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

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 Procedures, 323-1123-510.

Clearing alarms

2-29

RS RS-Quality of service violation (15 minute)

Significance The Rs_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAS active performance monitoring threshold has been broken within a 15 minute monitoring period.

2

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Minor Alarm

Consequent action None.

Possible causes Possible causes for the Rs_qosv_15M alarm are:

• Excessive attenuation in cable or optical fibre.

• Errored input signal

• Faulty traffic 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-9 Rs_qosv_15M alarm clearing

Step

Action

1

Check for the presence of the Rs_los or Rs_lof alarm. Identify and remove the cause of this alarm.

2

Check for the presence of B1 bit errors. Identify and remove the cause of these errors.

3

The Rs_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—

2-30

Clearing alarms

RS RS-Quality of service violation (24 hour)

Significance The Rs_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAS active performance monitoring threshold has been broken within a 24 hour monitoring period.

Instance/Unit This alarm is raised against a port instance, reported as

S <slot-no> - <port-no>

For details of valid arguments see Table 2-1 on page 2-10

Impact

Minor Alarm

Consequent action None.

Possible causes Possible causes for the Rs_qosv_24H alarm are:

• Excessive attenuation in cable.

• Errored input signal

• Faulty traffic 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-10 Rs_qosv_24H alarm clearing

Step