Alrm Clear 4xe31

323-1123-543

SDH TRANSMISSION

Nortel TN-4XEAlarm Clearing Procedures

Release 3.01 Standard March 2000

SDH TRANSMISSION

Nortel TN-4XEAlarm Clearing Procedures

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

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

Printed in England

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

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

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

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

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

Nortel TN-4XE Alarm Clearing Procedures

ii

VT100 is a trademark of Digital Equipment Corporation. Unix and the X device are trademarks of The Open GroupRS-232 is a trademark of the Electronic Industries AssociationCNet is a trademark of CNet Technology IncEthernet is a trademark of Xerox Corporation

323-1123-543 Release 3.01 Standard

iii

)

ot

m)

to

Publication historyMarch 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 functionredundancy

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

• Performance monitoring to G.826

• New connection types (unprotected PDH tributary to tributary, time slinterchange on aggregate to aggregate)

February 1999


• Engineering Order Wire card

• STM-4o optical aggregate long haul 1550 nm

• Rack fan tray

December 1998


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

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

• Installation in 19 inch (482 mm) equipment rack


iv

ts

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 por

• 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

ContentsAbout this document xiAssociated documents xi

Introduction 1-1Maintenance philosophy 1-1Alarm clearing 1-1Response to action logs 1-2Defect detection and alarm reporting 1-2

Card LEDs 1-2Rack alarm unit (RAU) indications on the subrack 1-2

Correlation (fault masking) 1-3Alarm severity and RAU category 1-4

Alarm severity states 1-6RAU categories 1-6

Consequent actions and alarms 1-7

Clearing alarms 2-1Alarm instances 2-10OS-Optical Power High 2-11OS-Laser Bias High 2-12OS-Disabled Laser Shutdown 2-13OS-Laser Shutdown 2-14ES-Coded mark inversion violation 2-15ES-Transmit Fail (TF) 2-16ES-Code violation quality of service violation

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

(24 hour) 2-18RS-Unexpected signal 2-19RS-Loss of Signal (LOS) 2-20RS-Loss of Frame (LOF) 2-22RS-Excessive errors (EXC) 2-24RS-Trace Identifier Mismatch (TIM) 2-26RS-Loopback On 2-28RS-Quality of service violation (15 minute) 2-29RS-Quality of service violation (24 hour) 2-30MS-Alarm Indication Signal (AIS) 2-31MS-Remote Defect Indicator (RDI) 2-33MS-Remote Error Indicator (REI) 2-35MS-Excessive errors (EXC) 2-37MS-Signal Degrade (DEG) 2-39MS-Quality of service violation (15 minute) 2-41


vi Contents

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

Release 3.01 Standard

Contents vii

PPI PPI- Transmit-Loss of Frame (T-LOF) 2-123PPI PPI-Code violation Quality of service violation

(15 minute) 2-124PPI PPI-Code violation-Quality of service violation

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

Index 3-1

Figures


viii Contents

Figure 1-1 RAU indicators on the Upper EOS card 1-3Figure 1-2 Card Alarm Correlation hierarchy 1-4Figure 1-3 Traffic and BER alarm correlation hierarchy 1-5Figure 1-4 Hierarchy of alarm correlation for PDH traffic

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

Release 3.01 Standard

Contents ix

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


xiii

on

About this documentThis document contains procedures to locate and clear alarm indicationsthe TN-4XE subrack.

AudienceThis document is intended for use by the following people:

• field maintenance personnel

• maintenance engineers

• system test engineers

• network administrators

Associated documentsThe 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

the

it’s n the

s

is

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

[email protected]

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

United KingdomFreephone: 0800 626 881Telephone: 0208 361 4693FAX: 0208 945 3456

InternationalTelephone: +44 208 361 4693FAX: +44 208 945 3456

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


in

nd

Code: EDEU0001Issue: 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 listedSection 2 and fulfil our obligations under the EU Directives listed in Section 3.

Section 1 - Products Covered

Section 2 - Standards Applied

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

Section 3 - European Union Directives

Section 4 - Authority of Issuer

Declaration Issued By: Peter Schuddeboom John Freebairn

Position of Issuer: VP, ION Product Development Senior Manager, CustomerSatisfaction & Quality

Signed: ________________

Date: ________________

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

This declaration has been made in accordance with ISO/IEC Guide 22, General criteria for suppliers' declaration of conformity

Product Name Product TypeTN-4XE STM4 Add Drop SDH Multiplexer system;

permissable configurations which use TN-4XE subrack assembly (NTEU70AA) and TN-4XE fan tray assembly (NTEU55AA) (optional)

StdsRef

Standard Number Edition Amendments Subject of Standard

1 EN 55022 1995 Emissions from IT Equipment1 EN 50082-1 1992 Generic Immunity2 EN 60950 1992 1,2,3 & 4 Safety of IT equipment2 EN 60825-1 1994 1 Safety of Laser Products

DirectiveNumber

Abbreviated Directive Title StdsRef

CE Marking 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

1-1

1

e

d by re on

on

t a n to

Introduction 1-Maintenance philosophy

This section describes the maintenance method for locating and clearingalarm indications.

The maintenance philosophy is to identify the source of a fault without thneed 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 providethe TN-4XE and the Element Controller (EC-1) or CAT. TN-4XE has failuindicator lamps on the hardware and also has alarm or action log reportsthe user interface.

Alarms and action logs descriptions are in the System Description, 323-1123-100.

Alarm clearingTo 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 which the highest severity alarm has occurred.

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

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

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


1-2 Introduction

or

r

s

e

an

ve

itch

you he

e

her

Response to action logsTN-4XE action logs are information messages that the Network Elementthe 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 otrouble conditions.

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

Defect detection and alarm reportingThe TN-4XE subrack provides local alarm indications to aid identifying thsource of a problem.

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

Traffic cards LEDsThe 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 remothe card while this LED is on.

• the LOS LED (yellow) indicates a loss of signal

EOS cards LEDsThe 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 subrackThe UEOS card includes two visual alarm indicators and a push button swrelated to the RAU. The ‘Alarm’ indicator is on when any of the RAU indicators Prompt, Deferred maintenance or In-Station are active. When operate the ‘Receive Attention’ switch the ‘Alarm’ indicator goes off and t‘Alarm acknowledge’ indicator comes on.

CAUTIONRisk of traffic interruptionThe TN-4XE Network Element is a high capacity system. Bcareful not to interrupt traffic or perform any task without a valid reason. Where possible reroute the traffic through anotpath before replacing any traffic-carrying circuit pack.


Introduction 1-3

1

, can tity e

rchy at e

fore y

alarm ions

Figure 1-1RAU indicators on the Upper EOS card

Correlation (fault masking)When the TN-4XE alarm handling hardware and software detects a faultoften the multiplexer reports more than one alarm. Many of these alarmsbe related but vary in severity levels. Alarm correlation reduces the quanof alarms shown to the operator because the multiplexer only displays thalarm nearest to the fault source.

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

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

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

FAIL

ACK ALARM

ALARM

REC ATT

NP

UT

RAU indicators


1-4 Introduction

ally, t oad nes

ory. he larm.

or

Figure 1-2Card Alarm Correlation hierarchy

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

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

The operator can change the RAU category for each alarm. If the operatchanges the RAU category for an alarm the alarm severity also changesautomatically.

Card Fault Card Fail Wrong Card Unexpected Card

Any alarm raised on the Card/Slot instance

Equipment Alarms Card Alarms


Introduction 1-5

1
Figure 1-3Traffic and BER alarm correlation hierarchy
RS LOS

RS LOF

RS TIM MS RDI RS COMMS FAIL

MS AIS

MS EXC

MS REI

MS DEG AU LOP

AU AIS

HP TIM HP PLM HP UNEQ

HP-EXC

HP DEGHP RDI

HP REI TU LOP

TU AIS

LPOM EXC

= Consequent Action configuration dependent

= Masked if TU type is TU-1

HP LOM

INT TU LOP

INT TU AIS

LP EXC

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

LP-REI

ES CMI

INT HP OP BUFF

PPI LOF-T

LPOM UNEQLPOM PLMLPOM TIM

HPOM EXC

HPOM PLMHPOM TIM

RS UNEXP SGNL

HPOM UNEQ

MS COMMS FAIL

FOP_PAM FOP_SCM FOP_INV


1-6 Introduction

ices d

by s an

se

ing

:

uire to a

Figure 1-4Hierarchy of alarm correlation for PDH traffic

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

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

• Major alarm- a failure which decreases the quality of services providedthe network, but not to the same degree as a Critical failure. RS-TIM iexample of a major alarm.

• Minor alarm- a failure in the network or a failure which does not decreathe quality of service provided by the network. AIS and protected cardfailures 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 warnalarm indicates a condition exists that requires action.

RAU categoriesEach 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 reqimmediate action outside normal hours. Generally, this alarm passesmaintenance/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.

PPI EXC

INT LP IP BUFFPPI DEG

PPI LOS

PPI AIS INT HP IP BUFF

PPI UNEXP SGNL

PPI LOF

PPI LOM


Introduction 1-7

1 in

d

NE wing

Consequent actions and alarmsConsequent actions are events which occur as a result of a traffic or BERalarm to indicate the condition of the received signal. There are three maconsequent actions:

• AIS indication (internal to the multiplexer)

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

• an SNC-P or path protection switch

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

• the feature is enabled (for example Path Trace)

• alarm reports are set to On or Monitor

• the consequent actions are enabled for the NE

• the consequent action is enabled for the alarm type

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

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

end of chapter


2-12

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

Electrical section 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


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

Multiplexer section alarms

Administrative Unit alarms


RS-Unexpected signal Rs_unexp_signal 2-19

RS-Loss of Signal (LOS) Rs_los 2-20

RS-Loss of Frame (LOF) Rs_lof 2-22

RS-Excessive errors (EXC) Rs_exc 2-24

RS-Trace Identifier Mismatch (TIM) Rs_tim 2-26

RS-Loopback On Rs_loopback_on 2-28

RS-quality of service violation 15 minute RS_qosv_15M 2-29

RS-quality of service violation 24 hour RS_qosv_24H 2-30


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


AU-Alarm Indication Signal (AIS) Au_ais 2-45

AU-Loss of Pointer (LOP) Au_lop 2-47


Clearing alarms 2-3

2

Higher order path alarms

Higher order path alarms with overhead monitoring


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


HPOM-Excessive errors (EXC) Hpom_exc 2-71

HPOM-Trail Identifier Mismatch (TIM) Hpom_tim 2-73

HPOM-Payload Label Mismatch (PLM) Hpom_plm 2-75

HPOM-Unequipped (UNEQ) Hpom_uneq 2-77


2-4 Clearing alarms

Transport unit alarms

Low order path alarms

Low order path alarms with overhead monitoring


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


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


LPOM-Excessive Errors (EXC) Lpom_exc 2-104


Clearing alarms 2-5

2

PDH physical interface alarms

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


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-6 Clearing alarms

Synchronization alarms


Sync-SETG Fail Sync_setg_fail 2-126

Sync-Unexpected signal Sync_unexp_signal 2-127

Sync-ESO Source Not Primary Sync_eso_src_not_primary 2-128

Sync-Holdover Sync_holdover 2-129

Sync-Source Not Primary Sync_src_not_primary 2-130

Sync-External Sync Loss Of Signal Sync_ext_sync_los 2-131

Sync-SETG Frequency suspect Sync_frequency_suspect 2-133

Sync-Source out of limits Sync_source_out _of_limits 2-134

Sync-Lock fail Sync_lock_fail 2-135


Clearing alarms 2-7

2

Miscellaneous alarms

Card alarms


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 NE-Card Out Ne_card_out 2-149

Card NE-Unexpected Card Ne_unexpected_card 2-151

Card NE-Card Fail Ne_card_fail 2-153

Card NE-Card Fault Ne_card_fault 2-154

Card NE-Wrong Card Ne_wrong_card 2-155

Card NE-Invt Write Jumper Fitted Ne_invt_wri_jumper_fitted 2-156

Card NE-Minor card mismatch Ne_minor_card_mismatch 2-157


2-8 Clearing alarms

Configuration alarms


Config INT NE-Configuration Corrupt 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_Mismatch

2-168

Config INT NE-Standby Configuration fail

