323-1081-543

SDH TRANSMISSION

Nortel TN-1C
Alarm Clearing Procedures
Release 2 Standard June 1997

SDH TRANSMISSION

Nortel TN-1C
Alarm Clearing Procedures

Document Number: 323-1081-543 Document Status: Standard Product Release Number: Release 2 Date: June 1997

Copyright Coypright statement Country of printing NT confidential NTE disclaimer Trademarks

Copyright 1996, 1997 Northern Telecom

The copyright of this document is the property of Northern Telecom. Without the written consent of Northern Telecom, 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.

Printed in England NORTHERN TELECOM CONFIDENTIAL:

The information contained in this document is the property of Northern Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation, and maintenance purposes only. So far as Northern Telecom is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Northern Telecom can give no warranty or undertaking and make no representation as to their accuracy. In particular, Northern Telecom 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.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

iii

Publication history
June 1997 Release 2 Standard. December 1996 Release 1 Standard.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

Contents
About this document Technical support and information Chapter 1: Introduction
Maintenance philosophy 1-1 Alarm indications 1-1 Element Controller 1-2 Craft access terminal 1-2 Unit indications 1-2 Alarm masking 1-3 Alarm consequences 1-6 Beginning fault finding 1-8 Responding to logs 1-8 Alarm category and severity 1-9

xi xii 1-1

Chapter 2: Clearing equipment alarms

PS-Power_Fail 2-4 PS-Battery_Low 2-5 INT-NE-SW_Corrupt 2-6 INT-EC-Alarms_Buffer 2-7 NE-Door_Open 2-8 PS-Door_Open 2-9 INT-NE-RAM_Fail 2-11 INT-NE-Config_Corrupt 2-12 NE-Card_Fail 2-14 RS-Loss_of_Signal 2-15 OS-Optical_Power_High 2-18 OS-Laser_Bias_High 2-19

2-1

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

vi Contents INT-RS-Tx_Buffer 2-20 INT-HP-Insert_Bus 2-21 RS-Loss_of_Frame 2-22 RS-Realign_Phase 2-25 INT-OS-Laser_Test 2-27 OS-Laser_Shutdown 2-28 MS-Excessive_BER 2-29 MS-Signal_Degrade 2-32 MS-AIS 2-34 MS-FERF 2-36 INT-HP-IP_Buffer 2-37 Qecc-Comms_Fail 2-39 AU-AIS 2-41 HP-TU_Multiframe 2-43 INT-AU-LOP 2-45 INT-AU-AIS 2-47 HP-Excessive_BER 2-49 HP-Signal_Degrade 2-50 HP-FERF 2-51 HP-FEBE 2-52 TU-AIS 2-53 TU-LOP 2-55 HP-Path_Trace 2-57 HP-Signal_Label 2-59 INT-TU-AIS 2-61 INT-TU-LOP 2-62 LP-Excessive_BER 2-63 LP-Signal_Degrade 2-65 TN-1C Alarm Clearing Procedures 323-1081-543 Release 2 Standard

Contents vii LP-Signal_Label 2-66 LP-FERF 2-68 LP-FEBE 2-69 INT-LP-OP_Buffer 2-70 PPI-Output_Fail 2-71 PPI-Unexp_Signal 2-72 PPI-Loss_of_Signal 2-73 PPI-Excessive_BER 2-75 PPI-Signal_Degrade 2-76 INT-LP-IP_Buffer 2-77 EA-Ext_inpn 2-78 SYNC-Holdover 2-79 SYNC-SETG_Fail 2-80 NE-Ext_Card_Out 2-81 NE-Wrong_Card 2-82 NE-Unexpected_Card 2-84 NE-Fan_Fail 2-85 NE-High_Temp 2-86

Chapter 3: Common procedures

Optical connector cleaning 3-2 Optical output power measurement 3-5 Optical input power measurement 3-7 Applying/clearing loopbacks 3-9

3-1

Chapter 4: Diagnostic tools

Loopbacks 4-1 STM-1 local loopback (Loop to Mux) 4-1 STM-1 remote loopback (Loop to Line) 4-2 Tributary local loopback (Loop to Mux) 4-2 Tributary remote loopback (Loop to Line) 4-2 Simultaneous loopbacks 4-2 2 Mbit/s or 34 Mbit/s test pattern generator and detector 4-4

4-1

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

viii Contents

Index Figures
Figure 1-1 Figure 1-2 Figure 4-1 Figure 4-2 Masking hierarchy (part 1) 1-4 Masking hierarchy (part 2) 1-5 TN-1C loopbacks 4-3 PRBS location 4-4

5-1

Tables
Table 1-1 Table 1-2 Table 2-1 Alarm consequences 1-7 Alarm category and alarm severity settings 1-9 List of alarm clearing procedures 2-2

Procedures
Procedure 2-1 Procedure 2-2 Procedure 2-3 Procedure 2-4 Procedure 2-5 Procedure 2-6 Procedure 2-7 Procedure 2-8 Procedure 2-9 Procedure 2-10 Procedure 2-11 Procedure 2-12 Procedure 2-13 Procedure 2-14 Procedure 2-15 Procedure 2-16 Procedure 2-17 Procedure 2-18 Procedure 2-19 Procedure 2-20 Procedure 2-21 Procedure 2-22 Procedure 2-23 Procedure 2-24 Procedure 2-25 Procedure 2-26 Procedure 2-27 Procedure 2-28 Procedure 2-29 Procedure 2-30 Procedure 2-31 Procedure 2-32 Procedure 2-33 Procedure 2-34 Procedure 2-35 Procedure 2-36 Procedure 2-37 Procedure 2-38 Procedure 2-39 Procedure 2-40 TN-1C Alarm Clearing Procedures PS-Power_Fail alarm clearing 2-4 PS-Battery_Low alarm clearing 2-5 NE-Door_Open alarm clearing 2-8 PS-Door_Open alarm clearing 2-9 INT-NE-Config_Corrupt alarm clearing 2-12 RS-Loss_of_Signal alarm clearing 2-16 RS-Loss_of_Frame alarm clearing 2-23 STM-Realign_Phase alarm clearing 2-25 MS-Excessive_BER alarm clearing 2-30 MS-Signal_Degrade alarm clearing 2-32 MS-AIS alarm clearing 2-35 MS-FERF alarm clearing 2-36 INT-HP-IP_Buffer alarm clearing 2-37 Qecc-Comms_Fail alarm clearing 2-39 AU-AIS alarm clearing 2-42 HP-TU_Multiframe alarm clearing 2-44 HP-Excessive_BER alarm clearing 2-49 HP-Signal_Degrade alarm clearing 2-50 HP-FERF alarm clearing 2-51 HP-FEBE alarm clearing 2-52 TU-AIS alarm clearing 2-54 TU-LOP alarm clearing 2-56 HP-Path_Trace alarm clearing 2-58 HP-Signal_Label alarm clearing 2-60 LP-Excessive_BER alarm clearing 2-64 LP-Signal_Degrade alarm clearing 2-65 LP_Signal_Label alarm clearing 2-67 LP-FERF alarm clearing 2-68 LP-FEBE alarm clearing 2-69 INT-LP-OP_Buffer alarm clearing 2-70 PPI-Output_Fail alarm clearing 2-71 PPI-Loss_of_Signal alarm clearing 2-74 PPI-Excessive_BER alarm clearing 2-75 PPI-Signal_Degrade alarm clearing 2-76 INT-LP-IP_Buffer 2-77 SYNC-Holdover alarm clearing 2-79 SYNC-SETG_Fail alarm clearing 2-80 NE-Ext_Card_Out alarm clearing 2-81 NE-Wrong_Card alarm clearing 2-82 NE-Unexpected_Card alarm clearing 2-84 323-1081-543 Release 2 Standard

Contents ix Procedure 3-1 Procedure 3-2 Procedure 3-3 Procedure 3-4 Procedure 3-5 Procedure 4-1 Cleaning an optical plug 3-3 Cleaning an optical coupler 3-4 Optical output power measurement 3-5 Optical input power measurements 3-7 Applying/removing loopbacks 3-10 Applying/stopping a continuity test 4-5

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

xi

About this document

This document provides information on the alarm clearing procedures for the TN-1C add/drop multiplexer. The document is divided into the following chapters:
0

Chapter 1: Provides general information regarding the maintenance philosophy and an guide to beginning fault nding. Chapter 2: Provides details on each of the alarms generated by the TN-1C and procedures for clearing each fault. Chapter 3: Provides details of common procedures used in the alarm clearing procedures. Chapter 4: Provides details of diagnostic tools available on the TN-1C which may be used in the alarm clearing procedures.

Audience This document is intended for:

0

Maintenance engineers Customer support engineers

Associated documents Personnel must ensure that they are familiar with TN-1C Documentation Overview and Safety, NTP 323-1081-090 which includes essential safety information. Procedures where the User Interface (UI) for the TN-1C is used require reference to TN-1C User Interface Guide, NTP 323-1081-401. Procedures for changing eld replaceable units are given in TN-1C Equipment Maintenance Procedures, NTP 323-1081-547.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

xii

Technical support and information

Nortel provides a comprehensive technical support service for its customers. The Nortel Service Desk may be contacted between the hours of 8:30 am and 5:00 pm, Monday to Friday (UK local time), using the following FAX or telephone numbers: United Kingdom Freephone: 0800 626 881 Telephone: 0181 361 4693 FAX: 0181 945 3456 International Telephone: +44 181 361 4693 FAX: +44 181 945 3456 Access to assistance from the Customer Service Desk 24-hour help line can be provided and is subject to a suitable Support Agreement being in place. To discuss Technical Support services, please contact the Technical Support Hotline on 0181 945 3525.

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

End of chapter file

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

1
1-1

Chapter 1: Introduction
Maintenance philosophy
This chapter provides the eld maintenance strategy for locating faulty equipment. The maintenance philosophy is to identify the faulty equipment without the need for extensive on-site maintenance. At all times, the maintenance procedures attempt to avoid disrupting live trafc.

Alarm indications
When a defect is detected, the following occurs: When used in a managed environment, the defect is reported to the TN-MS Element Controller (TN-MS EC). The Element Controller provides a consolidated view of the active alarms in the network and provides alarm log facilities. The Element Controller also passes active alarms to the Network Resource Manager (NRM), if applicable, for rst-alert functionality. The alarm is logged for access by operational personnel via the craft access terminal (CAT). The CAT also provides additional information which may be used in fault diagnosis (alarm logs, performance measurements). If the Rack Alarm Adapter is tted, the appropriate LEDs on the Rack Alarm Adapter are lit and graded alarm extensions are provided to the station alarm system. The appropriate LEDs on the TN-1C units are lit. Where possible, services are re-established by performing path protection switching. When the alarm indicates a path failure or receipt of AIS, an AIS is inserted in all dependent downstream paths and, if appropriate, a remote alarm indication is sent in the opposite direction and is detected by the remote multiplexer.

The TN-1C multiplexer performs a degree of alarm correlation (masking) to limit the number of reports to the craft access terminal (see Unit indications on page 1-2).

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

1-2 Introduction

Element Controller
The TN-MS Element Controller (TN-MS EC) provides all the facilities needed for exible management of synchronous digital networks based on Nortels synchronous multiplexers. When an TN-1C Network Element (NE) is brought within the TN-MS ECs span of control, a Element Controller Association Session (ECAS) is set up between the TN-1C and the TN-MS EC. This provides a communications channel through which unsolicited event and alarm messages are sent, performance monitoring reports are polled, and NE clocks are aligned. The TM-MS EC also provides access to the user interface (UI) on the TN-1C NE for conguration and monitoring facilities. When used with the TN-1C, the TN-MS EC provides consolidated alarm reporting for all NEs within its span of control, providing alarm counts according to the severity of the alarms. The TN-MS also provides alarm/event logs which can be viewed, printed and archieved. The TN-MS EC requests performance monitoring reports from the TN-1C NE once every 8 hours which are stored in a daily log. The logs are kept in a comma delimited le which simplies the exporting to external spreadsheet programs. Viewing, ltering, printing and exporting of performance monitoring reports is carried out outside the TN-MS EC. Logs are saved for 7 days.

Craft access terminal