Int_ne_stdby_cfg_fail 2-169


Clearing alarms 2-9

2

1+1 Card Protection alarms

Multiplex section protection alarms


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


Protection scheme mismatch FOP_PAM 2-175

Channel mismatch FOP_SCM 2-176

Invalid K bytes (Invalid command) FOP_INV 2-177

Invalid K bytes (timeout) FOP_TMOUT 2-178


2-10 Clearing alarms

d
Alarm instances
The following table details the alarm instances that are valid for each cartype in a TN-4XE.

Table 2-1Possible 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, 12

1 - -

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, 12

1 - -

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

2er

e the

s still

OSOS-Optical Power High

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

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

Instance/UnitThe multiplexer raises this alarm on an optical port instance, reported asS <slot-no> - <port-no>

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

ImpactCritical alarm

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

Consequent actionThe laser is shutdown. This is a safety feature, although the laser output iwithin the standard safe range.

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

Resulting alarmsNone

Possible causesFaulty aggregate card or STM-1o tributary card.

Corrective actionsRe-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.



laser

he

OSOS-Laser Bias High

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

Instance/UnitThis alarm is raised against an optical port instance, reported as S <slot-no> - <port-no>



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

Consequent actionNone.

Possible causesAgeing of the laser on the indicated optical port.

Corrective actionsReplace the indicated aggregate card or STM-1 tributary card. Refer to tMaintenance Procedures, 323-1123-547.



2

ving

OSOS-Disabled Laser Shutdown

SignificanceThe automatic laser shutdown (ALS) function is disabled on the indicatedoptical port.

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

Instance/UnitThis alarm is raised against an optical port instance, reported asS <slot-no> - <port-no>


ImpactMinor alarm.

Does not affect traffic.

Consequent actionAutomatic laser shutdown will not operate on the indicated port.

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

Corrective actionsThis alarm is only cleared when ALS is enabled. ALS is enabled by remoa 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.



wn

or

OSOS-Laser Shutdown

SignificanceThis alarm is raised when the laser on the specified optical port is shutdoby the automatic laser shutdown (ALS) circuit.

Instance/UnitThis alarm is raised against an optical port instance, reported asS <slot-no> - <port-no>



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


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

• RS_LOS alarm.

• Faulty aggregate or STM-1o tributary.

Corrective actionsIf the RS_LOS alarm is present, perform the alarm clearing procedures fthat 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.



2

ESES-Coded mark inversion violation

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

Instance/UnitThis alarm is raised against a port instance, reported asS <slot-no> - <port-no>




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

Possible causesPossible 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-1Es-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—



ld.

ESES-Transmit Fail (TF)

SignificanceThe STM-1e tributary output signal has fallen below a predefined thresho



ImpactCritical Alarm

Loss of STM-1e traffic output


Possible causesPossible causes for the ES-TF alarm are:

• Cable fault.


Corrective actions

Procedure 2-2ES_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 is still present, escalate problem or replace subrack.

—end—



2, 5

ng

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

SignificanceThe Es_cv_qosv_15M alarm is raised to indicate that any BBE, ES, SESUAS active performance monitoring threshold has been broken within a 1minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the The Es_cv_qosv_15M alarm are:




Corrective actionsThis alarm automatically clears upon completion of a 15 minute monitoriperiod in which no QOSV thresholds have been exceeded. The followingprocedure describes how to detect the cause of the alarm.

Procedure 2-3Es_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—



, 24

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

SignificanceThe Es_cv_qosv_24H alarm is raised to indicate that any BBE, ES, SESUAS active performance monitoring threshold has been broken within a hour monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Es_cv_qosv_24H alarm are:




Corrective actionsThis alarm automatically clears upon completion of a 24 hour monitoringperiod. The following procedure describes how to detect the cause of thealarm.

Procedure 2-4ES-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—



2 has

RSRS-Unexpected signal

SignificanceIndicates that an optical signal is present at a specified port, but the portnot been configured to receive the connection.



ImpactMajor alarm.



Possible causesIncorrect configuration of connections.

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



h ll be

RSRS-Loss of Signal (LOS)

SignificanceThe indicated card detects the loss of the received signal.





Consequent actionAIS 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 switcoccurs. If entered in the synchronization source hierarchy list, this port wimarked unavailable for synchronization.

Resulting alarmOS_laser_shutdown, Ms_ais alarms.

Possible causesPossible 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.



2

Corrective actions

Procedure 2-5Rs-los alarm clearing

Step Action

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

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

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

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



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

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

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

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

5 Replace the far end STM-N card. Refer to the Maintenance Procedures, 323-1123-547.



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

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

7 On optical cards, clean the transmit optical connections at the far aggregate or STM-1o tributary and verify that the transmit optical power at the far aggregate or STM-1o tributary is in the correct range. Refer to Maintenance 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—



RSRS-Loss of Frame (LOF)

SignificanceThe 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).





Consequent actionAIS 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 alarmsMs_ais alarm.

Possible causesPossible causes for the Rs_lof alarm are:

• Faulty optical fibre or cable.





2

Corrective actions

Procedure 2-6Rs_lof alarm clearing

Step Action

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

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



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



3 Perform a ‘Local’ loopback on the appropriate far end card (see Network 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.


5 Replace the far end card. Refer to the Maintenance Procedures, 323-1123-547.







—end—



RSRS-Excessive errors (EXC)

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





Consequent actionAIS 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 causesPossible 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.



2

Corrective actions

Procedure 2-7Rs-exc alarm clearing

Step Action

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

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



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





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.








—end—



te of ised

g).

RSRS-Trace Identifier Mismatch (TIM)

SignificanceThis alarm indicates that the received STM path trace string in the J0 bythe RS overhead does not match the expected string. The alarm is not rauntil four successive occurrences of the string mismatch.



ImpactMajor alarm

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

Resulting alarmMS_AIS if the consequent action is on.

Possible causesPossible causes for the Rs-tim alarm are:

• Incorrect connection setup.

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

• Cyclic redundancy check (CRC) settings incorrect.

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

• If intermittent or transient events, errors in signal.



2

Corrective actions

Procedure 2-8Rs-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-1123-310.

If settings are correct, go to step 3.

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


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

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



—end—



t the

t.

RSRS-Loopback On

SignificanceThis alarm indicates that an internal local or remote loopback is present aindicated port.



ImpactMinor alarm.


Possible causesThe operator has applied a local or remote loopback at the indicated por

Corrective actionsIf required, remove the loopback as detailed in Network Surveillance Procedures, 323-1123-510.



2AS nute

ng

RSRS-Quality of service violation (15 minute)

SignificanceThe Rs_qosv_15M alarm is raised to indicate that any BBE, ES, SES, Uactive performance monitoring threshold has been broken within a 15 mimonitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Rs_qosv_15M alarm are:

• Excessive attenuation in cable or optical fibre.


• Faulty traffic card.


Procedure 2-9Rs_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—



S ur

RSRS-Quality of service violation (24 hour)

SignificanceThe Rs_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAactive performance monitoring threshold has been broken within a 24 homonitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Rs_qosv_24H alarm are:





Procedure 2-10Rs_qosv_24H alarm clearing

Step Action

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


3 The Rs_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—



2 re

if it

in

MSMS-Alarm Indication Signal (AIS)

SignificanceAn AIS is detected in the K2 byte in the multiplex section overhead whichindicates a failure at the far multiplexer. The alarm is raised when there athree successive occurrences of AIS.



ImpactMinor alarm.

Traffic is affected on unprotected paths.

Temporary traffic hit on protected paths during switch.

Consequent actionAIS is inserted on the MS overhead K2 byte of the on-going path. RDI isinserted in the overhead of the return path.

Resulting alarmMS-RDI alarm is raised at the remote (source) multiplexer.

This alarm causes the port to be marked unavailable for synchronizationis entered in the synchronization source priority list.

Possible causesMS-AIS alarm is generated at the source multiplexer or by a regeneratorbetween.



Corrective actions

Procedure 2-11MS-AIS alarm clearing

Step Action

1 Check the far multiplexer and any intermediate regenerators for the cause of the AIS.

If the cause of the AIS is found, perform the appropriate alarm clearing procedure.

If the cause of the alarm is not found, go to step 3.

2 If the ‘Local’ port provides the current synchronization source, switch to an alternative source.


If the alarm is still present, remove the ‘Local’ loopback and go to step 3.

If the alarm clears, remove the ‘Local’ loopback and go to step 5.

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



5 Replace the far end card. Refer to Maintenance Procedures, 323-1123-547.



—end—



2 MS

s

es of

MSMS-Remote Defect Indicator (RDI)

SignificanceAn MS Remote Defect Indicator has been detected in the K2 bytes of theoverhead. This indicates that the far multiplexer has detected a fault in itincoming signal. The alarm is raised when there are five successive occurrences of RDI and cleared when there are three successive absencRDI.



ImpactMajor alarm.


Possible causesPossible causes for the MS-RDI alarm are:

• MS-AIS alarm at the far multiplexer.





Corrective actions

Procedure 2-12MS-RDI alarm clearing

Step Action

1 Check the far multiplexer for the cause of the MS-AIS alarm.

If the cause of the alarm is found, perform the appropriate alarm clearing procedure.

If the cause of the alarm is not found, go to step 2.

2 Check local multiplexer for local receive errors.

If local receive errors are found, investigate cause of errors.








—end—



2

MSMS-Remote Error Indicator (REI)

SignificanceAn MS Remote Error Indication (the M1 byte of the section overhead) indicates that the bit errors received at the far end multiplexer exceed theconfigured threshold.

Note: REI alarm reports can be disabled.



ImpactMajor alarm.


Possible causesPossible causes for the MS-REI alarm are:

• Ms-exc alarm at the far multiplexer.





Corrective actions

Procedure 2-13MS-REI alarm clearing

Step Action

1 Check the far multiplexer for the cause of the MS-EXC alarm.

If the cause of the alarm is found, perform the appropriate alarm clearing procedure.



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





—end—



2rror

).

MSMS-Excessive errors (EXC)

SignificanceAn MS Excessive Bit Error alarm is raised when the BER of the BIP-24 echeck on a received signal exceeds the configured threshold.





If this port is entered in the synchronization source priority list this alarm causes it to be marked unavailable for synchronization.

Consequent actionAIS is injected on the AU-4 payload of the transmitted path(the consequent action is configurable - the default is off).

Transmission of MS-RDI in the return path (if the consequent action is on

Possible causesPossible causes for the MS-EXC alarm are:

• Faulty optical fibre, cable or connections.





Corrective actions

Procedure 2-14MS-EXC alarm clearing

Step Action









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

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




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 (see Chapter 4).

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

If the received optical power is not within range, clean the receive optical connections at the local aggregate or STM-1o tributary.



If the transmit optical power is within range, the fault is associated with the optical fibre. Use appropriate methods to isolate and repair fibre fault.

—end—



2or

MSMS-Signal Degrade (DEG)

SignificanceThe MS Signal Degrade alarm is raised when the BER of the BIP-24 errcheck exceeds the configured threshold.



ImpactMajor alarm.



Resulting alarmPossible intermittent HP-REI alarms raised at an HP source.

Possible causesPossible causes for the MS-DEG alarm are:

• Faulty optical fibre, cable or connections.





Corrective actions

Procedure 2-15MS_DEG alarm clearing

Step Action









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

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

5 Replace the far end card. Refer to Maintenance Procedures,323-1123-547.



6 On optical cards, clean the receive optical connections at the local aggregate or STM-1o tributary and verify that the received optical power is in the correct range (see Chapter 4).

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

If the received optical power is not within range, clean the receive optical connections at the local aggregate or STM-1o tributary.



If the transmit optical power is within range, the fault is associated with the optical fibre. Use appropriate methods to isolate and repair fibre fault.

—end—



2AS nute

ng

MSMS-Quality of service violation (15 minute)

SignificanceThe Ms_qosv_15M alarm is raised to indicate that any BBE, ES, SES, Uactive performance monitoring threshold has been broken within a 15 mimonitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Ms_qosv_15M alarm are:





Procedure 2-16Ms_qosv_15M alarm clearing

Step Action

1 Check for the presence of the Rs_los, Rs_lof alarm, Ma-ais or Ms-exc. Identify and remove the cause of this alarm.


3 The Ms_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—



AS ur

MSMS-Quality of service violation (24 hour)

SignificanceThe Ms_qosv_24H alarm is raised to indicate that any BBE, ES, SES, Uactive performance monitoring threshold has been broken within a 24 homonitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Ms_qosv_24H alarm are:





Procedure 2-17Ms_qosv_24H alarm clearing

Step Action



3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—



2, 5

ng

MSMS-Far end quality of service violation (15 minute)

SignificanceThe Ms_fe_qosv_15M alarm is raised to indicate that any BBE, ES, SESUAS active performance monitoring threshold has been broken within a 1minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Ms_fe_qosv_15M alarm are:





Procedure 2-18Ms_fe_qosv_15M alarm clearing

Step Action



3 The Ms_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—



, a 24

MSMS-Far end quality of service violation (24 hour)

SignificanceThe Ms_fe_qosv_24H alarm is raised to indicate that any BBE, ES, SESUAS active performanance monitoring threshold has been broken within hour monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Ms_fe_qosv_24H alarm are:





Procedure 2-19Ms_fe_qosv_24H alarm clearing

Step Action

1 Check for the presence of the Rs_los,Rs_lof alarm, Ma-ais or Ms-exc. Identify and remove the cause of this alarm.


3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—



2he nt

AUAU-Alarm Indication Signal (AIS)

SignificanceAn AIS has been detected in the H1 and H2 bytes indicating a failure in tupstream path. This alarm is raised when AIS occurs on three consequeframes.

Instance/UnitThis alarm is raised against a high order path instance, reported asS <slot-no> - <port-no> - J<AU-4>


ImpactMinor alarm.


Consequent actionAIS is injected on the AU-4 payload of the transmitted path.

A protection switch occurs at PPS protected VC-4 connections.

Resulting alarmsTransmission of HP-RDI in the return path.

Possible causesPossible causes for the AU-AIS alarm are:





Corrective actions

Procedure 2-20AU-AIS alarm clearing

Step Action

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

2 Check the remote multiplexer and any intermediate regenerators for the cause of AIS.

If the cause of AIS found, perform the appropriate alarm clearing procedure.

If the cause of AIS not found, go to step 3.

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

Note: This loops back the STM-N data.

If the alarm is still present remove the ‘Local’ loopback and go to step 4.

If the alarm clears, the fault is at the far multiplexer. Remove the ‘Local’ loopback and go to step 5.

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






—end—



2ree

AUAU-Loss of Pointer (LOP)

SignificanceThe pointer value in the H1 and H2 bytes in the AU pointer is invalid for thconsecutive frames.



ImpactMinor alarm.


Consequent actionAIS injection on the AU-4 payload of the transmitted path.

A protection switch occurs at PPS protected VC-4 connections.

Resulting alarmsTransmission of HP-RDI in the return path.

Possible causesFaulty aggregate, STM-1o tributary or STM-1e tributary.

Corrective actions

Procedure 2-21AU-LOP alarm clearing

Step Action

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




—end—



d he

EXC

HP HP-Excessive errors (EXC)

SignificanceWhen a VC-4 signal is created, a BIP-8 parity checksum is generated antransmitted with the signal in the B3 byte. The B3 byte is examined and tBit error rate (BER) calculated when the VC-4 signal is received and terminated.

When the BER value exceeds the operator configured threshold, the HP-alarm is raised.



ImpactCritical alarm.

Traffic is affected.

Consequent actionA protection switch occurs at protected VC-4 connections.

AIS is injected on the payload of the VC-4 transmitted path.

Note:The consequent actions are configurable (default off).

Resulting alarmsHP-RDI is transmitted in the return path (if the consequent action is on).

Possible causesPossible causes for the HP-EXC alarm are:

• Possible line errors.





2

Corrective actions

Procedure 2-22HP-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-1123-510).

If the alarm is still present, the fault is at the local multiplexer. Remove the ‘Local’ loopback and perform step 4 at the local multiplexer.

If the alarm clears, the fault is at the far multiplexer. Remove the ‘Local’ loopback and perform step 5 at the far multiplexer.







—end—



the is

HPHP-Signal Degrade (DEG)

SignificanceSignal degrade is an intermediate alarm which informs the operator that signal quality is declining. The B3 byte is examined and the Bit error rate(BER) calculated when the VC-4 signal is received and terminated. WhenBER value exceeds the operator configured threshold, the HP-DEG alarmraised.

If signal quality continues to decline the HP-EXC alarm threshold will be crossed.



ImpactMajor alarm.


Resulting alarmHP-REI alarm.


Possible causesPossible causes for the HP-DEG alarm are:






2

Corrective actions

Procedure 2-23HP-DEG alarm clearing

Step Action









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



—end—



er at

trace ed.

g).

HPHP-Trace Identifier Mismatch (TIM)

SignificanceThe VC-4 path trace feature allows the operator to specify a trace identifithe transmitting multiplexer and an expected identifier at the terminating multiplexer. In the event of four successive occurrences of the expected identifier not matching the transmitted identifier, the HP-TIM alarm is rais

Note:You can disable reporting of this alarm.



ImpactMajor alarm.

Traffic is affected if incorrect connection (wrong traffic).


Resulting alarmTransmission of HP-RDI in the return path.

Note:The consequent action is configurable; the default is off.

Possible causesPossible causes for the HP-TIM alarm are:






2

Corrective actions

Procedure 2-24HP-TIM alarm clearing

Step Action




2 Check the connections have been provisioned correctly. Refer to Provisioning and Operations Procedures, 323-1123-310 for the procedure to view and change connections.

If the connections are incorrect, reconfigure as necessary.


3 Check the system path trace settings at both ends (refer to Provisioning and Operations Procedures, 323-1123-310).

If settings are incorrect, reconfigure as necessary.


4 At the local multiplexer, replace the indicated card. Refer to Maintenance Procedures, 323-1123-547.



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

If the alarm clears, alarm clearing procedure is complete.


—end—



yte lt in

HPHP-Remote Defect Indicator (RDI)

SignificanceThe VC-4 path remote defect indication (RDI) bit in the VC-4 path status b(G1) is set. This indicates that the far end multiplexer has detected a fauthe incoming VC-4.

This alarm is raised when three successive RDI indications occur.



ImpactMajor alarm.


Possible causesPossible causes for the HP-RDI alarm are:

• AU_AIS, AU_LOP, HP_LOM, or HP_EXC alarm at far multiplexer.




2

Corrective actions

Procedure 2-25HP-RDI alarm clearing

Step Action

1 Check far multiplexer for cause of alarm (AU_AIS,AU_LOP, HP_LOM, or HP_EXC alarm).

If the cause of the alarm found, perform the appropriate alarm clearing procedure.

If the cause of the alarm not found, go to step 2.



If the alarm is permanent, go to step 3.




—end—



e H4

HPHP-Loss of Multiframe (LOM)

SignificanceWhen the VC-4 contains TU-12 payloads, the H4 byte indicates valid multiframes. Loss of multiframe alignment is indicated if three consecutivbad H4 bytes are received. Alignment is regained if two consecutive goodbytes are received.



ImpactMajor alarm.


Consequent actionAIS injection on the payload of the VC-4 transmitted path.

Possible causesPossible causes for the HP_LOM alarm are:

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

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



2

Corrective actions

Procedure 2-26HP-LOM alarm clearing

Step Action


If the alarm is still present, the fault is at the local multiplexer. Remove the ‘Local’ loopback. Goto step 2.

If the alarm clears, the fault is at the far multiplexer. Remove the ‘Local’ loopback. Goto step 3.







—end—



d

HPHP-Remote Error Indicator (REI)

SignificanceThe BER of the remote error indication (REI) bits in the VC-4 path statusbyte (G1) exceeds the configured threshold. This indicates that the far enmultiplexer has detected errors in the VC-4 path.



ImpactMajor alarm.


Possible causesPossible causes for the HP-REI alarm are:

• HP errors on network.

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

Corrective actions

Procedure 2-27HP-REI alarm clearing

Step Action

1 Check remote multiplexer for cause of errors.

If the cause of the errors found, perform the appropriate alarm clearing procedure.

If the cause of the errors not found, go to step 2.



If the alarm is permanent, go to step 3.




—end—



2nd

).

d

HPHP-Payload Label Mismatch (PLM)

SignificanceThe value of the VC-4 signal label code in the C2 byte does not correspowith the expected value. This alarm is raised when five successive stringmismatches occur.

Note: This alarm report can be disabled.



ImpactMajor alarm.

Traffic is affected if the connection is incorrectly setup (wrong traffic).


Note that:

1 The consequent action is configurable. The default is off.

2 The consequent action for the HP-UNEQ and HP-PLM alarms are configured together for any instance of VC-4.

Resulting alarmsTransmission of HP-RDI in the return path (if the consequent action is on

Possible causesPossible causes for the HP-PLM alarm are:


• Settings incorrectly set during configuration (i.e. receive string or far entransmit string).

• If intermittent or transient events, errors in the signal.



Corrective actions

Procedure 2-28HP-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.




3 Check the HP signal label settings for each node. Refer to Provisioning and Operations Procedures, 323-1123-310 for the procedure to view and change the settings.

If the settings are incorrect, reconfigure as necessary.

If the settings are correct, go to step 4.

4 At the far multiplexer, replace the indicated card. Refer to Maintenance Procedures, 323-1123-547.



—end—



2

HPHP-Unequipped (UNEQ)

SignificanceThe value of the VC-4 path signal label code in the C2 byte indicates unequipped (no connection is made). This alarm is raised when five successive string mismatches occur.




ImpactMajor alarm.


Consequent actionAIS injection on the VC-4 payload of the transmitted path.

Resulting alarmsTransmission of HP-RDI in the return path overhead.

Please note:

1 The consequent action is configurable; the default is off.

2 The consequent action for the HP-UNEQ and HP-PLM alarms are configured together for any instance of VC-4.

Possible causesPossible causes for the HP-UNEQ alarm are:


• Signal label incorrect (i.e. receive string or far end transmit string).



Corrective actions

Procedure 2-29HP-UNEQ alarm clearing

Step Action




2 Check the signal label settings at both ends. Refer to Provisioning and Operations Procedures, 323-1123-310.



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






—end—



2

HPHP-Signal Fail (SF)

SignificanceThe HP Signal Fail alarm is raised if both paths of a VC-4 protected connection fail.






Possible causesPossible causes for the HP-SF alarm are:

• Incorrect connections.

• Faulty far end card.



Corrective actions

Procedure 2-30HP-SF alarm clearing

Step Action




2 Check the provisioned connections at both ends. Refer to Provisioning and Operations Procedures, 323-1123-310.









—end—



2

HPINT-HP-Input Buffer Overflow

SignificanceThe INT-HP-IP-BUFFER is raised if the input buffer for the high order (VC-4) PDH mapper overflows.

Instance/UnitThis alarm is raised against a high order slot instance, reported asS <slot-no> - <port-no> - J<AU-4>.


ImpactMajor alarm


Temporary traffic hit on protected paths.

Consequent actionThe VC-4 payload of the ongoing path is filled with ‘all ones’.

Possible causesPossible causes for the INT-HP-IP-BUFFER alarm are:

• Incoming 140 Mbit/s signal bit-rate out-of-limits.

• Faulty 140 Mbit/s tributary card.

Corrective actions

Procedure 2-31INT-HP-IP-BUFFER alarm clearing

Step Action

1 Check if the tributary input signal is within limits.

If the tributary input signal is not within limits, investigate preceding 140 Mbit/s equipment.

If the tributary signal is within limits, go to step 2.

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



—end—



HPINT HP-Output Buffer Overflow

SignificanceThe INT-HP-OP-BUFFER is raised if the output buffer for the 140M bit/s desynchronizer overflows.

Instance/UnitThis alarm is raised against a high order port instance, reported asS <slot-no> - <port-no> - J<AU-4>.


ImpactMajor alarm




Possible causesPossible causes for the INT-HP-OP-BUFFER alarm are:

• Transient changes in the payload bit rate.


Corrective actions

Procedure 2-32INT-HP-OP-BUFFER alarm clearing

Step Action

1 Check if the tributary received signal is stable and within limits.



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



—end—



2AS

ng

HPHP-Quality of service violation (15 minute)

SignificanceThe Hp_qosv_15M alarm is raised to indicate that any BBE, ES, SES, Uactive performanance monitoring threshold has been broken within a 15 minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Hp_qosv_15M alarm are:





Procedure 2-33Hp_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.


3 The Hp_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—



S hour

HPHP-Quality of service violation (24 hour)

SignificanceThe Hp_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAactive performanance monitoring threshold has been broken within a 24 monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Hp_qosv_24H alarm are:





Procedure 2-34Hp_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 and remove the cause of these alarms.


3 The Hp_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—



2, a 15

ng

HPHP-Far end quality of service violation (15 minute)

SignificanceThe Hp_fe_qosv_15M alarm is raised to indicate that any BBE, ES, SESUAS active performanance monitoring threshold has been broken within minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Hp_fe_qosv_15M alarm are:

• HP-RDI alarm from the far multiplexer.




Procedure 2-35Hp_fe_qosv_15M alarm clearing

Step Action

1 Check for the presence of the HP-RDI alarm. Identify and remove the cause of this alarm.

2 Check for the presence of errored blocks from HP-REI. Identify and remove the cause of these errors.

3 The Hp_fe_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—



, a 24

HPHP-Far end quality of service violation (24 hour)

SignificanceThe HP_fe_qosv_24H alarm is raised to indicate that any BBE, ES, SESUAS active performanance monitoring threshold has been broken within hour monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the HP_fe_qosv_24H alarm are:

• HP-RDI alarm from the far multiplexer.




Procedure 2-36Hp_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—



2d he e

m a

HPOMHPOM-Excessive errors (EXC)

SignificanceWhen a VC-4 signal is created, a BIP-8 parity checksum is generated antransmitted with the signal in the B3 byte. The B3 byte is examined and tBit error rate (BER) calculated from the VC-4 signal. When the BER valuexceeds the operator configured threshold, the HP-EXC alarm is raised.

The HPOM-EXC alarm is similar to the HP-EXC alarm. The HPOM-EXCalarm is non-intrusively monitored whereas the HP-EXC is monitored froterminated connection.





Consequent actionA protection switch occurs at protected VC-4 connections.

AIS is injected on the payload of the VC-4 transmitted path.

Note: The consequent actions are configurable (default off).

Resulting alarmsHP-RDI is transmitted in the return path (if the consequent action is on).

Possible causesPossible causes for the HPOM-EXC alarm are:






Corrective actions

Procedure 2-37HPOM-EXC alarm clearing

Step Action



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



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






—end—



2er at

trace ed.

a

g).