The craft access terminal is an IBM-PC compatible Laptop computer running VT-100 emulation software. Access with the TN-1C is via an RS232 serial interface port. The craft access terminal uses the TN-1C multiplexers user interface. This interface uses simple commands to display and change conguration data and to view multiplexer status reports (e.g. alarms, performance monitoring). Details of the craft access facilities are given in the TN-1C User Interface Guide, NTP 323-1081-401.

Unit indications
The following indications are provided on the various TN-1C units: TN-1C multiplexer unit (not visible when cover is tted) Red FAIL LED (main card). Indicates that a defect has been detected on the unit. Red FAIL LED (tributary extension card). Indicates that a NE-Wrong_Card, NE-Unexpected_Card or NE-Card_Fail alarm has been detected on the tributary extension card. Green ACTIVE LED. Indicates that the +5 V supply is present on the unit.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Introduction 1-3

Power Supply Unit (on alarm/interface unit, not visible when cover is tted) Red LED. Indicates a low battery voltage and that the batteries have been disconnected from the load. Green LED. Indicates that the charger output is within the normal working range of -25.5 V to -30 V d.c.

Rack Alarm Adapter (optional) Red Alarm LED. Green Receive Att LED. The two LEDs indicate the overall alarm state of the TN-1C as follows: Both LEDs off indicates that the subrack has no alarms. Red LED only on indicates that the subrack has one or more unacknowledged alarm. Green LED only on indicates that an acknowledged alarm has not yet cleared. Both LEDs on indicates that an acknowledged alarm has cleared.

Alarm masking
Alarm masking is the process by which alarm correlation is performed. This ensures that if several related alarms occur, only the highest importance alarm on the same trafc path is reported, all other related alarms are reported as clear. If the high-priority alarm clears, the alarm with the highest priority of the remaining alarms is reported. For example, if RS-Loss_of_Signal and AU-AIS are both detected, only RS-Loss_of_Signal is reported as AU-AIS is a consequence of RS-Loss_of_Signal, therefore the AU-AIS indication has a high probability of being caused by the RS-Loss_of_Signal. Figure 1-1 and Figure 1-2 show the masking hierarchy for the TN-1C.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

1-4 Introduction Figure 1-1 Masking hierarchy (part 1)

1-1

PS-Battery_ Low

INT-NE-S/W _Corrupt

INT-NERAM_Fail

INT-ECAlarms_Buffer

SYNCHoldover

NEDoor_Open

PSDoorOpen

PS-Power_ Fail

INT-NECong_Corrupt

SYNC-SETG _Fail

EA-Ext_ inpn

NE-Card_ Fail

NE-Fan _High_Temp

INT-RSTx_Buffer

OS-Optical_ Power_High

RS-Loss_ of_Signal

OS-Laser_ Bias_High

INT-OSLaser_Test

NE-Fan_ Fail

INT-HPInsert_Bus

RS-Realign_ Phase

RS-Loss_ of_Frame

OS-Laser_ Shutdown

MS-FERF

MS-AIS

QeccComms_Fail

MS-Excessive _BER

MS-Signal _Degrade

AU-AIS

A
To Figure 1-2

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Introduction 1-5 Figure 1-2 Masking hierarchy (part 2)

1
1-2

From Figure 1-1

A
INT-HPIP_Buffer

INT-AU_LOP

INT-AU_AIS

HP-Excessive _BER

NE-Ext_ Card_Out

HP-Signal_ Degrade

HP-FERF

HP-TU_ Multiframe

HP-Path_ Trace

NE-Wrong_ Card

HP-FEBE

TU-LOP

HP-Signal_ Label

NE-Unexpected _Card

TU-AIS

NE-Card_ Fail

INT-TU_LOP

PPI-Unexp_ Signal

PPI-Output_ Fail

INT-TU_AIS

PPI-Loss_of _Signal

LP-Excessive _BER

INT-LP-I/P _Buffer

PPI-Excessive _BER

INT-LP-OP _Buffer

PPI-Signal_ Degrade

LP-Signal _Label

LP-Signal _Degrade

LP-FERF

LP-FEBE

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

1-6 Introduction

Alarm consequences
Certain defects result in automatic consequent actions, namely: Injection of a far end receive failure indication (MS-FERF, HP-FERF, or LP-FERF) to the far path/section end. LP-FERF may be discontinued if the path protection switching mechanism re-routes to an alternative valid path. Injection of AIS in the outgoing tributary signal (Trib AIS). Injection of tributary AIS may be discontinued if the path protection switching mechanism re-routes to an alternative valid path. Injection of low-order AIS towards the STM-1 aggregate port(s). The consequent action can be user congured to send either Tx Trib AIS (standard default) or TU AIS (non-standard). When congured to TU AIS, an indication of the local failure is provided at the far path termination. Injection of pass through TU-AIS on TUs that are passed-through the multiplexer. For protected paths, path protection switching to an alternative valid path. Laser shutdown. This is a safety feature, the laser shutdown is latched and the laser remains switched off until the multiplexer is powered-up. Multiplexer restart. The multiplexer restart is performed from the other software bank. Conguration switch. The conguration switch is performed using the other conguration data bank, if available and updated. Otherwise software factory-set defaults are used.

Table 1-1 details the consequence of each trafc alarm.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Introduction 1-7 Table 1-1 Alarm consequences

Consequent Action MS-FERF Alarm Pass-through AU-AIS (see Note 7)

1
1-1

Pass-through TU AIS

HP-FERF

LP-FERF

RS-Loss_of_Signal RS-Loss_of_Frame MS-AIS MS-Excessive_BER AU-AIS INT-AU-AIS INT-AU-LOP HP-TU_Multiframe (see Notes 4 & 5) HP-Path_Trace (see Note 3) HP-Signal-Label (see Note 3) TU-AIS TU-LOP INT-TU _AIS INT-TU_LOP LP-Signal_Label LP-Excessive_BER (see Note 1) PPI_Loss_of_Signal PPI-Unexp_Signal (see Note 2) OS-Optical_Power_High INT-NE-Cong_Corrupt

Tx Trib or TU AIS

Trib AIS

Note 1: LP-Excessive_BER can be user congured not to cause consequent actions (LP-FERF and Trib AIS) and not to cause a path protection switch simultaneously (consequent actions and path protection switch cannot be disabled individually). Note 2: The consequent action is dependent on the conguration of Tx Trib AIS or TU AIS. In case of standard conguration (i.e. Tx Trib AIS), the PPI-Unexp_Signal will not cause any consequent action. In case of non-standard conguration (i.e. TU AIS), the PPI-Unexp_Signal will cause TU AIS injection, overriding the unequipped code.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

Use other cong bank or crash defaults

Path Protection Switch

Laser Shutdown

1-8 Introduction

Note 3: HP-Path_Trace and HP-Signal_Label can be user congured not to cause consequent actions (path protection switch, Trib AIS, HP-FERF and LP-FERF). Note 4: HP-TU_Multiframe causes LP-FERF, Trib AIS and path protection switching for VC-12s and 2 Mbit/s tributaries only, not for VC-3s and 34/45 Mbit/s tributaries. Note 5: HP-TU_Multiframe causes pass-through TU AIS for TU-12s only, not for TU-3s. Note 6: HP-TU_Multiframe monitoring can be disabled by the user. Note 7: Pass-through AU-AIS is only applicable if a VC-4 through connection is made.
0

Beginning fault nding

To locate and clear a fault in the TN-1C system, it is recommended to proceed as follows: Identify the TN-1Cs on which the fault indications are present. This is achieved by: On managed systems, using the TN-MS EC to identify the TN-1C with the highest severity alarms. The TN-MS EC can be used to provide a network level alarm status, this may be used to perform some manual network level alarm correlation in order to isolate the cause of the alarm. On unmanaged systems, using the CAT to identify the TN-1C with the highest severity alarm. If the external output alarm is used to extend the TN-1C alarms to other external equipment, monitor the external equipment for TN-1C alarm conditions. Refer to Chapter 2 for detailed, step-by-step procedures for clearing the alarms. When clearing multiple alarms, you should be aware that one alarm can mask or be masked by others (see Alarm masking on page 1-3).

Responding to logs
TN-1C logs are informational messages that are generated by the TN-1C. Logs can be viewed using the CAT and the TN-MS EC. Often, no action is required on the part of maintenance personnel as a result of log messages. However, some logs are designed to provide supplemental information for certain alarms or trouble-clearing procedure. Copies of the logs may also be useful for Nortel personnel when providing further diagnostic support.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Introduction 1-9

Alarm category and severity

Each alarm instance is assigned an rack alarm category (prompt, deferred, or in-station) for extension to a rack alarm system. The default alarm categories are given in Table 1-2, these can be changed via the user interface. Alarm instances are categorised as Critical, Major, or Minor according to the seriousness of their impact (or potential impact). These categories are pre-set for each alarm instance and cannot be changed. The severity settings are given in Table 1-2. The rack alarm category and alarm severity are included in the TN-1C UI alarm reports. Alarm reports on the Element Controller use only the alarm severity.
Table 1-2 Alarm category and alarm severity settings Alarm PS-Power_Fail PS-Battery_Low INT-NE-SW_Corrupt INT-EC-Alarms_Buffer NE-Door_Open PS-Door_Open INT-NE-RAM_Fail INT-NE-Cong_Corrupt NE-Card_Fail RS-Loss_of_Signal OS-Optical_Power_High OS-Laser_Bias_High INT-RS-Tx_Buffer INT-HP-Insert_Bus RS-Loss_of_Frame RS-Realign_Phase INT-OS-Laser_Test OS-Laser_Shutdown MS-Excessive_BER MS-Signal_Degrade MS-AIS MS-FERF INT-HP-IP_Buffer Qecc-Comms_Fail AU-AIS HP-TU_Multiframe Alarm category Prompt Prompt Prompt Prompt Prompt Prompt Prompt Prompt Prompt Prompt Prompt In-station Prompt Prompt Prompt Prompt In-station In-station Prompt Deferred In-station Deferred Deferred Prompt In-station Deferred
continued

1-2

Alarm severity Critical Critical Critical Critical Critical Critical Critical Critical Critical Critical Critical Minor Critical Critical Critical Critical Minor Minor Critical Major Minor Major Major Critical Minor Major

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

1-10 Introduction Table 1-2 Alarm category and alarm severity settings (continued) Alarm INT-AU-LOP INT-AU-AIS HP-Excessive_BER HP-Signal_Degrade HP-FERF HP-FEBE TU-AIS TU-LOP HP-Path_Trace HP-Signal_Label INT-TU-AIS INT-TU-LOP LP-Excessive_BER LP-Signal_Degrade LP-Signal_Label LP-FERF LP-FEBE INT-LP-OP_Buffer PPI-Output_Fail PPI-Unexp_Signal PPI-Loss_of_Signal PPI-Excessive_BER PPI-Signal_Degrade INT-LP-IP_Buffer EA-Ext_inpn (n=1 to 8) SYNC-Holdover SYNC-SETG_Fail NE-Ext_Card_Out NE-Wrong_Card NE-Unexpected_Card NE-High_Temp NE-Fan_Fail Alarm category Deferred In-station Prompt Deferred Deferred Deferred In-station Deferred Deferred Deferred In-station Deferred Deferred Deferred Deferred Deferred Deferred Deferred Deferred In-station Deferred Deferred Deferred Deferred Prompt Prompt Deferred Prompt Prompt In-station Prompt Deferred
end
End of chapter file

1-2

Alarm severity Major Minor Critical Major Major Major Minor Major Major Major Minor Major Major Major Major Major Major Major Major Minor Major Major Major Major Critical Critical Major Critical Critical Minor Critical Major

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

2-1

Chapter 2: Clearing equipment alarms

This chapter describes how to locate and clear alarms on the TN-1C equipment. The alarm clearing procedures are based on a TN-1C ring system conguration. If the TN-1C is used in other system congurations, the user should refer to the appropriate equipment handbooks for the appropriate alarm clearing procedures whenever references are made to the far multiplexer. Table 2-1 provides a list of alarms and the page where the alarm clearing information can be found. Note: In case where a STM local loopback is performed and passed, it might be helpful to also perform a manual optical loopback (using a bre pigtail) before investigating the problem in the bre.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-2 Clearing equipment alarms Table 2-1 List of alarm clearing procedures Alarm PS-Power_Fail PS-Battery_Low INT-NE-SW_Corrupt INT-EC-Alarms_Buffer NE-Door_Open PS-Door_Open INT-NE-RAM_Fail INT-NE-Cong_Corrupt NE-Card_Fail RS-Loss_of_Signal OS-Optical_Power_High OS-Laser_Bias_High INT-RS-Tx_Buffer INT-HP-Insert_Bus RS-Loss_of_Frame RS-Realign_Phase INT-OS-Laser_Test OS-Laser_Shutdown MS-Excessive_BER MS-Signal_Degrade MS-AIS MS-FERF INT-HP-IP_Buffer Qecc-Comms_Fail AU-AIS HP-TU_Multiframe INT-AU-LOP INT-AU-AIS HP-Excessive_BER HP-Signal_Degrade HP-FERF HP-FEBE TU-AIS
continued