HPOMHPOM-Trace Identifier Mismatch (TIM)

SignificanceThe VC-4 path trace feature allows the operator to specify a trace identifithe transmitting multiplexer and an expected identifier at the terminating multiplexer. In the event of four successive occurrences of the expected identifier not matching the transmitted identifier, the HP-TIM alarm is rais

The HPOM-TIM alarm is similar to the HP-TIM alarm. The HPOM-TIM alarm is non-intrusively monitored whereas the HP-TIM is monitored fromterminated connection.

Note: You can disable reporting of this alarm.



ImpactMajor alarm.



Possible causesPossible causes for the HPOM-TIM alarm are:






Corrective actions

Procedure 2-38HPOM-TIM alarm clearing

Step Action







3 Check the system path trace settings at both ends (refer to Provisioning and Operations Procedures, 323-1123-310).



4 At the local multiplexer, replace the indicated card. Refer to Maintenance Procedures, 323-1123-547.






—end—



2nd

a

d

HPOMHPOM-Payload Label Mismatch (PLM)

SignificanceThe value of the VC-4 signal label code in the C2 byte does not correspowith the expected value. This alarm is raised when five successive stringmismatches occur.

The HPOM-PLM alarm is similar to the HP-PLM alarm. The HPOM-PLMalarm is non-intrusively monitored whereas the HP-PLM is monitored fromterminated connection.




ImpactMajor alarm.

Traffic is affected if the connection is incorrectly setup (wrong traffic).


Possible causesPossible causes for the HPOM-PLM alarm are:


• Settings incorrectly set during configuration (i.e. receive string or far entransmit string).

• If intermittent or transient events, errors in the signal.



Corrective actions

Procedure 2-39HPOM-PLM alarm clearing

Step Action

1 Check that the optical connections are correct.






3 Check the HP signal label settings for each node. Refer to Provisioning and Operations Procedures, 323-1123-310 for the procedure to view and change the settings.

If the settings are incorrect, reconfigure as necessary.


4 At the far multiplexer, replace the indicated card. Refer to Maintenance Procedures, 323-1123-547.



—end—



2

is

HPOMHPOM-Unequipped (UNEQ)

SignificanceThe value of the VC-4 path signal label code in the C2 byte indicates unequipped (no connection is made). This alarm is raised when five successive string mismatches occur.

The HPOM-UNEQ alarm is similar to the HP-UNEQ alarm. The HPOM-UNEQ alarm is non-intrusively monitored whereas the HP-UNEQmonitored from a terminated connection.




ImpactMajor alarm.



Possible causesPossible causes for the HPOM-UNEQ alarm are:


• Signal label incorrect (i.e. receive string or far end transmit string).



Corrective actions

Procedure 2-40HPOM-UNEQ alarm clearing

Step Action




2 Check the signal label settings at both ends. Refer to Provisioning and Operations Procedures, 323-1123-310.









—end—



2

TUTU-Alarm Indication Signal (AIS)

SignificanceAn AIS has been detected in the pointer bytes of the TU overhead.

Instance/UnitThis alarm is raised against a low order path instance, reported asS <slot-no> - <port-no> - J<VC-4> - K<klm>


ImpactMinor alarm



Consequent actionTU-AIS is injected on all through and add/drop TU connections.

TU-AIS is injected temporarily on protected TU connections.

A protection switch occurs on VC-3 or VC-12 PPS connections.

Possible causesTU-AIS being generated by another multiplexer on the network.

Corrective actions

Procedure 2-41TU-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—



ree

TUTU-Loss of Pointer (LOP)

SignificanceThe pointer value in the pointer bytes of the TU overhead is invalid for thconsecutive frames.

Instance/UnitThis alarm is raised against a low order path instance, reported asS <slot-no> - <port-no> - J<VC-4> - K<klm>


ImpactMajor alarm



Consequent actionTU-AIS is injected on all through and add/drop TU connections.

A protection switch occurs on VC-3 or VC-12 protected connections.

TU-AIS is injected temporarily on protected TU connections.

Possible causesFaulty aggregate or tributary card.

Corrective actions

Procedure 2-42TU-LOP alarm clearing

Step Action

1 Check that the correct network settings have been made. Refer to Provisioning and Operations Procedures, 323-1123-310.

If network connection settings are incorrect, correct as necessary.

If network connection settings are correct, go to step 2.




—end—



2ytes th n

TUINT-TU-Alarm Indication Signal (AIS)

SignificanceINT-TU-AIS is raised where the an AIS has been detected in the pointer bof the TU overhead. This alarm is monitored later in the demultiplexer pathan the observation of TU-AIS, therefore an occurrence of INT-TU-AIS ithe absence of TU-AIS indicates an internal problem in the NE.

Instance/UnitThis alarm is raised against a PDH port instance, reported asS <slot-no> - <port-no>


ImpactMajor alarm

Consequent actionAIS is injected downstream to the PDH port output.

Possible causesFaulty upstream traffic source.

Faulty tributary.

Corrective actions

Procedure 2-43INT-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).


2 If INT_TU_AIS is present and TU-AIS is not present, replace the aggregate or tributary Unit. Refer to Maintenance Procedures, 323-1123-547.


—end—



TU d an al

TUINT-TU-Loss of Pointer (LOP)

SignificanceINT-TU-LOP is raised where the pointer value in the pointer bytes of the overhead are invalid for three consecutive frames. This alarm is monitorelater in the demultiplexer path than the observation of TU-LOP, thereforeoccurrence of INT-TU-LOP in the absence of TU-LOP indicates an internproblem in the NE.

Instance/UnitThis alarm is raised against a PDH port instance, reported asS <slot-no> - <port-no>


ImpactMajor alarm

Consequent actionAIS is injected downstream to the PDH port output.

Possible causesFaulty upstream traffic source.

Faulty tributary.

Corrective actions

Procedure 2-44INT-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).


2 If INT_TU_LOP is present and TU-LOP is not present, replace the aggregate or tributary Unit. Refer to Maintenance Procedures, 323-1123-547.


—end—



2d

LPLP-Excessive errors (EXC)

SignificanceThe BER of the VC-12 path status byte (V5) has exceeded the configurethreshold. This alarm is observed at the termination of the Low order container.




Traffic is affected on the outgoing signal.


LP-RDI is injected in the return path.

Possible causesThe VC-12 payload of the ongoing path is filled with ‘all ones’.


Corrective actions

Procedure 2-45LP-EXC alarm clearing

Step Action

1 Check upstream for Lpom alarms. If Lpom alarms present, fault lies upstream. If no Lpom alarms are present, fault is local.

2 Check network for possible bit errors.

3 Replace the indicated 2 Mbit/s tributary card. Refer to Maintenance Procedures, 323-1123-547.

4 Restore to the old configuration.



—end—



e

LPLP-Signal Degrade (DEG)

SignificanceThe LP-DEG alarm is raised when the BER of the VC-12 path status byt(V5) has exceeded the configured threshold.

If signal quality continues to decline the LP-EXC alarm threshold will be crossed.

Instance/UnitThis alarm is raised against a port instance, reported asS <slot-no> - <port-no>-J<VC-4>-Kklm


ImpactMajor alarm.


Possible causesPossible causes for the LP-DEG alarm are:

• Errors on network (Traffic source containing errors).

• Faulty tributary.

• Faulty backplane interface.



2

Corrective actions

Procedure 2-46LP-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-1123-547.

3 Restore to the old configuration.


4 Replace upstream traffic cards.

If the alarm is still present, escalate problem.

—end—



ond

LPLP-Payload Label Mismatch (PLM)

SignificanceThe value of the VC-12 signal label code in the V5 byte does not correspwith the expected value. This alarm is raised at a path termination point,subsequent to a protection switch.

Note:The reporting of this alarm and its consequent actions can be enabled/disabled.



ImpactMajor alarm

Traffic is affected

Consequent actionIf configured to on, the:

• The VC-12 payload of the ongoing path is filled with ‘all ones’.

• LP-RDI is injected in the return path.

Possible causesPossible causes for the LP-PLM alarm are:

• Incorrect overhead configuration at near or far end.

• Incorrect path connection.




2

Corrective actions

Procedure 2-47LP-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’.

Refer to Provisioning and Operations Procedures, 323-1123-310 for the procedure to view and change connections.



2 Verify that the path is correctly connected at all intermediate multiplexers and that no LP errors are present on the network.

If the path is incorrectly connected and/or LP errors are present, re-connect as necessary and/or investigate network errors.

If the path is correctly connected and there are no LP errors in the network, go to step 3.

3 Replace the local 2 Mbit/s tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-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-1123-547 for replacement procedures.



—end—



n.

LPLP-Remote Defect Indicator (RDI)

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



ImpactMajor alarm.


Possible causesPossible causes for the LP-RDI alarm are:

• AIS has occurred at path far end.

• If alarm raised for all tributaries, RS-LOS, RS-LOF, MS-AIS, MS-EXC,AU-AIS, INT-AU-AIS, INT-AU-LOP, HP-TIM, HP-PLM or HP-LOM alarm at the far multiplexer.

• If alarm raised for one tributary only, TU-AIS, TU-LOP, INT-TU-AIS, INT-TU-LOP, LP-PLM or LP-EXC alarm present at far path terminatio



2

Corrective actions

Procedure 2-48LP-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 the LP errors are present, investigate network errors.

If there are no LP errors in the network, go to step 3.

3 Replace the local tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547 for replacement procedures.



4 Replace the far end tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547 for replacement procedures.



—end—



LPLP-Remote Error Indication (REI)

SignificanceThe REI bit (bit 3 in the V5 byte) is set. This indicates that the far end multiplexer has detected a fault in the incoming VC-12.



ImpactMajor alarm.


Possible causesTU errors observed at path far end.

Corrective actions

Procedure 2-49LP-REI alarm clearing

Step Action

1 Investigate far path termination for cause of errors and carry out fault finding procedures for appropriate alarm (e.g. LP-DEG alarm).

If cause of alarm found, perform the appropriate alarm clearing procedure.

If cause of alarm not found, go to step 2.




3 Replace the far end tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547 for replacement procedures.



—end—



2

LPINT-LP-Input Buffer Overflow

SignificanceThe INT-LP-IP-BUFFER is raised if the input buffer for the low order (VC-12, VC-3) PDH mapper overflows.



ImpactMajor alarm




Possible causesPossible causes for the INT-LP-IP-BUFFER alarm are:

• Incoming signal bit-rate out-of-limits.

• Faulty tributary card.



Corrective actions

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

Step Action

1 Check if the INT-LP-IP_Buffer alarm is present on more than one 2 Mbit/s tributary port.

If the INT-LP-IP_Buffer alarm is only present on one tributary port, go to step 2.

If the INT-LP-IP_Buffer alarm is present on more than one tributary port on a single 2 Mbit/s card, go to step 3

If the INT-LP-IP_Buffer alarm is present on all the tributary ports on more than one 2 Mbit/s cards, go to step 2.

2 Check if the tributary input signal is within limits.






—end—



22,

LPINT LP-Output Buffer Overflow

SignificanceThe INT-LP-OP-BUFF is raised if the output buffer for the low order (VC-1VC-3) desynchronizer overflows.



ImpactMajor alarm




Possible causesPossible causes for the INT-LP-OP-BUFF alarm are:

• Transient changes in the received payload bit rate.




Corrective actions

Procedure 2-51INT-LP-OP-BUFFER alarm clearing

Step Action

1 Check if the INT-LP-OP_BUFFER alarm is present on more than one 2 Mbit/s tributary port.

If the INT-LP-OP_BUFFER alarm is only present on one tributary port, go to step 2.

If the INT-LP-OP_BUFFER alarm is present on more than one tributary port on a single 2 Mbit/s card, go to step 3

If the INT-LP-OP_BUFFER alarm is present on all the tributary ports on more than one 2Mbit/s cards, go to step 2.

2 Check if the tributary received signal is stable and within limits.






—end—



2C-3

LPLP-Signal Fail (SF)

SignificanceThe LP Signal Fail alarm is raised if both paths in a protected VC-12 or Vconnection fail.





Possible causesUpstream fault in both traffic paths.

Corrective actions

Procedure 2-52LP-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 Operations Procedures, 323-1123-310.



3 Investigate the traffic path alarms which are causing the SF alarm.

—end—



ifier t the

is

LPLP-Trail Identifier Mismatch (TIM)

SignificanceThe VC-12 path trace feature allows the operator to specify a trace identin the J2 byte at the transmitting multiplexer and an expected identifier aterminating multiplexer. In the event of the expected trace identifier not matching the transmitted identifier, the LP-TIM alarm is raised. This alarmdetected at a path termination after a path protection operation.



ImpactMajor alarm

If consequent actions are configured to ON traffic is affected.

Consequent actionAIS is injected in VC-12 payload.

RDI sent downstream in V5 byte.

Possible causesPossible causes for the LP-TIM alarm are:

• Incorrect configuration of far end or near end path string.





2

Corrective actions

Procedure 2-53LP-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.



3 Replace the local tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547, for replacement procedures.



4 Replace the far end card. Refer to the Equipment Maintenance Procedures, 323-1123-547, for replacement procedures.



—end—



ped

LPLP-Label Unequipped

SignificanceThe LP-UNEQ value of the VC-12 payload signal label indicates unequip(no traffic in payload).



ImpactMajor alarm

If consequent actions are configured to on traffic is affected



Possible causesPossible causes for the LP-UNEQ alarm are:






2

Corrective actions

Procedure 2-54LP-UNEQ alarm clearing

Step Action












4 Replace the far end card. Refer to the Equipment Maintenance Procedures, 323-1123-547 for replacement procedures.



—end—



S

ng

LPLP-Quality of service violation (15 minute)

SignificanceThe Lp_qosv_15M alarm is raised to indicate that any BBE, ES, SES, UAactive performanance monitoring threshold has been broken within a 15 minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Lp_qosv_15M alarm are:





Procedure 2-55Lp_qosv_15M alarm clearing

Step Action

1 Check for the presence of the RS defects,MS defects, AU defects,HP defects, TU-AIS, TU-LOP, LP-TIM, LP-PLM, LP-EXC, INT-LO-BUFFER-OVERFLOW. Identify and remove the cause of these alarms.

2 Check for the presence of errored blocks. Identify and remove the cause of these errors.

3 The Lp_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—



2S

hour

LPLP-Quality of service violation (24 hour)

SignificanceThe Lp_qosv_24H alarm is raised to indicate that any BBE, ES, SES, UAactive performanance monitoring threshold has been broken within a 24 monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Lp_qosv_24H alarm are:





Procedure 2-56Lp_qosv_24H alarm clearing

Step Action

1 Check for the presence of the RS defects,MS defects, AU defects,HP defects, TU-AIS, TU-LOP, LP-TIM, LP-PLM, LP-EXC, INT-LO-BUFFER-OVERFLOW. Identify and remove the cause of these alarms.

2 Check for the presence of errored blocks. Identify and remove the cause of these errors.

3 The Lp_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—



, a 15

ng

LPLP-Far end quality of service violation (15 minute)

SignificanceThe Lp_fe_qosv_15M alarm is raised to indicate that any BBE, ES, SESUAS active performanance monitoring threshold has been broken within minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the Lp_fe_qosv_15M alarm are:

• LP-RDI alarm from the far multiplexer.

• Faulty local tributary.

• Faulty far end tributary.


Procedure 2-57Hp_fe_qosv_15M alarm clearing

Step Action

1 Check for the presence of the LP-RDI alarm. Identify and remove the cause of this alarm.

2 Check for the presence of errored blocks from LP-REI. Identify and remove the cause of these errors.

3 The Lp_fe_qosv_15M alarm clears after the next 15 minute monitoring period.

—end—



2, a 24

LPLP-Far end quality of service violation (24 hour)

SignificanceThe LP_fe_qosv_24H alarm is raised to indicate that any BBE, ES, SESUAS active performanance monitoring threshold has been broken within hour monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the LP_fe_qosv_24H alarm are:

• LP-RDI alarm from the far multiplexer.

• Faulty local tributary.

• Faulty far end tributary.


Procedure 2-58Lp_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 the cause of these errors.

3 The Lp_qosv_24H alarm clears after the current 24 hour monitoring period.

—end—



V5)

LPOMLPOM-Excessive Errors (EXC)