2-1

Page page 2-4 page 2-5 page 2-6 page 2-7 page 2-8 page 2-9 page 2-11 page 2-12 page 2-14 page 2-15 page 2-18 page 2-19 page 2-20 page 2-21 page 2-22 page 2-25 page 2-27 page 2-28 page 2-29 page 2-32 page 2-34 page 2-36 page 2-37 page 2-39 page 2-41 page 2-43 page 2-45 page 2-47 page 2-49 page 2-50 page 2-51 page 2-52 page 2-53

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-3 Table 2-1 List of alarm clearing procedures (continued) Alarm TU-LOP HP-Path_Trace HP-Signal_Label INT-TU-AIS INT-TU-LOP LP-Excessive_BER LP-Signal_Degrade LP-Signal_Label LP-FERF LP-FEBE INT-LP-OP_Buffer PPI-Output_Fail PPI-Unexp_Signal PPI-Loss_of_Signal PPI-Excessive_BER PPI-Signal_Degrade INT-LP-IP_Buffer EA-Ext_inpn SYNC-Holdover SYNC-SETG_Fail NE-Ext_Card_Out NE-Wrong_Card NE-Unexpected_Card NE-Fan_Fail NE-High_Temp
end

2-1

Page page 2-55 page 2-57 page 2-59 page 2-61 page 2-62 page 2-63 page 2-65 page 2-66 page 2-68 page 2-69 page 2-70 page 2-71 page 2-72 page 2-73 page 2-75 page 2-76 page 2-77 page 2-78 page 2-79 page 2-80 page 2-81 page 2-82 page 2-84 page 2-85 page 2-86

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-4 Clearing equipment alarms

PS-Power_Fail
Signicance The a.c. mains supply or the external charger to the TN-1C Power Supply Unit has failed (fallen below set level). Note: This alarm is only applicable when using Nortels TN-1C Power Supply Unit. Impact None immediately. Minimum 3 hours of operation is available from battery backup. Consequent alarms/events None. Possible causes a.c. mains failure.
0

a.c. fuse blown. Input connector not properly connected. Faulty TN-1C Power Supply Unit.

Corrective action Perform the alarm clearing procedures detailed in Procedure 2-1.
Procedure 2-1 PS-Power_Fail alarm clearing Step 1 Action Check that the a.c. mains connector is properly connected. Re-connect the connector if required. If alarm still present, proceed to Step 2. Check a.c. fuse, replace if blown.

2-1

If fuse blows again, proceed to Step 4.

3 Verify that the a.c. mains supply is present.

If the a.c. mains supply is not present, investigate loss. If the a.c. mains supply is present, proceed to Step 4.
4 Replace the TN-1C Power Supply Unit. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-5

PS-Battery_Low
Signicance The battery voltage has dropped below 21 V 0.5 V, indicating that only a few minutes of operation remain. Note: This alarm is only applicable when using Nortels TN-1C Power Supply Unit. Impact Imminent trafc loss. Consequent alarms/events None. Possible causes a.c. mains failure.
0

Input connector not properly connected. Faulty power unit.

Corrective action Perform the alarm clearing procedures detailed in Procedure 2-2.
Procedure 2-2 PS-Battery_Low alarm clearing Step 1 Action Check if a PS-Power_Fail alarm is present.

2-2

If a PS-Power_Fail alarm is present, perform the alarm clearing procedure for the PS-Power_Fail alarm. If a PS-Power_Fail alarm is not present, proceed to Step 2.
2 Replace the TN-1C Power Supply Unit batteries.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-6 Clearing equipment alarms

INT-NE-SW_Corrupt
Signicance The checksum of the application code is incorrect. Impact None. Consequent alarms/events None. Possible causes Download failure.
0

Spurious software corruption.

Corrective action Copy the current good software bank to the corrupted bank using the TN-1C UI (see Software Administration Procedures, NTP 323-1081-303).

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-7

INT-EC-Alarms_Buffer
Signicance The alarm report buffer used for transferring alarm messages to the network management system has overloaded. All current alarm messages in the buffer are removed and an appropriate message is sent to the network management system, which will then request an active alarms report. Impact Non-trafc affecting. Consequent alarms/events None. Possible causes Excessive alarm activity on network.
0

If single occurrence, probably major network disturbance. If persistent, internal fault.

Corrective actions Investigate network for major disturbance. Investigate local multiplexer for excessive alarm activity. Align network management system alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-8 Clearing equipment alarms

NE-Door_Open
Signicance The cover on the TN-1C multiplexer unit has been removed. Note: The alarm remains active for approximately 5 minutes once the cover is tted. Impact None. Consequent alarms/events None. Possible causes TN-1C cover removed or not correctly tted. Tab broken on plastic cover. Faulty microswitch.

Corrective actions If cover removal unauthorised (i.e. no known maintenance activities), or alarm is not cleared within 5 minutes of door closure, perform the alarm clearing procedure given in Procedure 2-3.
Procedure 2-3 NE-Door_Open alarm clearing Step 1 Action Check that plastic tab is not broken on plastic cover and that the cover is properly tted.

2-3

If the cover is not correctly tted, ret the cover. If the plastic tab is broken, replace the plastic cover. If alarm is still present, proceed to Step 2.
2 Check that the microswitch lever is not damaged.

If microswitch is damaged, replace the TN-1C multiplexer. If microswitch is not damaged, escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-9

PS-Door_Open
Signicance The cover on the TN-1C Power Supply Unit (PSU) has been removed. Note 1: The alarm remains active for approximately 5 minutes once the cover is tted. Note 2: On the 16x2 Mbit/s versions of the TN-1C, the alarm will not be raised if the PS-Door_Open jumper is shorted. Impact None. Consequent alarms/events None. Possible causes TN-1C PSU cover removed or not correctly tted. Tab broken on plastic cover. Faulty microswitch.

Corrective actions Note: If the Nortel PSU is not being used, check that the alarm is disabled on the TN-1C (i.e. pins 4 and 9 linked on the power connector). If cover removal unauthorised (i.e. no known maintenance activities), or alarm is not cleared within 5 minutes of door closure, perform the alarm clearing procedure given in Procedure 2-4.
Procedure 2-4 PS-Door_Open alarm clearing Step 1 Action Check that plastic tab is not broken on plastic cover and that the cover is properly tted.

2-4

If the cover is not correctly tted, ret the cover. If the plastic tab is broken, replace the plastic cover. If alarm is still present, proceed to Step 2.
2 Check that the microswitch lever is not damaged.

If microswitch is damaged, replace the PSU. If microswitch is not damaged, proceed to Step 3.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-10 Clearing equipment alarms Procedure 2-4 PS-Door_Open alarm clearing Step 3 Action Replace the d.c./alarm cable between the TN-1C and the PSU.

2-4

If the alarm clears, no further action is required. If alarm is still present, replace the PSU.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-11

INT-NE-RAM_Fail
Signicance Failure of the on-board RAM during self-tests which are performed on initialisation and subsequently at regular intervals (approximately every 30 seconds). Impact Small risk of being trafc affecting. Consequent alarms/events None. Possible causes RAM failure on TN-1C multiplexer. Corrective action Replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-12 Clearing equipment alarms

INT-NE-Cong_Corrupt
Signicance The periodic checksum test on the conguration data held in the non-volatile memory has failed. Impact If alternate conguration bank not available, possibly trafc affecting. Consequent alarms/events If other conguration data bank is available and has been updated, a switch is made to the alternate conguration bank. If alternate conguration data bank not available, factory-set defaults are used. Possible causes Non-volatile store corrupt. Corrective actions Perform the alarm clearing procedure given in Procedure 2-5.
Procedure 2-5 INT-NE-Cong_Corrupt alarm clearing Step 1 Action Use the UI to view the conguration bank status.

2-5

If both banks contain the latest correct conguration and the multiplexer is operating correctly, no further action is required. If only one conguration bank contains the correct conguration, proceed to Step 2. If the multiplexer is operating from its default settings, proceed to Step 3. If the alarm is persistent, replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
2 Use the UI to commit the conguration to the other bank (see System Administration Procedures, NTP 323-1081-302). If the commit process fails, replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
continued

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-13 Procedure 2-5 INT-NE-Cong_Corrupt alarm clearing (continued) Step 3 Action If a backup conguration is available, download and switch to backup conguration using the UI. If the backup conguration is acceptable, commit the conguration to the other bank. For details of the UI procedures, refer to System Administration Procedures NTP, 323-1081-302. If the download, restore or commit process fails, replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

2-5

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-14 Clearing equipment alarms

NE-Card_Fail
Signicance Failure of the on-board ASIC tests or any other hardware tests which are performed on initialisation and subsequently at regular intervals (approximately every 30 seconds). Impact May be trafc affecting, depending on the type of failure. Consequent alarms/events None. Possible causes Failure of the one of the on-board ASICs.
0

Hardware checksum failure. Phase-Locked Loop problems.

Corrective actions If the alarm is reported for instance S0 (connector panel), replace TN-1C EMC enclosure. If the alarm is reported for instance S1 (main TN-1C ADM card), replace main TN-1C ADM card. If the alarm is reported for instance S2 (tributary extension card), replace tributary extension card. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-15

RS-Loss_of_Signal
Signicance The incoming optical signal has failed or fallen below the threshold level, causing the clock recovery circuit to lose lock, or an all-zeros pattern has been detected for at least 6.5 s 1 s. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs. Laser shutdown.

HP source MS-FERF and HP-FERF alarms.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing RS-Loss_of_Signal alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-16 Clearing equipment alarms

Possible causes Fibre break/bad termination.

0

Transmitter failure at far TN-1C multiplexer. Receiver failure on local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-6.
Procedure 2-6 RS-Loss_of_Signal alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures). Use the UI to issue a laser restart command.

2-6

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
3 Clean the receive optical connections at the local TN-1C multiplexer and verify that the received optical power is in the correct range (see Chapter 3, Common Procedures).

If the received optical power is within range, proceed to Step 4. If the received optical power is not within range, proceed to Step 5.
4 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, the alarm clearing procedures are complete.
continued

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-17 Procedure 2-6 RS-Loss_of_Signal alarm clearing (continued) Step 5 Action Clean the transmit optical connections at the far TN-1C multiplexer and verify that the transmit optical power at the far TN-1C multiplexer is in the correct range (see Chapter 3, Common Procedures).

2-6

If the transmit optical power is within range, the fault is associated with the optical bre. Use appropriate methods to isolate bre fault. If the transmit optical power is not within range, proceed to Step 6.
6 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-18 Clearing equipment alarms

OS-Optical_Power_High
Signicance The optical output power has exceeded the nominal output level by more than 4 dB, or has exceeded +4 dBm within 600 ms. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Laser shutdown. This is a safety feature, although the laser output is still within the standard safe range. Note: The laser shutdown is latched, the laser will remain off until the multiplexer is powered-up. Possible causes Faulty TN-1C transmit circuit. Corrective actions Replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-19

OS-Laser_Bias_High
Signicance The laser bias current is out-of-limits. Indicates that the laser performance has degraded and that the laser end-of-life is near. Impact Non-trafc affecting. Note: The alarm indicates that a maintenance action is needed, otherwise an Optical Source Low Power condition will occur, which is service affecting. Consequent alarms/events None. Possible causes Aging of laser. Corrective actions Replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-20 Clearing equipment alarms

INT-RS-Tx_Buffer
Signicance The DSPI FIFO in the mapping/multiplexing direction is either in the underow or overow state. Impact Trafc affecting. Consequent alarms/events None. Possible causes Faulty local TN-1C multiplexer. Corrective actions If alarm is persistent, replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-21