SignificanceThe LPOM-EXC is raised when the BER of the VC-12 path status byte (has exceeded the configured threshold.

The LPOM_EXC alarm is similar to the LP-EXC alarm. The LPOM-EXC alarm is non-intrusively monitored at the STM-N receive port of the container. The LP-EXC is monitored from a terminated connection at thetermination point.






Consequent actionA traffic protection switch occurs.

Possible causesPossible causes for the LPOM-EXC alarm are:

• Errors on network.




2

Corrective actions

Procedure 2-59LPOM-EXC alarm clearing

Step Action

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.

2 Replace the indicated card. Refer to Maintenance Procedures, 323-1123-547. Restore to the old configuration.



—end—



ifier t the

a

LPOMLPOM-Trail Identifier Mismatch (TIM)

SignificanceThe VC-12 path trace feature allows the operator to specify a trace identin the J2 byte at the transmitting multiplexer and an expected identifier aterminating multiplexer. In the event of the expected trace identifier not matching the transmitted identifier, the LPOM-TIM alarm is raised.

The LPOM-TIM alarm is similar to the LP-TIM alarm. The LPOM-TIM alarm is non-intrusively monitored whereas the LP-TIM is monitored fromterminated connection.

Instance/UnitThis alarm is raised against a port instance, reported asS <slot-no> - <port-no>--J<VC-4>-Kklm


ImpactMajor alarm


Possible causesPossible causes for the LPOM-TIM alarm are:

• Incorrect configuration of far end or near end path string.


• Faulty 2 Mbit/s tributary.



2

Corrective actions

Procedure 2-60LPOM-TIM alarm clearing

Step Action

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.






4 Replace the far 2 Mbit/s card. Refer to the Equipment Maintenance Procedures, 323-1123-547, for replacement procedures.



—end—



ond

a

LPOMLPOM-Payload Label Mismatch (PLM)

SignificanceThe value of the VC-12 signal label code in the V5 byte does not correspwith the expected value. This alarm is raised at a path termination point,subsequent to a protection switch.

The LPOM-PLM alarm is similar to the LP-PLM alarm. The LPOM-PLM alarm is non-intrusively monitored whereas the LP-PLM is monitored fromterminated connection.

Note:The reporting of this alarm can be enabled/disabled.



ImpactMajor alarm


Possible causesPossible causes for the LPOM-PLM alarm are:






2

Corrective actions

Procedure 2-61LPOM-PLM alarm clearing

Step Action




Refer to Provisioning and Operations Procedures, 323-1123-310 for the procedure to view and change connections.












—end—



ped

is

LPOMLPOM-Label Unequipped (UNEQ)

SignificanceThe LP-UNEQ value of the VC-12 payload signal label indicates unequip(no traffic in payload).

The LPOM-UNEQ alarm is similar to the LP-UNEQ alarm. The LPOM-UNEQ alarm is non-intrusively monitored whereas the LP-UNEQ monitored from a terminated connection.



ImpactMajor alarm

If consequent actions are configured to on traffic is affected


Possible causesPossible causes for the LPOM-UNEQ alarm are:






2

Corrective actions

Procedure 2-62LPOM-UNEQ alarm clearing

Step Action






2 Verify that the path is correctly connected at all intermediate multiplexers and that no LP or LPOM errors are present on the network.



3 Replace the local 2 Mbit/s tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547 for replacement procedures.






—end—



PPIPPI-Transmit Fail (TF)

SignificanceThe tributary output signal has fallen below a predefined threshold.



ImpactCritical Alarm

Loss of tributary traffic output


Possible causesPossible causes for the PPI-TF alarm are:

• Cable fault.




2

Corrective actions

Procedure 2-63PPI-TF alarm clearing

Step Action

1 Ensure that the traffic output cable is properly terminated. Re-terminate the connector if required.


2 Ensure that the traffic output cable is properly terminated. Re-terminate the connector if required.


3 Check the far end equipment for a short circuit.

If the alarm clears, the alarm clearing procedure is complete. If the alarm is still present, go to step 4.

4 Replace the indicated tributary card. Refer to the Equipment Maintenance Procedures, 323-1123-547, for replacement procedures.



—end—



PPIPPI-Loss Of Signal (LOS)

SignificanceThe PPI-LOS is raised where the loss of a PDH input signal is detected.




Consequent actionAll-ones(AIS) are transmitted in the traffic payload.

Possible causesPossible causes for the PPI-LOS alarm are:

• Preceding equipment failure.

• Input connector not properly connected.




2

Corrective actions

Procedure 2-64PPI-LOS alarm clearing

Step Action

1 Ensure that the associated input connector is properly connected.

If connector is not properly connected, re-insert connector.

If connector is properly connected, go to step 2.

2 Verify that a valid tributary signal is present at distribution frame.

If a valid signal is not present, check the tributary source equipment.

If a valid signal is present, go to step 4.

3 Verify that a valid tributary signal is present at the cable headshell.

Note: Removal of a 2 Mbit/s cable headshell causes a traffic loss on all 16 ports.

If a spare unused traffic port is available, the PDH signal can be verified by connecting the cable to the spare port. If a signal is present, a ‘PPI-Unexp_Signal’ alarm will be raised for the spare port.

If a valid signal is not present, a cable fault is suspected.


4 Replace the indicated tributary card, Refer to the Equipment Maintenance Procedures, 323-1123-547, for replacement procedures.



—end—



ition

PPIPPI-Alarm Indication Signal (AIS)

SignificanceThe PPI-AIS alarm is raised when the PDH interface detects an AIS condon the PDH input traffic.



ImpactMinor alarm.

Consequent actionAll-ones(AIS) are transmitted in the traffic payload.

Possible causesAIS being generated by preceding equipment.

Corrective actionsInvestigate preceding equipment for the cause of AIS.



2

PPIPPI-Excessive errors (EXC)

SignificanceThe PPI-EXC alarm is raised when HDB3 code violations exceed the threshold in a PDH signal.





Consequent actionAll-ones(AIS) are sent via the PDH input payload to the VC12 container.

Possible causesPossible causes for the PPI-EXC alarm are:


• Errored input signal.


Corrective actions

Procedure 2-65PPI-EXC alarm clearing

Step Action

1 Investigate preceding equipment and cable for cause of errors.






—end—



PPIPPI-Signal Degrade (DEG)

SignificanceThe PPI-DEG alarm is raised when HDB3 code violations exceed the threshold in a PDH signal.

If signal quality continues to decline the PPI-EXC alarm threshold will becrossed.



ImpactMajor alarm.



Possible causesPossible causes for the PPI-DEG alarm are:

• Errored input signals.


Corrective actions

Procedure 2-66PPI-DEG alarm clearing

Step Action

1 Investigate preceding equipment and cables for cause of errors.






—end—



2 a .

PPIPPI-Unexpected Signal

SignificanceThe PPI-UNEXP_SIGNAL alarm is raised where a signal is connected to2 Mbit/s or 140 Mbit/s port for which a traffic connection is not configured



ImpactMajor alarm.


Possible causesPossible causes for the PPI-UNEXP_SIGNAL alarm are:

• Incorrect cable connection.

• Incorrect System configuration.

• Faulty 2 Mbit/s or 140 Mbit/s tributary card.

Corrective actions

Procedure 2-67PPI-UNEXP_SIGNAL alarm clearing

Step Action

1 Check whether a connection is expected on this tributary.

If a connection is expected, re-configure system as necessary.

If a connection is not expected, go to step 2.

2 Check cable connections to ensure that the cables are connected to the correct input terminations.

If the cable connections are incorrect, re-connect the cables as required.

If the cable connections are correct, go to step 3.




—end—



g be

PPIPPI-Loss of Frame (LOF)

SignificanceThe PPI-LOF alarm is raised where a PDH port reports that signal framininformation cannot be recovered in the recieve path. This alarm will ony reported if the input port is configured to framed or multi-framed.



ImpactMajor alarm.


Possible causesPossible causes for the PPI-LOF alarm are:



Corrective actions

Procedure 2-68PPI-LOF alarm clearing

Step Action

1 Investigate preceding equipment and cables for cause of errors.






—end—



2nal put

PPIPPI-Loss of Multiframe (LOM)

SignificanceThe PPI-LOM alarm is raised where a 2 Mbit/s PDH port reports that sigmultiframing information cannot be recovered in the recieve path. The inport must be configured to multi-framed.



ImpactMajor alarm.


Possible causesPossible causes for the PPI-LOM alarm are:



Corrective actions

Procedure 2-69PPI-LOM alarm clearing

Step Action

1 Investigate preceding 2 Mbit/s equipment and cables for cause of errors.






—end—



f

PPIPPI-Loopback On

SignificanceThe PPI-LOOPBACK-ON alarm is raised if a local or remote loopback isplaced on a PDH port. This alarm is a reminder to the network operator oexisting configured loopbacks.



ImpactMinor alarm.


Possible causesLocal or remote loopback has been placed on a PDH port.

Corrective actionsIf required, remove the loopback as detailed in Network Surveillance Procedures, 323-1123-510.



2

PPIPPI- Transmit-Loss of Frame (T-LOF)

SignificanceThe PPI-T-LOF alarm is raised where a 140 Mbit/s PDH port reports thatsignal framing information cannot be recovered in the transmit path. Thisalarm will ony be reported if the input port is configured to framed or multi-framed.



ImpactMajor alarm.


Possible causesPossible causes for the PPI-T-LOF alarm are:


• Output cable fault.

Corrective actions

Procedure 2-70PPI-T-LOF alarm clearing

Step Action

1 Investigate preceding 140 Mbit/s equipment and cables for cause of errors.






—end—



S, a 15

ng

PPIPPI-Code violation Quality of service violation (15 minute)

SignificanceThe PPI_CV_qosv_15M alarm is raised to indicate that any BBE, ES, SEUAS active performanance monitoring threshold has been broken within minute monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the PPI_CV_qosv_15M alarm are:





Procedure 2-71PPI_CV_qosv_15M alarm clearing

Step Action

1 Check for the presence of code violation defects, PPI-LOF, PPI-AIS. Identify and remove the cause of these alarms.

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—



2S, a 24

PPIPPI-Code violation-Quality of service violation (24 hour)

SignificanceThe PPI_CV_qosv_24H alarm is raised to indicate that any BBE, ES, SEUAS active performanance monitoring threshold has been broken within hour monitoring period.



ImpactMinor Alarm


Possible causesPossible causes for the PPI_CV_qosv_24H alarm are:





Procedure 2-72PPI_CV_qosv_24H alarm clearing

Step Action

1 Check for the presence of code violation defects, PPI-LOF, PPI-AIS. Identify and remove the cause of these alarms.

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—



ing.

SYNCSync-SETG Fail

SignificanceThis alarm indicates that a serious problem has occurred in the synchronization source selection circuit on the indicated aggregate card.

Instance/UnitThis alarm is raised against an aggregate card instance, reported asS <slot-no>



The standby aggregate card is used as the source of synchronization tim


Possible causesFailure of the synchronization circuit on the indicated aggregate card.

Corrective actions

Procedure 2-73SYNC-SETG_Fail alarm clearing

Step Action

1 Replace the indicated aggregate card. Refer to Maintenance Procedures, 323-1123-547.

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

—end—



2ion

SYNCSync-Unexpected signal

SignificanceThe external synchronization input (ESI) port is receiving a synchronizatsignal but the port is not in the hierarchy list.

Instance/UnitThis alarm is raised against an external synchronization port instance, reported asS <slot-no> - 1


ImpactMajor alarm.


Possible causesThe ESI port is not in the SETG or ESO hierarchy list.

Corrective actionsAdd the ESI port to the hierarchy list.



ry

aise

SYNCSync-ESO Source Not Primary

SignificanceThe source currently selected to provide synchronization is not the primasource as defined in the ESO hierarchy list.

Note:

• If synchronization source messaging (SSM) is active this alarm is not raised.

• Selecting a synchronization source using a Forced override does not rthis alarm.

Instance/UnitNone.



Possible causesFailure of primary source.

Corrective actionsInvestigate primary source for possible faults or synchronization source switching actions.



2de is the

off e

nal

e.

SYNCSync-Holdover

SignificanceThis alarm is raised when the NE is operating in holdover mode. This moentered when all external synchronization input sources are rejected andinternal clock is running off historical values (or has just started).

The holdover alarm is not raised if the NE is deliberately configured to runthe internal oscillator (by a forced command or through an INT entry in thhierarchy list).

Instance/UnitThis alarm is raised against the NE.



Possible causesPossible causes for the SYNC-HOLDOVER alarm are:

• Forced switch to a faulty synchronization source.

• All sources on the hierarchy list are faulty and the NE is using the interoscillator for synchronization.

Corrective actionsIf a forced switch is active, check the status of the synchronization sourc

Change the hierarchy list to include a good synchronization source.



ry

t be

e,

SYNCSync-Source Not Primary

SignificanceThe source currently selected to provide synchronization is not the primasource as defined in the SETG hierarchy list.

Note:

• If synchronization source messaging (SSM) is active this alarm will noraised.

• If the current synchronization source was selected by a Forced overridthis alarm is not raised.

Instance/UnitNone.

ImpactMajor alarm.


Possible causesFailure of primary source.

Corrective actionsInvestigate primary source for possible faults or synchronization source switching actions.



2elf

r

SYNCSync-External Sync Loss Of Signal

SignificanceThe signal from the external synchronization input (ESI) on an End of Sh(EOS) card has failed.

Note: The external source must be in the synchronization hierarchy (oforced on) for the alarm to be raised.

Instance/UnitThis alarm is raised against an external synchronization port instance, reported asS <slot-no> - 1




Possible causesPossible 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-74SYNC-Ext_Sync_LOS alarm clearing

Step Action

1 Check that the ESI input connector is properly seated.

If the connector is not properly seated, re-insert connector.

If the connector is properly seated, go to step 2.

2 Check that a valid signal is present at the output of the ESI cable.

If a valid signal is not present, check the interconnecting cable and the external synchronization source.


3 Replace the indicated EOS card. Refer to Maintenance Procedures, 323-1123-547.


—end—



2 the

on)

SYNCSync-SETG Frequency suspect

SignificanceThe SETS reports an out of lock condition. This alarm means that eithercurrent synchronization source is out of limits or the SETS is out of lock.

Note: The source must be in the synchronization hierarchy (or forcedfor the alarm to be raised.


ImpactMajor alarm.


Possible causesFaulty synchronization source or SETS in the aggregate card.

Corrective actions

Procedure 2-75SYNC-SETG_frequency_suspect alarm clearing

Step Action

1 Apply a lockout to the indicated source. Refer to Provisioning and Operations Procedures, 323-1123-310.

If the alarm clears, the source is faulty.If the alarm is still present, go to step 2.

2 Replace the active aggregate card. Refer to Maintenance Procedures, 323-1123-547.

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

—end—



ffset.

or

SYNCSync-Source out of limits

SignificanceA port which can be used as a frequency source has a gross frequency o

Instance/UnitThis alarm is raised against an input port which is in either of the SETG ESO selector Synchronization Source Hierarchies.

ImpactMajor alarm.



Corrective actions

Procedure 2-76SYNC-SOURCE-OUT-OF-LIMITS alarm clearing

Step Action

1 Identify and remove the cause of the frequency errors.

2 Access the ‘Maint/Operations/Sync_source’ submenu by selecting

3 Execute the clr_out_of_limits command by selecting

4 Insert the port number of the alarm you wish to clear and select submit.

Confirmation is required

—end—

n Maint m

n Operations o

n Sync_source s

l clr_out_of_limits c



2lock

SYNCSync-Lock fail

SignificanceThis alarm is raised when either the SETG or ESO PLL reports an out-of-condition.

Instance/UnitThis alarm is raised against an aggregate card instance, reported asS <slot-no>





Corrective actions

Procedure 2-77SYNC-LOCK-FAIL alarm clearing

Step Action

1 Identify and remove the cause of the frequency errors.

2 Access the ‘Maint/Operations/Sync_source’ submenu by selecting

3 Execute the clr_out_of_limits command by selecting

4 Insert the port number of the alarm you wish to clear and select submit.

Confirmation is required

—end—

n Maint m

n Operations o

n Sync_source s

l clr_out_of_limits c



d

o a

MiscQecc Comms Fail

SignificanceThe NE cannot communicate with the neighbouring NE via the EmbeddeControl Channel (ECC).




Non-traffic affecting.

Inter-site data communications are unavailable.


Possible causesPossible causes for the Qecc Comms Fail alarm are:

• Loopback present.

• The card carrying the ECC has been unequipped.



When STM-1o tributary cards in a 1+1 MSP association are connected tTN-16X multiplexer, the non-active STM-1o port raises a ‘QECC commsfail’ alarm. This is normal operation and the alarm does not need to be cleared.



2

Corrective actions

Procedure 2-78Qecc_Comms_Fail alarm clearing

Step Action

1 Check if a loopback is present. Refer to Network Surveillance Procedures, 323-1123-510.

If a loopback is present, disable the loopback. If the alarm is still present, go to step 2.

If the alarm has cleared, the alarm clearing procedure is complete.

2 Check if any of the cards in the ECC path have been unequipped.

If the card is unequipped, re-equip it using the CAT. refer to Provisioning and Operations Procedures, 323-1123-310.

3 Examine the current Lapd mode.Refer to Provisioning and Operations Procedures, 323-1123-310.

4 Switch to Ms mode. Refer to Provisioning and Operations Procedures, 323-1123-310.



5 Switch to Rs mode. Refer to Provisioning and Operations Procedures, 323-1123-310.



6 Perform a status_view command to determine whether Rs or Ms has failed. Refer to Provisioning and Operations Procedures, 323-1123-310

Goto step 7

—continued—

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



Procedure 2-78 Qecc_Comms_Fail alarm clearing (continued)

Step Action







—end—



2

MiscINT NE-Spi Comms Fail

SignificanceA fault has been detected on the internal SPI communications function.




Non-traffic affecting.

Inter-site data communications are unavailable.


Possible causesPossible causes for the INT NE-Spi-Comms-Fail alarm are:



Corrective actions

Procedure 2-79Spi-Comms_Fail alarm clearing

Step Action




—end—



MiscEA-Ext inp <1-8>

SignificanceA alarm has been received on one of the external alarm inputs.

Instance/UnitThis alarm is raised against an external alarm input instance.



Possible causesDependant on the alarm source.

Corrective actionsInvestigate the alarm source for the cause of the alarm.



2E

is

rform

MiscINT NE-Configuration Corrupt

SignificanceThe configuration data held in the configuration bank is corrupt and the Nenters detached mode.

This alarm is raised only when one of the following configuration alarms raised:

• INT NE-config_all_banks_corrupt

• INT NE-config_available_bank_corrupt

• INT NE-config_validation_error

• INT NE-config_audit_mismatch

• INT NE-config_bp_mismatch




Possible causesConfiguration data corrupt.

Corrective actionsCheck which of the associated configuration alarms are also present. Pethe alarm clearing procedures for the associated alarm.



l

tor

MiscNE-Lan Alarm

SignificanceA 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/UnitThis alarm is raised against a LEOS port instance, reported asS 15B - <port-no>



Loss of communication to the EC and to any NEs connected via the locaLAN sub-network.


Possible causesPossible causes for the NE-Lan alarm are:

• LAN connector not properly terminated.

• Problem on LAN sub-network.

Corrective actionsCheck that the LAN connector is properly terminated. If the LAN connecis properly terminated, investigate the local LAN sub-network.



2

MiscNE-Unexpected LAN

SignificanceIndicates a LAN is present but the LAN service state is set to Standby (indicating that a LAN is not expected).

Instance/UnitNone.

ImpactMajor alarm.



Possible causesPossible causes for the Unexpected LAN alarm are:

• LAN is incorrectly connected.

• System is incorrectly configured.

Corrective actionsIf a LAN is expected, reconfigure the system as required (see Provisioning and Operations Procedures, 323-1123-310).

If a LAN is not expected, remove the LAN connection.



al rm

tion

MiscINT NE-Config bp mismatch

SignificanceThe serial number of the master aggregate card does not match the serinumber stored in the backplane SIM card. This check occurs during a waor cold restart of the master aggregate. The NE enters detached mode




Possible causesThe aggregate has been replaced or there is a mismatch in the configuradata.

Corrective actionsPerform the following procedures (refer to System and Data Administration Procedures, 323-1123-302):

• Check the configuration and change if necessary.

• Impose the stored configuration. This will;

—write the serial number of the aggregate cards into the SIM card

—take the NE out of detached mode

—remove the alarm



2iled.

MiscPs-power fail

SignificanceThe power supply to either the Upper or Lower end of shelf cards has fa

Instance/UnitThis alarm is raised against an EOS card instance, reported asS <slot-no>




Possible causesPower supply fail

Corrective actionsCheck the power connection to the indicated card.

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



e of

,

MiscNE-Date time unknown

SignificanceThis alarm is raised when the real time clock in the NE has no knowledgthe date and time.

Instance/UnitNone.

ImpactMajor alarm.



Possible causesA loss of power to the NE will cause the contents of the RTC to be lost.

Corrective actionsSet the real time clock. Refer to System and Data Administration Procedures 323-1123-302.



2

MiscUnexpected SW version

SignificanceThe software version on a tributary or aggregate card does not match theversion number in the configuration store.

Instance/UnitNone.

ImpactMinor alarm.


Possible causesCard installed with incorrect software load.

Corrective actionsPerform a software upgrade on the indicated card as detailed in System and Data Administration Procedures, 323-1123-302.



te or

MiscInternal 1 second clock loss of signal

SignificanceA card with a missing 1-second input clock will raise this alarm.

Instance/UnitThis alarm is raised against a card instance, reported asS <slot-no>


ImpactMajor alarm.


Possible causesPossible causes for this alarm are:

• aggregate failure.

• tributary failure.

• Backplane failure.

Corrective actionsPerform a SEMF protection switch. If the alarm persists, replace aggregatributary card (see Provisioning and Operations Procedures, 323-1123-310).



2hout

CardNE-Card Out

SignificanceIndicates that the indicated card has been removed from the subrack witunequipping the slot.

Note: When a card is inserted, the NE-Card_Out alarm remains activeuntil the card is configured in order to suppress other alarms.

Instance/UnitThis alarm is raised against an NE card instance, reported asS <slot-no>




Possible causesPossible causes for the Card Out alarm are:

• Card removed.

• System incorrectly configured.

• Faulty aggregate card.



Corrective actions

Procedure 2-80NE-Card_Out alarm clearing

Step Action

1 Check if the card is expected in the indicated slot.

If the card is not expected, go to step 2.

If the card is expected in the indicated slot, check that the card is correctly installed in the TN-4E. If the alarm still present, go to step 3.

2 Configure the equipment to unequip the indicated slot, see Provisioning and Operations Procedures, 323-1123-310.



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


If the alarm is still present, replace original aggregate card and escalate problem.

—end—



2ed’.

ctive

CardNE-Unexpected Card

SignificanceIndicates that a card is present in a slot which is configured as ‘UnequippThis alarm is raised approximately 30 seconds after the card is inserted.

Note: When a card is inserted, the Unexpected_Card alarm remains auntil the card is configured, in order to suppress other alarms.



ImpactMajor alarm.


Possible causesPossible causes for the Unexpected Card alarm are:

• Card inserted into wrong slot.





Corrective actions

Procedure 2-81NE-Unexpected_Card alarm clearing

Step Action

1 Check if the card is expected in indicated slot.

If the card is expected, go to step 2.

If the card is not expected, remove the card from the indicated slot. If alarm still present, go to step 3

2 Configure the equipment to equip the slot with the correct card type (see Provisioning and Operations Procedures, 323-1123-310).


If the alarm still present, go to step 3.

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


If the alarm still present, replace original aggregate card and escalate problem.

—end—



2

CardNE-Card Fail

SignificanceThe aggregate card detects a fault on the indicated card or fails to communicate with the indicated card.




May be traffic affecting.


Possible causesPossible causes for the Card Fail alarm are:

• Faulty indicated card.


Corrective actions

Procedure 2-82NE-Card_Fail alarm clearing

Step Action

1 Check if the alarm is permanently indicated for all cards.

If the alarm is permanently indicated for all cards, replace the active aggregate card. Refer to the Maintenance Procedures, 323-1123-547. Go to step 3.

If the alarm is permanently indicated for a single card, go to step 2.

2 Perform a warm restart on the card.If the alarm is still present, perform a cold restart on the card.

3 Check if alarm is still present.

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

—end—



CardNE-Card Fault

SignificanceSelf-diagnosis indicates the card has a fault.




Traffic is affected if the fault is on an aggregate or tributary card.


Possible causesFaulty indicated card.

Corrective actionsIf the alarm is repeated or persistent, replace indicated card. Refer to theMaintenance Procedures, 323-1123-547.



2(slot

CardNE-Wrong Card

SignificanceA card has been inserted into a slot designated for another type of card wrong or card wrong).




Traffic is affected if traffic card.


Possible causesPossible causes for the Wrong Card alarm are:

• Wrong card fitted in a slot.

• Card fitted in wrong slot.


Corrective actions

Procedure 2-83NE-Wrong_Card alarm clearing

Step Action

1 Check what unit should be fitted in the indicated slot.

If the correct unit is not fitted to the slot, remove the current unit and fit the correct unit. Go to step 2.

If the correct unit is fitted, reconfigure the slot to be equipped with the correct unit type (see Provisioning and Operations Procedures, 323-1123-310). Go to step 2.

2 Check if alarm is still present.



—end—



s to

CardNE-Invt Write Jumper Fitted

SignificanceThis alarm indicates that a link is present on a card which enables accesthe non-volatile RAM.



ImpactMajor alarm.


Possible causesLink is present on the card.

Corrective actionsContact Nortel Networks technical support.



2d

CardNE-Minor card mismatch

SignificanceThis alarm occurs when the operator configures a slot for a card type ansub release but inserts a card with a lower sub release.



ImpactMinor alarm.


Possible causesWrong sub release of card in slot

Corrective actionsReplace the card or re-equip the slot for the correct sub-release (see Provisioning and Operations Procedures, 323-1123-310).



s

ConfigINT NE-Configuration Corrupt Bank

SignificanceThe configuration data held in the active non volatile configuration bank icorrupt.


ImpactMajor alarm.


Possible causesPossible causes for the Configuration Corrupt bank alarm are:

• Non volatile store corruption on the aggregate card.

• Continual cyclic reboots.

Corrective actions

Procedure 2-84INT-NE_Config_Corrupt_Bank

Step Action

1 Carry out a restore of the configuration bank as detailed in System and Data Administration Procedures, 323-1123-302.

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



—end—



2

ConfigINT NE-Configuration All Banks Corrupt

SignificanceThe configuration data held in both the active and standby non-volatile configuration banks is corrupt.


ImpactMajor alarm.

Consequent actionThe 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 causesPossible causes for the Configuration All Banks Corrupt alarm are:

• Non-volatile store corruption on the aggregate card.


Corrective actions

Procedure 2-85INT-NE_Config_All_Banks_Corrupt

Step Action

1 Carry out a restore of the configuration banks as detailed in System and Data Administration Procedures, 323-1123-302.




—end—



ConfigINT NE-Configuration Available Bank Corrupt

SignificanceThis alarm is raised if the data held in the configuration bank is corruptedduring a software upgrade or configuration restore procedure.


ImpactMajor alarm.

Consequent actionThe NE enters detached mode

The following procedures are not allowed until the alarm is cleared:

• software upgrade

• configuration changes

• consolidation of the configuration banks

• a restore of the configuration banks

• traffic card provisioning

Possible causesPossible causes for the Configuration Available Bank Corrupt alarm are:





2

Corrective actions

Procedure 2-86INT NE-Config_Avail_Bank_Corrupt

Step Action

1 Display the configuration table status. Access the ‘Admin/cnfg_tbl’ submenu by selecting

Display the configuration table status by selecting

2 If the upgrade status is ‘Ready_to_commit’ then go to step 3.If the upgrade status is ‘Ready_to_activate’ then go to step 4.

3 Execute the Switch to original command by selecting

A confirmation is required.

4 Execute the backout command by selecting

5 Restart the software upgrade or configuration restore. Refer to System and Data Administration Procedures, 313-1123-302.



—end—

n Admin a

n Cnfg_tbl c

l View v

l Switch_to_original re

l Backout bo



he

ConfigINT NE-Configuration Software Mismatch

SignificanceThe version of software loaded on a card and the version referenced in tconfiguration bank are different.


ImpactMajor alarm.


Possible causesNew card inserted with incorrect software or configuration version.

Corrective actions

Procedure 2-87INT NE-Cfg_sw_mismatch

Step Action

1 Display the software and configuration table status. Access the ‘Admin/cnfg_tbl’ submenu by selecting

Display the status by selecting

2 If the software version is correct carry out step 3. If the software version is incorrect carry out step 4.

—continued—

n Admin a

n Cnfg_tbl c

l View v



2

Procedure 2-87 INT NE-Cfg_sw_mismatch (continued)

Step Action

3 Consolidate the configuration table. Access the ‘Admin/cnfg_tbl’ submenu by selecting

Consolidate the configuration table status by selecting

No confirmation is required.

4 If the alarm is still present, carry out a software download as detailed in System and Data Administration Procedures, 323-1123-302.



—end—

n Admin a

n Cnfg_tbl c

l Consolidate c



ConfigINT NE-Configuration Audit Mismatch

SignificanceA configuration audit indicates that the configuration data in the RAM is different to the configuration settings on the traffic cards.


ImpactMajor alarm.


Possible causesAudit mismatch.

Corrective actions

Procedure 2-88INT NE-Cfg_Audit_Mismatch

Step Action

1 If the configuration of the traffic cards is correct go to step 2.

2 If the data in the configuration store is correct go to step 3.

3 Manually update the configuration data in the configuration store.

4 Impose the configuration data. Access the ‘Admin/cnfg_tbl’ submenu by selecting

Execute the impose command by selecting

A confirmation is required.



—end—

n Admin a

n Cnfg_tbl c

l Impose_config ic



2

ConfigINT NE-Configuration Validation Error

SignificanceDuring a restart, a value read from the configuration store is invalid.


ImpactMajor alarm.


Traffic card provisioning is not allowed until the alarm is cleared:

Possible causesIncorrect software or configuration version.

Corrective actions

Procedure 2-89INT NE-Cfg_validation_error

Step Action

1 Carry out a restore of the configuration banks as detailed in System and Data Administration Procedures, 323-1123-302.




—end—



iled

ConfigINT NE-Standby Configuration Software Unstable

SignificanceThis alarm indicates a problem with the standby software.


ImpactMajor alarm.


Possible causesSoftware or configuration problem.

Corrective actionsPerform a backup of the active configuration store to the standby as detain System and Data Administration Procedures, 323-1123-302.



2

iled

ConfigINT NE-Standby Configuration Flash Corrupt

SignificanceThis alarm indicates a problem with the standby flash memory.


ImpactMajor alarm.


Possible causesCorruption of the standby non-volatile configuration banks.




n

iled

ConfigINT NE-Standby Configuration audit mismatch

SignificanceThe configuration data held in the active non-volatile standby configuratiobank is corrupt.


ImpactMajor alarm.


Possible causesPossible causes for the alarm are:






2

iled

ConfigINT NE-Standby Configuration fail

SignificanceThe configuration bank on the stand-by aggregate has failed.


ImpactMajor alarm.


Possible causesStand-by flash memory is corrupt or the stand-by configuration state is misaligned with the master aggregate.




ProtEquip_Fail

SignificanceRaised when a 1+1 protection I/O card fails.

Instance/UnitThis alarm is raised against the working tributary card.

ImpactMajor alarm.


Possible causesHardware failure on 1+1 protection I/O card.

Corrective actionsReplace the 1+1 protection I/O card. Refer to the Maintenance Procedures, 323-1123-547.



2no

not

ries.

ProtEquip_Out

SignificanceRaised when both the 1+1 working and protection tributary cards detect connection to the 1+1 protection I/O card.

Instance/UnitThis alarm is raised against the working tributary card.

ImpactMajor alarm.


Possible causesInterface cable between the 1+1 protection I/O card and the tributaries ispresent or is incorrectly connected.

Corrective actionsCheck interface cable between the 1+1 protection I/O card and the tributa



ction

ProtUnexpected_Equip

SignificanceRaised where the 1+1 I/O card is connected to a tributary card in a proteslot, but that slot is not in a 1+1 card association.

This alarm is not raised against a card in a working slot.

Instance/UnitThis alarm is raised against a protection tributary card.

ImpactMajor alarm.


Possible causesCard association not made by operator

Corrective actionsCreate card association for 1+1 card protection (see Provisioning and Operations Procedures, 323-1123-310).



2 1+1

.

port

ProtCable_Error

SignificanceRaised to indicate that a cable fault exists between a tributary slot and aprotection I/O card.

Instance/UnitThis alarm is raised against the working or protection card slot.

ImpactMajor alarm.

Consequent actionProtection switch to the other slot in the association.

Possible causesFault 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 on the 1+1 protection I/O card.

Corrective actionsReplace the interface cable between the 1+1 protection I/O card and thetributaries.



tion

ProtWrong_Equip

SignificanceRaised to indicate a mismatch between a tributary card and a 1+1 protecI/O card.

Instance/UnitThis alarm is raised against the working or protection card slot.

ImpactMajor alarm.


Possible causes1+1 protection I/O card and the tributaries are not compatible.

Corrective actionsReplace either the 1+1 protection I/O card or the tributaries



2hen

rent

MSPFOP_PAM

SignificanceThe Failure Of Protocol-Protection Architecture Mismatch alarm raises wthe multiplexing equipments at either end of transmission path are usingdifferent protection architectures. For example, the local multiplexer is operating 1+1 MSP and the remote end is operating 1:N protection.

Instance/UnitThe alarm is raised against bidirectional SDH protection ports.

ImpactMajor alarm.


Possible causesMultiplexing equipment at either end of transmission path are using diffeprotection architectures.

Corrective actionsReconfigure equipment to a common protection architecture.



and

s

cross

MSPFOP_SCM

SignificanceThe Failure Of Protocol-Selector Channel Mismatch alarm is raised to indicate that a difference exists in the transmitted channel of the K1 bytethe received channel K2 byte.


ImpactMajor alarm.

Consequent actionCauses an MSP protection switch.

Possible causesPossible causes for the FOP_SCM alarm are:

• Indicates a protocol failure.

• Incorrect optical fibre connection between protection and working cardacross the transmission path.

Corrective actionsEnsure optical fibre connections between protection and working cards athe transmission path are correct.



2d

d

MSPFOP_INV

SignificanceThe Failure Of Protocol-Invalid alarm is raised to indicate that the receiveK1 byte is invalid.


ImpactMajor alarm.

Consequent actionThis is an signal fail condition so it causes a MSP protection switch.

Possible causesPossible causes for the FOP_INV alarm are:

• Optical hygiene problem.



Corrective actionsExamine fibre-optic path for hygiene problems and replace local or far encards as necessary.



een

s

tical

MSPFOP_TMOUT

SignificanceThe Failure of protocol-Timeout alarm indicates that the K1 byte has not breceived within the specified 50 ms.


ImpactMajor Alarm

Consequent actionThis is an signal fail condition so it causes a MSP protection switch.

Possible causesPossible 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 cardacross the transmission path.

Corrective actionsReconfigure equipment to a common protection architecture or ensure opfibre connections between protection and working cards across the transmission path are correct.

end of chapter


3-1

3
Index 3-
Aaction

logfault clearing 1-2

alarmclearing 1-1consequent action 1-7correlation 1-3indications 1-2RAU category 1-4severity 1-4

AU-Alarm_Indication_Signal (AIS) alarm 2-45

AU-Loss_of_Pointer (LOP) alarm 2-47

CCable_Error alarm 2-173clearing

faultstaction log 1-2

consequent actionalarm 1-7

Critical (alarm severity) 1-6

DDeferred (RAU category) 1-6

EEA-Ext_inp alarm 2-140Equip_Fail alarm 2-170Equip_Out alarm 2-171

Ffaults

clearing faultsaction log 1-2

HHP-Excessive errors (EXC) alarm 2-48HP-Loss_of_Multiframe (LOM) alarm 2-56HPOM-Excessive errors (EXC) alarm 2-71HP-Path_Label_Mismatch (PLM)

alarm 2-59, 2-75HP-Remote_Defect_Indicator (RDI)

alarm 2-54HP-Remote_Error_Indicator (REI)

alarm 2-58HP-Signal Degrade (DEG) alarm 2-50HP-Signal_Fail (SF) alarm 2-63HP-Trace Identifier Mismatch (TIM) 2-52,

2-73HP-Unequipped alarm 2-61, 2-77

IIn station (RAU category) 1-6INT LP-Input Buffer Overflow alarm 2-65,

2-91INT LP-Output Buffer Overflow alarm 2-66,

2-93INT NE-Config_All_Banks_Corrupt

alarm 2-159INT NE-Config_Audit_Mismatch

alarm 2-164INT NE-Config_Available_Bank_Corrupt

alarm 2-160INT NE-Config_Bp_Mismatch alarm 2-144INT NE-Config_Corrup_Bank alarm 2-158INT NE-Config_Corrupt alarm 2-141INT NE-Config_Software_Mismatch

alarm 2-162INT NE-Config_Validation_Error

alarm 2-165INT NE-Spi_Comms_Fail alarm 2-139INT NE-Standby_Config_Audit_Mismatch

alarm 2-168INT NE-Standby_Config_Fail alarm 2-169


3-2 Index

INT NE-Standby_Config_Flash_Corrupt alarm 2-167

INT NE-Standby_Config_Sw_Unstable alarm 2-166

INT TU-Alarm Indication Signal (AIS) alarm 2-81

INT TU-Loss of Pointer (LOP) alarm 2-82

LLED

card alarms 1-2RAU alarms 1-2

logaction log

clearing faults 1-2LP-Excessive errors 2-83LP-Excessive_Errors (EXC) alarm 2-83LP-Label Unequipped alarm 2-98, 2-110LPOM-Excessive_Errors (EXC) alarm 2-104LP-Path Label Mismatch (PLM) alarm 2-86,

2-108LP-Remote Defect Indicator (RDI)

alarm 2-88LP-Remote Error Indication (REI)

alarm 2-90LP-Signal Degrade (DEG) alarm 2-84LP-Signal_Fail (SF) alarm 2-95LP-Trail Indentifier Mismatch (TIM)

alarm 2-96, 2-106

Mmaintenance

philosophy 1-1Major (alarm severity) 1-6Minor (alarm severity) 1-6MS-Alarm_Indication_Signal (AIS)

alarm 2-31MS-Excessive_Errors (EXC) alarm 2-37MSP FOP_INV alarm 2-177MSP FOP_PAM alarm 2-175MSP FOP_SCM alarm 2-176MSP FOP_TMOUT alarm 2-178MS-Remote_Defect_Indicator (RDI)

alarm 2-33MS-Remote_Error_Indicator (REI)

alarm 2-35MS-Signal_Degrade (DEG) alarm 2-39

NNE-Card_Fault alarm 2-154NE-Card_Out alarm 2-149NE-Date_Time_Unknown alarm 2-146NE-Invt_Write_Jumper_Fitted alarm 2-156NE-Lan_Alarm 2-142NE-Unexpected_Card alarm 2-151NE-Unexpected_LAN alarm 2-143NE-Wrong_Card alarm 2-155

OOS alarms 2-11OS-Disable_Laser_Shutdown alarm 2-13OS-Laser_Bias_High alarm 2-12OS-Laser_Shutdown alarm 2-14OS-Optical_Power_High alarm 2-11

PPPI-Alarm Indication Signal (AIS)

alarm 2-116PPI-Excessive errors (EXC) alarm 2-15,

2-117PPI-Loopback On alarm 2-122PPI-Loss Of Frame (LOF) alarm 2-120,

2-123PPI-Loss Of Multiframe (LOM) alarm 2-121PPI-Loss Of Signal (LOS) alarm 2-114PPI-Signal Degrade (DEG) alarm 2-118PPI-Transmit Fail (TF) alarm 2-16, 2-112PPI-Unexpected Signal alarm 2-119Prompt (RAU category) 1-6PS-Power_Fail alarm 2-145

QQecc_Comms_Fail alarm 2-136

Rrack alarm unit (RAU)

alarm category 1-4alarm indications 1-2

RS-Excessive_Errors (EXC) alarm 2-24RS-Loopback_On alarm 2-28RS-Loss_of_Signal (LOS) alarm 2-20RS-Trace_Identifier_Mismatch (TIM)

alarm 2-26RS-Unexpected_Signal alarm 2-19


Index 3-3

3

SSync-ESO_Source_Not_Primary

alarm 2-128SYNC-External_Sync_LOS alarm 2-131Sync-Holdover alarm 2-129Sync-SETG_Fail alarm 2-126Sync-SETG_Frequency_Suspect

alarm 2-133Sync-Source_Not_Primary alarm 2-130Sync-Unexpected_Signal alarm 2-127

TTU-Alarm_Indication_Signal alarm 2-79TU-Loss_of_Pointer (LOP) alarm 2-80

UUnexpected_Equip alarm 2-172Unexpected_SW_Version alarm 2-147

WWarning (alarm severity) 1-6Wrong_Equip alarm 2-174


International Optical NetworksNortel NetworksOakleigh Road SouthLondon N11 1HB

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

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

SDH TRANSMISSION

Nortel TN-4XEAlarm Clearing ProceduresCopyright © 1998 - 2000, Nortel Networks, All Rights Reserved.

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

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

Document Number: 323-1123-543Product Release Number: Release 3.01Status: StandardDate: March 2000Printed in England

Documents

Alrm Clear 4xe31