INT-HP-Insert_Bus
Signicance The payload data in the mapping/multiplexing direction is errored. The alarm is raised if the AU pointer values are errored in at least eight consecutive frames. Impact Trafc affecting. Consequent alarms/events None. Possible causes Faulty local TN-1C multiplexer. Corrective actions Replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-22 Clearing equipment alarms

RS-Loss_of_Frame
Signicance The frame alignment algorithm has detected loss of frame alignment (loss of framing pattern in the A1 and A2 bytes of the section overhead for three consecutive frames). Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source MS-FERF and HP-FERF alarms.

0

LP path termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing RS-Loss_of_Frame alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-23

Possible causes Invalid incoming STM-1 signal.

0

Faulty local or remote TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-7.
Procedure 2-7 RS-Loss_of_Frame alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2
2-7

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
3 Perform a Local loopback on the appropriate aggregate at the far TN-1C multiplexer (see Chapter 3, Common Procedures).

If a RS-Loss_of_Frame alarm is present at the far multiplexer, remove the Local loopback and replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If a RS-Loss_of_Frame alarm is not present at the far multiplexer, remove the Local loopback and proceed to Step 4.
4 Clean the receive optical connections at the local TN-1C multiplexer and verify that the received optical power is in the correct range (see Chapter 3, Common Procedures).

If the received optical power is within range, proceed to Step 5. If the received optical power is not within range, proceed to Step 6.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-24 Clearing equipment alarms Procedure 2-7 RS-Loss_of_Frame alarm clearing Step 5 Action Clean the transmit optical connections at the far TN-1C multiplexer and verify that the transmit optical power at the far TN-1C multiplexer is in the correct range (see Chapter 3, Common Procedures).

2-7

If the transmit optical power is within range, the fault is associated with the optical bre. Use appropriate methods to isolate bre fault. If the transmit optical power is not within range, proceed to Step 6.
6 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-25

RS-Realign_Phase
Signicance The STM-1 processor has realigned to a new phase without going out of frame alignment. Impact Possible trafc hit. Consequent alarms/events None. Possible causes Faulty local or remote TN-1C multiplexer. Corrective actions If the alarm is persistent, perform the alarm clearing procedure given in Procedure 2-8.
Procedure 2-8 STM-Realign_Phase alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback at the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2-8

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 6.
3 Perform a Local loopback on the appropriate aggregate at the far TN-1C multiplexer (see Chapter 3, Common Procedures).

If a RS-Realign_Phase alarm is present at the far multiplexer, remove the Local loopback and replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If a RS-Realign_Phase alarm is not present at the far multiplexer, remove the Local loopback and proceed to Step 4.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-26 Clearing equipment alarms Procedure 2-8 STM-Realign_Phase alarm clearing Step 4 Action Clean the receive optical connections at the local TN-1C multiplexer and verify that the received optical power is in the correct range (see Chapter 3, Common Procedures).

2-8

If the received optical power is within range, proceed to Step 5. If the received optical power is not within range, proceed to Step 6.
5 Clean the transmit optical connections at the far TN-1C multiplexer and verify that the transmit optical power at the far TN-1C multiplexer is in the correct range (see Chapter 3, Common Procedures).

If the transmit optical power is within range, the fault is associated with the optical bre. Use appropriate methods to isolate bre fault. If the transmit optical power is not within range, proceed to Step 6.
6 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-27

INT-OS-Laser_Test
Signicance The automatic laser shutdown (ALS) circuit has been disabled. Impact None. Consequent alarms/events None. Possible causes Laser forced_on from the TN-1C UI. Corrective actions Re-enable ALS by setting laser to normal operation from the UI (see User Interface Guide, NTP 323-1081-401). If the alarm is still present, replace the TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-28 Clearing equipment alarms

OS-Laser_Shutdown
Signicance The laser has been shutdown by the automatic laser shutdown (ALS) circuit or by OS-Optical_Power_High alarm. Note: The OS-Laser_Shutdown alarm remains active during the laser restart pulses (part of the ALS mechanism). Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events If shutdown by a RS-Loss_of_Signal alarm, automatic laser shutdown mechanism initiated. Laser restart attempted every 70 seconds until RS-Loss_of_Signal alarm is cleared. If shutdown due to an OS-Optical_Power_High alarm, the laser shutdown is latched and the laser will remain off until the multiplexer is powered-up.

Possible causes RS-Loss_of_Signal or OS-Optical_Power_High alarm. Corrective actions Send a laser restart command using the UI. If alarm is still present, investigate cause of RS-Loss_of_Signal or OS-Optical_Power_High alarm.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-29

MS-Excessive_BER
Signicance Impact
0

The BER of the BIP-24 error check has exceeded 10-3. Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source MS-FERF and HP-FERF alarms.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing MS-Excessive_BER alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-30 Clearing equipment alarms

Possible causes Faulty optical bre/connections.

0

Faulty local TN-1C multiplexer. Faulty far end TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-9.
Procedure 2-9 MS-Excessive_BER alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2-9

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
3 Clean the receive optical connections at the local TN-1C multiplexer and verify that the received optical power is in the correct range (see Chapter 3, Common Procedures).

If the received optical power is within range, proceed to Step 4. If the received optical power is not within range, proceed to Step 6.
4 Apply a manual (external) optical loopback at the local multiplexer.

If the alarm is still present, proceed to Step 5. If the alarm clears, proceed to Step 7.
5 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the external optical loopback.The alarm clearing procedures are complete.
continued

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-31 Procedure 2-9 MS-Excessive_BER alarm clearing (continued) Step 6 Action Clean the transmit optical connection at the far TN-1C multiplexer and verify that the transmit optical power at the far multiplexer is in the correct range (see Chapter 3, Common Procedures).

2-9

If the transmit optical power is within range, the fault is associated with the optical bre. Use appropriate methods to isolate bre fault. If the transmit optical power is not within range, proceed to Step 7.
7 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-32 Clearing equipment alarms

MS-Signal_Degrade
Signicance The BER of the BIP-24 error check has exceeded the congurable lower threshold (10-5, 10-6, or 10-7, default 10-5). Impact Trafc affecting. Consequent alarms/events Local Possible intermittent HP-Signal_Degrade and LP-Signal_Degrade alarms. HP source Possible intermittent HP-FEBE alarms. LP source Possible intermittent LP-FEBE alarms. Possible causes Faulty optical bre/connections.
0

Faulty local TN-1C multiplexer. Faulty far end TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-10.
Procedure 2-10 MS-Signal_Degrade alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2-10

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
continued

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-33 Procedure 2-10 MS-Signal_Degrade alarm clearing (continued) Step 3 Action Clean the receive optical connections at the local TN-1C multiplexer and verify that the received optical power is in the correct range (see Chapter 3, Common Procedures).

2-10

If the received optical power is within range, proceed to Step 4. If the received optical power is not within range, proceed to Step 6.
4 Apply a manual (external) optical loopback at the local multiplexer.

If the alarm is still present, proceed to Step 5. If the alarm clears, proceed to Step 7.
5 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the external optical loopback. The alarm clearing procedures are complete.
6 Clean the transmit optical connection at the far TN-1C multiplexer and verify that the transmit optical power at the far multiplexer is in the correct range (see Chapter 3, Common Procedures).

If the transmit optical power is within range, the fault is associated with the optical bre. Use appropriate methods to isolate bre fault. If the transmit optical power is not within range, proceed to Step 7.
7 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-34 Clearing equipment alarms

MS-AIS
Signicance An AIS has been detected in the K2 byte in the section overhead indicating a failure at the far multiplexer. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source MS-FERF and HP-FERF alarms.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP path containing MS-AIS alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-35

Possible causes MS AIS generated at far multiplexer or by a regenerator in between (if applicable). Note: MS AIS is not intentionally generated by the TN-1C multiplexer and should not be raised in a TN-1C to TN-1C system. Corrective actions Perform the alarm clearing procedure given in Procedure 2-11.
Procedure 2-11 MS-AIS alarm clearing Step 1 Action Check far multiplexer and any intermediate regenerators for cause of AIS.

2-11

If cause of AIS found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
2 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-36 Clearing equipment alarms

MS-FERF
Signicance A FERF indication has been detected in the K2 bytes of the section overhead, indicating that the far multiplexer has detected a fault in the incoming signal. Impact None. Consequent alarms/events None. Possible causes RS-Loss_of_Signal, RS-Loss_of_Frame, MS-AIS, or MS-Excessive_BER alarm at the far multiplexer. Corrective actions Perform the alarm clearing procedure given in Procedure 2-12.
Procedure 2-12 MS-FERF alarm clearing Step 1 Action Check far multiplexer for cause of alarm (RS-Loss_of_Signal, RS-Loss_of_Frame, MS-AIS, or MS-Excessive_BER alarm).

2-12

If cause of alarm found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
2 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-37

INT-HP-IP_Buffer
Signicance The AU FIFO buffer, which allows the incoming STM-1 signal to be aligned to the local frame, has underowed or overowed. Impact Trafc affecting. Consequent alarms/events None. Note: If the alarm persists, protected paths may switch due to HP and LP defects. Possible causes Synchronisation problems in network.
0

Incoming STM-1 signal out-of-limits. Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-13.
Procedure 2-13 INT-HP-IP_Buffer alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Isolate the TN-1C from the synchronisation perspective (i.e. remove all external source from the hierarchy so that the TN-1C is operating in the holdover mode).

2-13

If the alarm clears, investigate the network for possible synchronisation loops. If the alarm is still present, return the synchronisation hierarchy to the previous settings and proceed to Step 3.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-38 Clearing equipment alarms Procedure 2-13 INT-HP-IP_Buffer alarm clearing (continued) Step 3 Action Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2-13

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original local TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 4.
4 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-39

Qecc-Comms_Fail
Signicance Communication over the Embedded Control Channel (ECC) has been lost with the adjacent multiplexer on a specic STM-1 link. Impact Non-trafc affecting. Inter-site data communications are unavailable.

Consequent alarms/events None. Possible causes Faulty local or far end TN-1C multiplexer. Remote or local aggregate loopback on the local or far end multiplexer. If alarm is temporary, cold or warm restart on the local or far TN-1C multiplexer.

Corrective actions If the alarm is persistent, perform the alarm clearing procedure given in Procedure 2-14.
Procedure 2-14 Qecc-Comms_Fail alarm clearing Step 1 Action Disable faulty link at the local TN-1C by disconnecting optical bres and then reconnecting them.

2-14

If alarm clears, report occurrence (no other action is required). If alarm is still present, proceed to Step 2.
2 Reboot the software using a cold restart from the UI.

If alarm clears, report occurrence (no other action is required). If alarm is still present, proceed to Step 3.
3 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If alarm still present, replace the original local TN-1C multiplexer and proceed to Step 4. If the alarm clears, the alarm clearing procedures are complete.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-40 Clearing equipment alarms Procedure 2-14 Qecc-Comms_Fail alarm clearing (continued) Step 4 Action Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

2-14

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-41

AU-AIS
Signicance An AIS has been detected in the H1 and H2 bytes indicating a failure in the upstream path. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source HP-FERF alarm.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing AU-AIS alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP path source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-42 Clearing equipment alarms

Possible causes AU AIS being generated by far multiplexer. Note: AU AIS is not intentionally generated by the TN-1C multiplexer and should not be raised in a TN-1C to TN-1C system.
0

Corrective actions Perform the alarm clearing procedure given in Procedure 2-15.
Procedure 2-15 AU-AIS alarm clearing Step 1 Action Check far multiplexer and any intermediate regenerators for cause of AIS.

2-15

If cause of AIS found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
2 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-43

HP-TU_Multiframe
Signicance An illegal multiframe sequence has been detected in the H4 byte. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Note: When the TN-1C is used in a VC-3 only ring, the HP-TU_Multiframe alarm is not applicable and should be disabled using the UI (see User Interface Guide, NTP 323-1081-401). Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP path containing HP-TU_Multiframe alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-44 Clearing equipment alarms

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

Possible causes Line errors.

0

Faulty local TN-1C multiplexer. Faulty far end TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-16.
Procedure 2-16 HP-TU_Multiframe alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback at the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2-16

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
3 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-45

INT-AU-LOP
Signicance The internal pointer value in the H1 and H2 bytes in the AU pointer has been invalid (i.e. an invalid New Data Flag or size bits) for three consecutive frames. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source HP-FERF alarm.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP path containing INT-AU-LOP alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-46 Clearing equipment alarms

Possible causes Faulty local TN-1C multiplexer. Corrective actions Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original local TN-1C multiplexer and escalate the problem.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-47

INT-AU-AIS
Signicance An internal AIS has been detected internally in the H1 and H2 bytes for three consecutive frames. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source HP-FERF alarm.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP path containing INT-AU-AIS alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

Possible causes Faulty local TN-1C multiplexer.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-48 Clearing equipment alarms

Corrective actions Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original local TN-1C multiplexer and escalate the problem.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-49

HP-Excessive_BER
Signicance Impact Trafc affecting. Consequent alarms/events HP source HP-FEBE alarm. LP source Possible LP-FEBE alarms. Possible causes Faulty local TN-1C multiplexer. Faulty far end TN-1C multiplexer. Corrective actions Perform the alarm clearing procedure given in Procedure 2-17.
Procedure 2-17 HP-Excessive_BER alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

The BER of the VC-4 path (B3) BIP-8 error check has exceeded 10-3.

2-17

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
3 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer. If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-50 Clearing equipment alarms

HP-Signal_Degrade
Signicance The BER of the VC-4 path (B3) BIP-8 error check has exceeded the congurable lower threshold (10-5, 10-6, or 10-7, default 10-5). Impact Trafc affecting. Consequent alarms/events Local Possible LP-Signal_Degrade alarms. HP source Possible HP-FEBE alarm. LP source Possible LP-FEBE alarms. Possible causes Faulty local TN-1C multiplexer. Faulty far end TN-1C multiplexer. Corrective actions Perform the alarm clearing procedure given in Procedure 2-18.
Procedure 2-18 HP-Signal_Degrade alarm clearing Step 1 2 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the local TN-1C multiplexer (see Chapter 3, Common Procedures).

2-18

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 3.
3 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer. If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-51

HP-FERF
Signicance The VC-4 Path FERF bit in the VC-4 path status byte (G1) has been set indicating that the HP origin has detected a fault in the incoming HP. Impact None. Consequent alarms/events None. Possible causes INT-AU-AIS, HP-Excessive_BER, or INT-AU-LOP alarm at the far multiplexer. Corrective actions Perform the alarm clearing procedure given in Procedure 2-19.
Procedure 2-19 HP-FERF alarm clearing Step 1 Action Check far multiplexer for cause of alarm (AU-AIS, INT-AU-AIS, INT-AU-LOP, or HP-TU_Multiframe alarm).

2-19

If cause of alarm found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
2 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-52 Clearing equipment alarms

HP-FEBE
Signicance The BER of the FEBE bits in the VC-4 path status byte (G1), indicating that the far multiplexer has detected errors in the VC-4 path, has exceeded the congurable threshold of 10-5, 10-6, or 10-7 (default 10-5). Impact None. Consequent alarms/events None. Possible causes HP errors on the network. Corrective actions Perform the alarm clearing procedure given in Procedure 2-20.
Procedure 2-20 HP-FEBE alarm clearing Step 1 Action Check far HP path termination for cause of errors (e.g. HP-Signal_Degrade or HP-Excessive_BER alarm) and carry out fault nding procedures for appropriate alarm.

2-20

If cause of errors found, perform the appropriate alarm clearing procedure. If cause of errors not found, proceed to Step 2.
2 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-53

TU-AIS
Signicance An AIS has been detected in the pointer bytes of the TU. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Protected add/drop TU path Temporary AIS injection on associated tributary output if switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU path AIS injection on associated tributary output.

LP source Protected add/drop TU path LP-FERF alarm if both paths have failed at local multiplexer.
0

Unprotected add/drop TU path LP-FERF alarm.

Possible causes TU AIS being generated by another multiplexer on the network. Corrective actions Perform the alarm clearing procedure given in Procedure 2-21.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-54 Clearing equipment alarms Procedure 2-21 TU-AIS alarm clearing Step 1 Action Is trafc expected on the indicated channel.

2-21

If trafc is expected, proceed to Step 2. If trafc is not expected, use the UI to set the channel to Trafc Off (this will disable the alarm).
2 Investigate network (LP path source and intermediate locations) for cause of AIS (e.g. PPI-Loss_of_Signal or PPI-Unexp_Signal alarm at far multiplexer or alarms that cause pass-through TU-AIS injection).

If cause of AIS found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
3 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-55

TU-LOP
Signicance The pointer value in the pointer bytes of the TU is invalid for three consecutive frames. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths if paths switched to aggregate containing alarm.

Consequent alarms/events Local Through path TU-AIS injection on associated TU. Protected add/drop TU path Temporary AIS injection on associated tributary output if switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU path AIS injection on associated tributary output.

LP termination Protected add/drop TU path TU-AIS alarm. If TU switched to HP containing TU-LOP alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths TU-AIS alarms.

LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer.
0

Unprotected add/drop TU paths LP-FERF alarms.

Possible causes Faulty local TN-1C multiplexer. Faulty far TN-1C multiplexer. Incorrect connection settings (e.g. VC-3 against a VC-12 connection).

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-56 Clearing equipment alarms

Corrective actions Perform the alarm clearing procedure given in Procedure 2-22.
Procedure 2-22 TU-LOP alarm clearing Step 1 Action If the route is protected, ensure that the trafc is switched to the other aggregate port. Check that the correct network connection settings have been made.

2-22

If network connection settings are incorrect, correct as necessary. If network connection settings are correct, proceed to Step 3.
3 If the route is protected, ensure that the trafc is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C multiplexer (see Chapter 3, Common Procedures).

If the alarm is still present, remove the Local loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to Step 4.
4 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer. If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-57

HP-Path_Trace
Signicance The received string of the VC-4 path trace byte (J1) does not match the expected string. Impact Trafc affecting if incorrect connection (wrong trafc). Consequent alarms/events Note: Consequent actions for the HP-Path_Trace alarm can be disabled using the UI (see User Interface Guide, NTP 323-1081-401). The default is for the consequent actions to be disabled. Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source HP-FERF alarm.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP path containing HP-Path_Trace alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-FERF alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-58 Clearing equipment alarms

Possible causes Incorrect connection setup.

0

Settings incorrectly set during conguration (i.e. receive string or far end transmit string). Fibre break if operating in the Single Fibre Working mode. Faulty local or far TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-24.
Procedure 2-23 HP-Path_Trace alarm clearing Step 1 Action If operating in the Single Fibre Working mode, check for bre breaks (i.e. output signal is being reected back to the input of the same TN-1C.

2-23

If bre break detected, perform appropriate actions to repair bre. If no bre break detected, proceed to Step 2.
2 Check that the correct optical connections have been made.

If the optical connections are incorrect, reconnect as required. If the optical connections are correct, proceed to Step 2.
3 Check the system path trace settings at both ends.

If settings are incorrect, recongure as necessary. If settings are correct, proceed to Step 3.
4 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm clears, the alarm clearing procedures are complete. If the alarm is still present, replace the original local TN-1C multiplexer and proceed to Step 4.
5 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-59

HP-Signal_Label
Signicance The value of the signal label code in the C2 byte of the VC-4 does not correspond with the expected value (a value of 1 and 2 is expected). Impact Trafc affecting if incorrect connection (wrong trafc). Consequent alarms/events Note: Consequent actions for the HP-Signal_Label alarm can be disabled using the UI (see User Interface Guide, NTP 323-1081-401). The default is for the consequent actions to be disabled. Local Through paths TU-AIS injection on all through paths. Protected add/drop TU paths Temporary AIS injection on tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid).
0

Unprotected add/drop TU paths AIS injection on all tributary outputs.

HP source HP-FERF alarm.

0

LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing HP-Signal_Label alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-FERF alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-FERF alarms.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-60 Clearing equipment alarms

Possible causes Incorrect connection setup.

0

Settings incorrectly set during conguration (the settings for the TN-1C are not congurable). Faulty local or far TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-24.
Procedure 2-24 HP-Signal_Label alarm clearing Step 1 Action Check that the correct optical connections have been made.

2-24

If the optical connections are incorrect, reconnect as required. If the optical connections are correct, proceed to Step 2.
2 If applicable, check the far end HP signal label settings.

If settings are incorrect, recongure as necessary. If settings are correct, proceed to Step 3.
3 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm clears, the alarm clearing procedures are complete. If the alarm is still present, replace the original local TN-1C multiplexer and proceed to Step 4.
4 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-61

INT-TU-AIS
Signicance An internal AIS has been detected internally in the pointer bytes of the TU. Impact Trafc affecting. Consequent alarms/events Local AIS injection on associated tributary output. LP source LP-FERF alarm. Possible causes Faulty local TN-1C multiplexer. Corrective actions Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If alarm still present, replace original local TN-1C multiplexer and escalate problem.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-62 Clearing equipment alarms

INT-TU-LOP
Signicance The internal pointer value in the pointer bytes of the TU is invalid for three consecutive frames. Impact Trafc affecting. Consequent alarms/events Local AIS injection on associated tributary output. LP source LP-FERF alarm. Possible causes Faulty local TN-1C multiplexer. Corrective actions Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If alarm still present, replace original local TN-1C multiplexer and escalate problem.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-63

LP-Excessive_BER
Signicance The BER of the BIP-2 (VC-12) or BIP-8 (VC-3) error check has exceeded 10-3. Impact
0

Trafc affecting on unprotected paths. Temporary trafc hit on protected paths.

Consequent alarms/events Local Protected add/drop TU path Temporary AIS injection on tributary output if protection switching enabled as a consequent action of an LP-Excessive_BER alarm and path switched to aggregate containing alarm. Protection switch to other aggregate (if valid) if protection switching enabled as a consequent action of an LP-Excessive_BER alarm. AIS injection on tributary output if LP-Excessive_BER is congured to cause consequent actions and protection switching and LP-Excessive_BER is received on both paths. Note: If LP-Excessive_BER is received from both paths, path protection switching will be performed every oscillation-guard_time (an event message about path protection switching will only be issued after the rst switch). Unprotected add/drop TU path AIS injection on associated tributary output if LP-Excessive_BER congured to cause consequent actions.
0

Path source Protected TU path LP-FERF alarm if both paths have failed at local multiplexer. LP-FEBE alarm if LP-Excessive_BER is congured not to cause consequent actions. Unprotected TU path LP-FERF alarm if LP-Excessive_BER congured to cause consequent actions. LP-FEBE alarm if LP-Excessive_BER is congured not to cause consequent actions. Note: LP-FERF as a consequent action of LP-Excessive_BER is congurable by the user (default on).

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-64 Clearing equipment alarms

Possible causes Errors on network. Faulty local TN-1C multiplexer. Faulty far TN-1C multiplexer.

Corrective actions Perform the fault nding procedure given in Procedure 2-25.
Procedure 2-25 LP-Excessive_BER alarm clearing Step 1 Action Check if there are any MS or HP alarms in the network.

2-25

If there are MS or HP alarms in the network, perform recommended actions to clear alarm. If there are no MS or HP alarms in the network, proceed to Step 2.
2 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original TN-1C multiplexer and replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-65

LP-Signal_Degrade
Signicance The BER of the BIP-2 error check has exceeded the lower congurable threshold: Impact Trafc affecting. Consequent alarms/events Path source Possible LP-FEBE alarm (LP-FEBE alarm is not congurable to 10-3 (only 10-4 and 10-5). Possible causes Errors in network.
0

10-4 or 10-5 (default 10-5) for VC-12 10-5 or 10-6 or 10-7 (default 10-5) for VC-3.

Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-26.
Procedure 2-26 LP-Signal_Degrade alarm clearing Step 1 Action Check if there are any MS or HP alarms in the network.

2-26

If there are MS or HP alarms in the network, perform recommended actions to clear alarm. If there are no MS or HP alarms in the network, proceed to Step 2.
2 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original TN-1C multiplexer and replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-66 Clearing equipment alarms

LP-Signal_Label
Signicance The value of the signal label bits in the V5 byte (VC-12) or C2 byte (VC-3) does not correspond with the expected value as follows: Impact Trafc affecting. Consequent alarms/events Local AIS injection on tributary output. LP source LP-FERF alarm. Possible causes Incorrect trafc settings.
0

for VC-12s a value of 1 or 2 is expected if the trafc is on, a value of 0 is expected if the trafc is off. for VC-3s a value of 1 or 4 is expected if the trafc is on, a value of 0 is expected if the trafc is off.

Incorrect path connection. Faulty local or far TN-1C multiplexer.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-67

Corrective actions Perform the alarm clearing procedure given in Procedure 2-27.
Procedure 2-27 LP_Signal_Label alarm clearing Step 1 Action Ensure that the system path conguration at both ends is correct as follows: VC-12s - if no trafc expected, both ends should be congured to send a value of 0 (trafc-off). - if trafc is expected, both ends should be congured to send a value of 1 or 2 (trafc-on). VC-3s - if no trafc expected, both ends should be congured to send a value of 0 (trafc-off). - if trafc is expected, both ends should be congured to send a value of 1 or 4 (trafc-on). If the settings are not correct, proceed to Step 2. 2 3 Verify that the path is correctly connected at all intermediate multiplexers. Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

2-27

If the alarm clears, the alarm clearing procedures are complete. If the alarm is still present, proceed to Step 3.
4 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer. If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-68 Clearing equipment alarms

LP-FERF
Signicance The VC-12/VC-3 path FERF bit in the incoming VC-12/VC-3 has been set, indicating that a fault has been detected in the receive LP path at the far path termination. Impact None. Consequent alarms/events None. Possible causes If alarm raised for all tributaries, RS-Loss_of_Signal, RS-Loss_of_Frame, MS-AIS, MS-Excessive_BER, AU-AIS, INT-AU-AIS, INT-AU-LOP, HP-Path_Trace, HP-Signal_Label or HP-TU_Multiframe alarm at the far multiplexer. If alarm raised for one tributary only, TU-AIS, TU-LOP, INT-TU-AIS, INT-TU-LOP, LP-Signal_Label or LP-Excessive_BER alarm present at far path termination.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-28.
Procedure 2-28 LP-FERF alarm clearing Step 1 Action Investigate far multiplexer/path termination for cause of alarm and carry out fault nding procedures for appropriate alarm.

2-28

If cause of alarm found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
2 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm clears, the alarm clearing procedures are complete. If the alarm is still present, proceed to Step 3.
3 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer. If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-69

LP-FEBE
Signicance The BER of the FEBE bits in the V5 byte of the incoming VC-12, indicating that the far station has detected errors in the VC-12 path, has exceeded the congurable threshold of 10-3, 10-4, or 10-5 (default 10-5). Impact None. Consequent alarms/events None. Possible causes TU errors on network. Corrective actions Perform the alarm clearing procedure given in Procedure 2-29.
Procedure 2-29 LP-FEBE alarm clearing Step 1 Action Investigate far path termination for cause of errors and carry out fault nding procedures for appropriate alarm (e.g. LP-Signal_Degrade alarm).

2-29

If cause of alarm found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to Step 2.
2 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm clears, the alarm clearing procedures are complete. If the alarm is still present, proceed to Step 3.
3 Replace the far TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original far TN-1C multiplexer. If the alarm is still present, replace the original far TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-70 Clearing equipment alarms

INT-LP-OP_Buffer
Signicance The FIFO in the demapping/demultiplexing direction is either in the underow or overow state. Impact Trafc affecting. Consequent alarms/events None. Possible causes Synchronisation problems in network.
0

Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-30.
Procedure 2-30 INT-LP-OP_Buffer alarm clearing Step 1 Action Isolate the TN-1C from the synchronisation perspective (i.e. remove all external sources from the hierarchy so that the TN-1C is operating in the holdover mode).

2-30

If the alarm clears, investigate the network for possible synchronisation loops. If the alarm is still present, return the synchronisation hierarchy to the previous settings and proceed to Step 2.
2 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original local TN-1C multiplexer and escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-71

PPI-Output_Fail
Signicance The output tributary signal has fallen below a predened threshold. Impact Loss of 2 Mbit/s or 34/45 Mbit/s trafc output. Consequent alarms/events None. Possible causes Faulty local TN-1C multiplexer. Corrective actions Perform the alarm clearing procedures given in Procedure 2-31.
Procedure 2-31 PPI-Output_Fail alarm clearing Step 1 Action Ensure that the 2 Mbit/s or 34/45 Mbit/s trafc output cable is properly connected. Re-connect the connector if required. If the alarm is still present, proceed to Step 2. Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

2-31

If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-72 Clearing equipment alarms

PPI-Unexp_Signal
Signicance A 2 Mbit/s or 34/45 Mbit/s signal has been detected on a tributary which is congured not to expect trafc (i.e. trafc off). Impact None. Consequent alarms/events Tx Trib AIS or TU AIS If Tx Trib AIS selected as consequent action, no indication will be provided at the far path termination. If TU AIS selected as consequent action, TU AIS indication will be provided at far path termination. Note: Tx Trib AIS/TU AIS is congurable by the user (default Tx Trib AIS). Possible causes Cable mis-connection/system conguration. Corrective actions If a 2 Mbit/s or 34/45 Mbit/s signal is expected on this port, recongure system (i.e. turn trafc on for port). If a 2 Mbit/s or 34/45 Mbit/s signal is not expected on this port, check cable connections to ensure that cables are connected to the correct input terminations.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-73

PPI-Loss_of_Signal
Signicance Loss of the tributary input signal, raised if: Impact Trafc affecting. Consequent alarms/events Tx Trib AIS or TU AIS If Tx Trib AIS selected as consequent action, no indication will be provided at the far path termination. If TU AIS selected as consequent action, TU AIS indication will be provided at far path termination. Note 1: Tx Trib AIS/TU AIS is congurable by the user (default Tx Trib AIS). Note 2: If TU AIS is congured as a consequence action of PPI-Loss_of_Signal, TU AIS is transmitted on both aggregates of a protected path. At the far multiplexer, TU AIS may be detected on the working path rst, causing a path protection switch on the far multiplexer. Similarly, upon restoration of the tributary signal, the TU AIS may clear on the idle path rst, causing a path protection switch at the far multiplexer. Possible causes Input connector not properly terminated.
0

2 Mbit/s HDB3 tributary: no marks (ones or violations) are detected for 11 clock periods. 34 Mbit/s HDB3 tributary: input is low for 256 bit periods. 45 Mbit/s B3ZS tributary: no transitions for 200 bit periods.

Preceding equipment failure. Faulty local TN-1C multiplexer.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-74 Clearing equipment alarms

Corrective actions Perform the fault nding procedure given in Procedure 2-32.
Procedure 2-32 PPI-Loss_of_Signal alarm clearing Step 1 Action If the tributary is a 2 Mbit/s signal, use the UI to check that the 2 Mbit/s port is congured for the correct impedance (75 or 120 ). If the tributary is a 34 Mbit/s or 45 Mbit/s signal, use the UI to check that the port is congured for the correct bit rate (34 Mbit/s or 45 Mbit/s). Refer to the User Interface Guide NTP, 323-1081-401 for details.

2-32

If the port is congured incorrectly, recongure as appropriate. If the port is correctly congured, proceed to Step 2.
2 Ensure that the associated input connector is properly connected. Re-connect the connector if required. If the alarm is still present, proceed to Step 3. Verify that a valid tributary signal is present at the output of the cable.

Note: For 2 Mbit/s tributaries, if a spare unused 2 Mbit/s port is available, the 2 Mbit/s signal can be veried by connecting the cable to the spare port. If a signal is present, a PPI-Unexp_Signal alarm will be raised for the spare 2 Mbit/s port.
For 34 Mbit/s or 45 Mbit/s tributaries, or if a spare unused 2 Mbit/s port is not available for 2 Mbit/s tributaries, a manual (external) loopback on the affected port can be used to verify that a valid tributary signal is present. If the alarm clears when the loopback is applied, the tributary input signal is invalid.

If a valid signal is not present, check the interconnecting cable and the tributary source equipment. If a valid signal is present, proceed to Step 4.
4 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original local TN-1C multiplexer and escalate the problem
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-75

PPI-Excessive_BER
Signicance The BER of the code violations in the incoming tributary signal has exceeded 10-3. Impact Trafc affecting. Consequent alarms/events None. Possible causes Errored input signal.
0

Faulty input circuit on TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-33.
Procedure 2-33 PPI-Excessive_BER alarm clearing Step 1 Action Investigate preceding 2 Mbit/s, 34 Mbit/s or 45 Mbit/s equipment for cause of errors.

2-33

If errors are intermittent, most likely cause is cabling and the connectors. If no errors from preceding equipment, proceed to Step 2.
2 Perform a manual (external) loopback on the appropriate tributary port.

If the alarm is still present, remove the external loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the external loopback and escalate problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-76 Clearing equipment alarms

PPI-Signal_Degrade
Signicance The BER of the code violations in the incoming tributary signal has exceeded 10-5. Impact Trafc affecting. Consequent alarms/events None. Possible causes Errored input signal.
0

Faulty input circuit on TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedures given in Procedure 2-34.
Procedure 2-34 PPI-Signal_Degrade alarm clearing Step 1 Action Investigate preceding 2 Mbit/s, 34 Mbit/s or 45 Mbit/s equipment for cause of errors.

2-34

If errors are intermittent, most likely cause is cabling and the connectors. If no errors from preceding equipment, proceed to Step 2.
2 Perform a manual (external) loopback on the appropriate tributary port.

If the alarm is still present, remove the external loopback and replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem. If the alarm clears, remove the external loopback and escalate problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-77

INT-LP-IP_Buffer
Signicance The FIFO in the mapping/multiplexing direction is in an underow or overow state. Impact Trafc affecting. Consequent alarms/events None. Possible causes Incoming tributary signal out-of-limits.
0

Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-35.
Procedure 2-35 INT-LP-IP_Buffer Step 1 Action Check if tributary input signal is within limits.

2-35

If tributary input signal is not within limits, investigate preceding 2 Mbit/s equipment. If tributary input signal is within limits, proceed to Step 2.
2 Isolate the TN-1C from the synchronisation perspective (i.e. remove all external sources from the hierarchy so that the TN-1C is operating in the holdover mode).

If the alarm clears, investigate the network for possible synchronisation loops. If the alarm is still present, return the synchronisation hierarchy to the previous settings and proceed to Step 2.
3 Replace the local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If the alarm is still present, replace the original TN-1C multiplexer and escalate the problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-78 Clearing equipment alarms

EA-Ext_inpn
Signicance The external alarm n (where n = 1 to 8) is active. The alarms can be assigned names of up to 8 characters. Impact Dependant on what the alarm represents. Consequent alarms/events None. Possible causes External device. Corrective actions Investigate external device.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-79

SYNC-Holdover
Signicance The synchronisation clock has entered the holdover (using last known frequency) or free-run (using internal clock) state. The alarm is not raised during switching between external sources. Note: The alarm is not raised if the internal clock is selected as the primary source. Impact The multiplexer is not traceable to the network synchronisation, which may cause problems depending on the system synchronisation architecture. Consequent alarms/events None. Possible causes No valid external synchronisation sources available.
0

Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-36.
Procedure 2-36 SYNC-Holdover alarm clearing Step 1 Action Check each of the sources in the synchronisation hierarchy for validity (e.g. appropriate alarms). If any of the sources are invalid, perform the appropriate alarm clearing procedure to clear alarm. If synchronisation is non-revertive, perform a manual switch back to required source. If the multiplexer cannot synchronise to any valid source, proceed to Step 2. 2 Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

2-36

If alarm still present, replace original local TN-1C multiplexer and escalate problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-80 Clearing equipment alarms

SYNC-SETG_Fail
Signicance The synchronisation source has become invalid. Impact None. Consequent alarms/events None. Possible causes Loss of selected synchronisation signal. Receipt of AIS on aggregate selected as synchronisation source. Source out-of-limits. Excessive BER on selected source (see Note). Loss of frame alignment on selected STM signal (see Note). HP-Path_Trace alarm present. Note: Excessive BER, loss of frame alignment, and HP-Path_Trace are user congurable criteria for synchronisation source switching.
0

Corrective actions Perform the alarm clearing procedure given in Procedure 2-37.
Procedure 2-37 SYNC-SETG_Fail alarm clearing Step 1 Action Use the UI (view_status/sync_source_status) to check if the source is out-of-limits (indicated by SS_OUT_OF_LIMITS in the report).

2-37

If the source is out-of-limits, x the source frequency, then use the UI to clear the out-of-limits alarm (see User Interface Guide, NTP 323-1081-401). If the source is not out-of-limits, proceed to Step 2.
2 Investigate the cause of source failure.

If cause identied, perform the alarm clearing procedures for the appropriate alarm. When the synchronisation source is recovered, the SYNC-SETG_Fail alarm clears. If the alarm is still present, escalate the problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-81

NE-Ext_Card_Out
Signicance The tributary extension card is provisioned as equipped but is not physically present. Impact Loss of tributary trafc carried by tributary extension card. Consequent alarms/events TU-AIS injection on all channels that are connected to the tributary extension card. Possible causes Tributary extension card removed.
0

System incorrectly congured. Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-38.
Procedure 2-38 NE-Ext_Card_Out alarm clearing Step 1 Action Check if tributary extension card is expected.

2-38

If tributary extension card is expected, check that the tributary extension card is correctly installed in the TN-1C. If alarm still present, proceed to Step 3. If the tributary extension card is not expected, proceed to Step 2.
2 Provision the equipment to unequip the tributary extension card (see User Interface Guide, NTP 323-1081-401).

If alarm still present, proceed to Step 3.

3 Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If alarm still present, replace original local TN-1C multiplexer and escalate problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-82 Clearing equipment alarms

NE-Wrong_Card
Signicance If the alarm is reported with instance S2, the tributary extension card is physically present but has been equipped as a different type of tributary extension card. If the alarm is reported with instance S0, the tributary extension card equipped does not correspond to the backplane of the TN-1C. If a 8 x 2 Mbit/s tributary extension card (NTFT08AA) is being tted, the backplane must be NTFT03AC (part of TN-1C NTFT52AB). If a 34/45 Mbit/s tributary extension card (NTFT31AA) is being tted, the backplane can be NTFT03AB or NTFT03AC. Loss of tributary trafc carried by tributary extension card. TU-AIS injection on all channels that are connected to the tributary extension card.

Impact

Consequent alarms/events None. Possible causes Wrong tributary extension card tted.
0

System incorrectly congured. Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-39.
Procedure 2-39 NE-Wrong_Card alarm clearing Step 1 Action Check what tributary extension card/connector panel should be tted.

2-39

If the correct tributary extension card is not tted, t the correct tributary extension card in the TN-1C. If alarm still present, proceed to Step 3. If the correct tributary extension card is tted, proceed to Step 2.
2 Provision the equipment to equip the correct tributary extension card (see User Interface Guide, NTP 323-1081-401).

If alarm still present, proceed to Step 3.

continued

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-83 Procedure 2-39 NE-Wrong_Card alarm clearing Step 3 Action Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

2-39

If alarm still present, replace original local TN-1C multiplexer and escalate problem.
end

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-84 Clearing equipment alarms

NE-Unexpected_Card
Signicance The tributary extension card is physically present but is provisioned as unequipped. Impact Loss of tributary trafc carried by tributary extension card. Consequent alarms/events None. Possible causes Tributary extension card incorrectly tted.
0

System incorrectly congured. Faulty local TN-1C multiplexer.

Corrective actions Perform the alarm clearing procedure given in Procedure 2-40.
Procedure 2-40 NE-Unexpected_Card alarm clearing Step 1 Action Check if tributary extension card is expected.

2-40

If tributary extension card is not expected, remove the tributary extension card from the TN-1C. If alarm still present, proceed to Step 3. If the tributary extension card is expected, proceed to Step 2.
2 Provision the equipment to equip the tributary extension card of the correct type (see User Interface Guide, NTP 323-1081-401).

If alarm still present, proceed to Step 3.

3 Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

If alarm still present, replace original local TN-1C multiplexer and escalate problem.
end

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Clearing equipment alarms 2-85

NE-Fan_Fail
Signicance The fan has been detected as faulty (i.e. on the rst time it is used). The alarm is only cleared when the fan is proved to be operating or is removed. Note: The NE-Fan_Fail alarm is raised after approximately 30 seconds from detecting the condition and remains active for approximately 30 seconds after the cause is removed. Impact Possible overheating of TN-1C. Consequent alarms/events None. Possible causes Faulty fan module.
0

Faulty wiring to fan module. Faulty -12 V fan power.

Corrective actions Check that the wiring to the fan is correct/not broken. If wiring correct/not broken, replace fan module. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

2-86 Clearing equipment alarms

NE-High_Temp
Signicance The NE temperature has exceeded 55C. The alarm is cleared if the temperature falls below 39C. Possible overheating of TN-1C. Consequent alarms/events If fan is tted, fan will operate. Possible causes Fan module required. Faulty fan module. Ambient temperature too high.

Impact

Corrective actions If fan not tted, t fan module. Refer to the Installation Procedures, NTP 323-1081-200, for installation procedures. If fan tted, use UI to force fan on. If fan does not operate, replace fan module. Refer to the Equipment Maintenance Procedures, NTP 323-1081-547, for replacement procedures.

End of chapter file

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

3-1

Chapter 3: Common procedures

This chapter provides a list of common task procedures to which the user is referred when performing certain alarm clearing procedures.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

3-2 Common procedures

Optical connector cleaning

All optical connectors must be treated with the utmost care and a very high standard of cleanliness maintained otherwise their performance may be seriously affected. As soon as a connector is disconnected, the free ends MUST be protected with dust caps. WARNING
Danger from exposure to laser light

Avoid direct exposure to laser beam or bre. Invisible laser light can blind. Keep all optical connectors capped. Ensure that the far end of the bre is disconnected before starting the cleaning procedure. Materials required The following materials are required for cleaning optical connectors and couplings: Microscope with adaptor suitable for connector Lint free anti-static lens tissues Cotton buds Approved cleaning solvent Aerosol dust remover (anti-static). CAUTION
Cleanliness of materials

Always use new cleaning cloth material and lens tissues to avoid contamination. Never re-use materials. Ensure connector caps are clean and dust free. There are two main dirt problems for an optical connector, dust and the grease to which dust can stick. Dust appears as lumps, akes, or even bres (from clothes or hair). Grease appears as smears or blobs and is most commonly introduced from the nger tips.

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Common procedures 3-3

The procedures for cleaning optical plugs and optical couplers are described in Procedure 3-1 and Procedure 3-2.
Procedure 3-1 Cleaning an optical plug Step 1 Action Inspect the connector using the microscope. Where possible the side as well as the end of the ferrule should be inspected for serious scores or scratches (visible to the naked eye). The ferrule end should then be inspected using a microscope. Particular attention should be paid to the core area of the bre. The bre end must be generally smooth and free from cracks. Slight chipping in the cladding is permissible but not obvious cracks or any damage that extends to the core area. There will invariably be some score marks. Obvious deep score marks are usually evidence of damage by foreign bodies. If these marks are pronounced or extend near to or into the bre, then the plug should be rejected and the cable reterminated. 2 3 4 5 Blow dust clear using the aerosol dust remover. Inspect again. In the case of persistent dust wipe with clean, dry tissue. Blow dust clear. Inspect again. In the case of persistent dirt or grease (nger marks etc.) apply a small amount of solvent from a solvent dispenser on to a tissue and wipe the plug with the tissue. Blow dry and clear of dust using the aerosol dust remover. Reinspect and repeat the cleaning procedure if necessary.
end

3-1

6 7

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

3-4 Common procedures Procedure 3-2 Cleaning an optical coupler Step 1 2 3 Action Inspect and, if necessary, proceed with steps 2 to 5 Blow dust clear using the aerosol dust remover. Inspect again. In the case of persistent dirt or grease, apply some solvent to the tip of a cotton bud and wipe out dirt. Blow dry and clear of dust. Reinspect and repeat the cleaning procedure if necessary.
end

3-2

4 5

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Common procedures 3-5

Optical output power measurement

WARNING
Danger from exposure to laser light

Avoid direct exposure to laser beam or bre. Invisible laser light can blind. Keep all optical connectors capped. The procedure for measuring the optical output power is given in Procedure 3-3.
Procedure 3-3 Optical output power measurement Step 1 2 3 Action Connect the Craft Access Terminal to the TN-1C. Open a UI session with the TN-1C. Enter your username after the prompt: <username> Enter your password after the prompt: <password> The UI main menu is displayed. Turn the laser off (forced_off) by typing: c l o <inst> where <inst> is a or b (required aggregate). Disconnect the optical patchcord from the optical transmit output. Connect the optical transmit output to the input of an optical power meter using a low loss singlemode optical patchcord. Power down and then power-up the TN-1C. Open a UI session with the TN-1C and enter your username and password (see Steps 2 to 4). Use the UI to turn the laser on (forced_on) within 90 seconds of power-up by typing: c l f <inst> where <inst> is a or b (required aggregate).

3
3-3

6 7

Note: The laser on (forced_on) command can only be issued in the rst 90 seconds immediately after power-up.
9 Measure the optical output power of the unit. Limits: -8 dBm to -15 dBm.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

3-6 Common procedures Procedure 3-3 Optical output power measurement (continued) Step 10 Action Use the UI to turn the laser off (forced_off) by typing: c l o <inst> where <inst> is a or b (required aggregate). Disconnect the optical transmit output from the optical power meter. Connect the optical patchcord to the optical transmit output. Use the UI to return the laser to the normal operating state by typing: c l n <inst> where <inst> is a or b (required aggregate). Return to the UI main menu by typing: ~ The UI main menu is displayed. Logout from the UI by typing: l Disconnect the Craft Access Terminal to the TN-1C.
end

3-3

11 12 13

14

15

16

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Common procedures 3-7

Optical input power measurement

WARNING
Danger from exposure to laser light

Avoid direct exposure to laser beam or bre. Invisible laser light can blind. Keep all optical connectors capped. The procedure for measuring the optical input power is given in Procedure 3-4.
Procedure 3-4 Optical input power measurements Step 1 2 Action Open a UI session with the far TN-1C. Enter your username after the prompt: <username> Enter your password after the prompt: <password> The UI main menu is displayed. Turn the laser off (forced_off) at the far TN-1C by typing: c l o <inst> where <inst> is a or b (required aggregate).

3
3-4

Note: This requires a technician at the far-end in the case of an unprotected system or if other end is a TN-1X. If the far end is unmanned, do not issue a remote laser off (forced_off) command for the far end otherwise communication will be lost with the far end.
5 Disconnect the receive optical bre from the receive optical input and connect the optical receive bre to the input of an optical power meter. Power down and then power-up the TN-1C at the far end. Open a UI session with the far TN-1C and enter your username and password (see Steps 1 to 3). Use the UI to turn the laser on (forced_on) at the far end by typing: c l f <inst> where <inst> is a or b (required aggregate).

Note: The laser on (forced_on) command can only be issued in the rst 90 seconds immediately after power-up.
continued

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

3-8 Common procedures Procedure 3-4 Optical input power measurements (continued) Step 7 Action Measure the optical input power from the bre. Limits: -8 dBm to -28 dBm. 8 Turn the laser off (forced_off) at the far by typing: c l o <inst> where <inst> is a or b (required aggregate). Disconnect the receive optical bre from the optical power meter and reconnect the bre to the receive optical input connector. Use the UI to return the laser at the far end to the normal operating state by typing: c l n <inst> where <inst> is a or b (required aggregate). Return to the UI main menu by typing: ~ The UI main menu is displayed. Logout from the UI by typing: l
end

3-4

10

11

12

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Common procedures 3-9

Applying/clearing loopbacks
The TN-1C has a number of loopback facilities which can be used in the alarm clearing/maintenance procedures, see Chapter 4 for details. CAUTION
STM-1 local loopback

Activating the STM-1 local loopback will cause loss of trafc.

STM-1 loopbacks

Activating the STM-1 local or remote loopback on an unprotected STM-1 link (or STM-1 local or remote loopbacks on both aggregates on an protected STM-1 link) will cause subsequent loss of ECC communications. If the loopback(s) is activated remotely, a site visit will be required to de-activate the loopback. The procedure for applying/clearing loopbacks is given in Procedure 3-5.

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

3-10 Common procedures Procedure 3-5 Applying/removing loopbacks Step 1 2 Action Open a UI session with the TN-1C via the CAT or the TN-MS EC. Enter your username after the prompt: <username> Enter your password after the prompt: <password> The UI main menu is displayed. To apply a remote loopback, type the following: d l r <inst> where <inst> is a or b for the aggregates or S<m>-<n> for tributaries <m> is the slot number 1 or 2, <n> is the tributary port 1 to 8 for each tributary port. To apply a local loopback, type the following: d l l <inst> where <inst>is a or b for the aggregates or S<m>-<n> for tributaries <m> is the slot number 1 or 2, <n> is the tributary port 1 to 8 for each tributary port. To clear a loopback, type the following: d l c <inst> where <inst> is a or b for the aggregates or S<m>-<n> for tributaries <m> is the slot number 1 or 2, <n> is the tributary port 1 to 8 for each tributary port. 5 Return to the UI main menu by typing: ~ The UI main menu is displayed. Logout from the UI by typing: l
end
End of chapter file

3-5

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

4-1

Chapter 4: Diagnostic tools

This chapter details the diagnostic tools available on the TN-1C multiplexer for maintenance purposes, namely:
0

Loopbacks Tributary Test Pattern Generator and Detector

Loopbacks
Loopbacks are provided for the user for various test procedures and for assisting in alarm clearing. The loopbacks are initiated from the TN-1C UI. CAUTION
Synchronisation loops

When performing loopbacks, pay attention to avoid synchronisation loops.

STM-1 local loopback (Loop to Mux) A local loopback can be activated on either of the aggregates. When activated, the outgoing STM-1 data is routed back to the STM-1 receiver on the same aggregate link, as well as being transmitted towards the line (see Figure 4-1). CAUTION
STM-1 local loopback

Where possible, all trafc should be switched away from the aggregate port before activating the STM-1 local loopback. Activating the STM-1 local loopback will cause loss of trafc on that aggregate. Activating the STM-1 local loopback on an unprotected STM-1 link (or STM-1 local loopbacks on both aggregates on an protected STM-1 link) will cause subsequent loss of ECC communications. If the loopback(s) is activated remotely, a site visit will be required to de-activate the loopback. Note: When activating the STM-1 local loopback, a temporary RS-Loss_of_Signal alarm will be raised whilst the loopback switch
323-1081-543 Release 2 Standard TN-1C Alarm Clearing Procedures

4-2 Diagnostic tools

occurs. If any of the paths are switched to this aggregate, path protection switching will occur for these tributaries. STM-1 remote loopback (Loop to Line) A remote loopback can be activated on either of the aggregates. When activated, the incoming STM-1 data is routed back to the STM-1 transmitter on the same aggregate link, as well as being transmitted towards the TN-1C (see Figure 4-1). CAUTION
STM-1 remote loopback

Where possible, all trafc should be switched away from the appropriate aggregate port at the far multiplexer before activating the STM-1 remote loopback. Activating the STM-1 remote loopback will cause loss of trafc on that aggregate. Activating the STM-1 remote loopback on an unprotected STM-1 link (or STM-1 remote loopbacks on both aggregates on an protected STM-1 link) will cause subsequent loss of ECC communications. If the loopback(s) is activated remotely, a site visit will be required to de-activate the loopback. Note: When activating the STM-1 remote loopback, a temporary RS-Loss_of_Signal alarm will be raised at the far multiplexer whilst the loopback switch occurs. If any of the paths are switched to this aggregate, path protection switching will occur at the far multiplexer for these tributaries. Tributary local loopback (Loop to Mux) A local tributary loopback (2 Mbit/s or 34/45 Mbit/s) can be activated independently on any of the tributary ports. When activated, the outgoing tributary data is routed back to the tributary receiver on the same link, as well as being transmitted towards the STM-1 line (see Figure 4-1). Tributary remote loopback (Loop to Line) A remote tributary loopback (2 Mbit/s or 34/45 Mbit/s) can be activated independently on any of the tributary ports. When activated, the incoming tributary data is routed back to the tributary line on the same link, as well as being transmitted towards the tributary receiver (see Figure 4-1). Simultaneous loopbacks STM-1 and tributary loopbacks can be performed independently. On a specic tributary or aggregate, only one direction of loopback (local or remote) is allowed at a given time. If a loopback request is made for one direction whilst the other direction loopback is active, the current loopback is deactivated and the requested loopback is activated.
TN-1C Alarm Clearing Procedures 323-1081-543 Release 2 Standard

Diagnostic tools 4-3 Figure 4-1 TN-1C loopbacks

4-1

STM-1 Section Termination Module DSPI ElectroOptical Module

STM-1 local loopback

STM-1 Section Termination Module DSPI ElectroOptical Module

STM-1 remote loopback

2 Mbit/s or 34/45 Mbit/s

Trib Electrical Line Driver

Trib Mapper

Tributary local loopback

2 Mbit/s or 34/45 Mbit/s

Trib Electrical Line Driver

Trib Mapper

Tributary remote loopback

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

4-4 Diagnostic tools

2 Mbit/s or 34 Mbit/s test pattern generator and detector

The TN-1C multiplexer includes an in-built 2 Mbit/s or 34 Mbit/s test pattern generator and detector. The facility allows the bit-error performance to be measured for a selected 2 Mbit/s or 34 Mbit/s channel. The Pseudo-Random Binary Sequence (PRBS) generator/detector is located between the tributary mapper and the tributary line drivers as shown in Figure 4-2. The PRBS generator/detector is shown for a single tributary, the PRBS generator/detector is common for all tributaries and can be switched to any tributary.
Figure 4-2 PRBS location

4-2

PRBS Generator

2 Mbit/s or 34/45 Mbit/s Trib electrical line driver PRBS Detector Trib mapper

towards optical line

Note 1: PRBS should not be injected towards the optical side when the same tributary is in remote loopback. The test will fail due to a lack of clock source in that scenario and the test does not provide any value. Note 2: When the 34 Mbit/s PRBS to line is applied, the downstream trafc (to 34 Mbit/s line) is broken and PRBS is injected instead. Note 3: For 34 Mbit/s tributaries, PRBS to line does not operate if a PPI-Loss_of_Signal alarm is detected on the tributary. The test pattern is a PRBS with a pattern length of 215-1 for 2 Mbit/s tributaries and 223-1 for 34/45 Mbit/s tributaries, as dened in ITU-T O.151. The pattern may be injected towards the aggregate on a specic tributary link or towards the tributary line. The pattern overrides the tributary data and framing bits (e.g. for 2 Mbit/s signal all 256 bits per frame carry the test pattern). The pattern detector is connected to the tributary data extracted from the VC-12/VC-3 or from the tributary line. The detector synchronises to the test pattern and then counts the errors between the incoming bit-stream and the expected bit-stream. An indication is provided if synchronisation is lost during the test period. The errors are periodically read and accumulated to derive the test results. The period of test results can be set (1 - 30000 seconds, default 30 seconds). Note: If the period of test results is too frequent, it will cause fast scrolling on the UI screen, making it hard to read for the user.
TN-1C Alarm Clearing Procedures 323-1081-543 Release 2 Standard

Diagnostic tools 4-5

The results are displayed on all open UI sessions. The following is an example of the format of the results:
89, Continuity Test Results 891, S1-1, Test_name: Continuity, User name = nortl, 01/08/1995 16:22:58 892, S1-1, CT_direction = Fiber, CT_elapsed_time = 00:00:00 893, S1-1, CT_stnc_status_since_last_report = NO_sync 894, S1-1, CT_error_count = 0, CT_BER = 0.0E+00, * 895, End of Test Results;

Note: If an * is shown at the end of the PRBS report (as above), it indicates that synchronisation was lost or a counter overow occurred while the test was running (this invalidates the whole test).
Procedure 4-1 Applying/stopping a continuity test Step 1 2 3 Action Open a UI session with the TN-1C. Enter your username after the prompt: <username> Enter your password after the prompt: <password> The UI main menu is displayed. To apply a continuity test towards the optical line, type the following: d c f <trib_inst> <RF> <trib_inst> is S<m>-<n> where <m> is the card number 1 or 2, <n> is the tributary port 1 to 8 for each tributary <RF> is the report frequency (range 1 to 30,000 seconds, in 1 second steps, default 30 seconds) To apply a continuity test towards the tributary line, type the following: d c l <trib_ inst> <RF> <trib_inst> is S<m>-<n> where <m> is the card number 1 or 2, <n> is the tributary port 1 to 8 for each tributary <RF> is the report frequency (range 1 to 30,000 seconds, in 1 second steps, default 30 seconds) To stop a continuity test, type the following: d c s 5 Return to the UI main menu by typing: ~ The UI main menu is displayed. Logout from the UI by typing: l
end
End of chapter file

4-1

323-1081-543 Release 2 Standard

TN-1C Alarm Clearing Procedures

5-1

Index
Numerics
2 Mbit/s test pattern 4-4 34 Mbit/s test pattern 4-4 HP-Signal_Label 2-59 HP-TU_Multiframe 2-43

I
INT-AU-AIS 2-47 INT-EC-Alarms_Buffer 2-7 INT-HP-Insert_Bus 2-21 INT-HP-IP_Buffer 2-37 INT-LP-IP_Buffer 2-77 INT-LP-OP_Buffer 2-70 INT-NE-Config_Corrupt 2-12 INT-NE-RAM_Fail 2-11 INT-NE-SW_Corrupt 2-6 INT-OS-Laser_Test 2-27 INT-RS-Tx_Buffer 2-20 INT-TU-AIS 2-61 INT-TU-LOP 2-62

A
alarm category 1-9 consequences 1-6 indications 1-1 masking 1-2 severity 1-9 associated documents xi AU-AIS 2-41 audience xi

C
cleaning optical connector 3-2 craft access terminal 1-2

L
logs 1-8 loopbacks 4-1 applying/removing 3-9 LP-Excessive_BER 2-63 LP-FEBE 2-69 LP-FERF 2-68 LP-Signal_Degrade 2-65 LP-Signal_Label 2-66

D
diagnostic tools 4-1

E
EA-Ext-inpn 2-78 element controller 1-2

F
fault finding beginning 1-8

M
maintenance philosophy 1-1 masking 1-2 measurement optical input power 3-7 optical output power 3-5 MS-AIS 2-34 MS-Excessive_BER 2-29 MS-FERF 2-36
TN-1C Alarm Clearing Procedures

H
HP-Excessive_BER 2-49 HP-FEBE 2-52 HP-FERF 2-51 HP-Path_Trace 2-57 HP-Signal_Degrade 2-50
323-1081-543 Release 2 Standard

5-2 Index

MS-Signal_Degrade 2-32

N
NE-Card_Fail 2-14 NE-Door_Open 2-8 NE-Ext_Card_Out 2-81 NE-Fail_Fail 2-85 NE-High_Temp 2-86 NE-Unexpected_Card 2-84 NE-Wrong_Card 2-82

O
optical connector cleaning 3-2 optical input power measurement 3-7 optical output power measurement 3-5 OS-Laser_Bias_High 2-19 OS-Laser_Shutdown 2-28 OS-Optical_Power_High 2-18

P
PPI-Excessive_BER 2-75 PPI-Loss_of_Signal 2-73 PPI-Output_Fail 2-71 PPI-Signal_Degrade 2-76 PPI-Unexp_Signal 2-72 PS-Battery_Low 2-5 PS-Door_Open 2-9 PS-Power_Fail 2-4

Q
Qecc-Comms_Fail 2-39

R
RS-Loss_of_Frame 2-22 RS-Loss_of_Signal 2-15 RS-Realign_Phase 2-25

S
SYNC-Holdover 2-79 SYNC-SETG_Fail 2-80

T
TU-AIS 2-53 TU-LOP 2-55

TN-1C Alarm Clearing Procedures

323-1081-543 Release 2 Standard

Contacts Legal statements Trademarks

International Broadband Networks (Dept. 18600) Nortel plc Oakleigh Road South London, N11 1HB So far as Northern Telecom is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Northern Telecom can give no warranty or undertaking and make no representation as to their accuracy. In particular, Northern Telecom 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.

Family Product Manual Copyright Copyright statement NT confidetial DocNum DocIssue DocStatus Date Publishing statement

SDH TRANSMISSION

Nortel TN-1C
Alarm Clearing Procedures
Copyright 1996, 1997 Northern Telecom The copyright of this document is the property of Northern Telecom. Without the written consent of Northern Telecom, 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.

NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation, and maintenance purposes only.
Document Number: 323-1081-543 Product Release Number: Release 2 Document Status: Standard Date: June 1997 Printed in England