Cảnh Báo SDH

323-1081-543
SDH TRANSMISSION
Nortel TN-1C/TN-1P
Alarm Clearing Procedures
Release 5.1 Standard September 2000
SDH TRANSMISSION
Nortel TN-1C/TN-1P
Document Number: 323-1081-543 Document Status: Standard Product Release Number: 5.1 Date: September 2000
Copyright 1996 2000 Nortel Networks, All Rights Reserved. Printed in England
The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever. NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document. *NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are trademarks of Nortel Networks. Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation. IBM is a registered trademark of International Business Machines Corporation. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation.
Nortel TN-1C/TN-1P Alarm Clearing Procedures
iii
Publication history
September 2000 Release 5.1 Standard. Release 5.1 features added. November 1999 Release 5 Standard. TN-1C and TN-1P documents combined, Release 5 features added. March 1998 Release 3 Standard. June 1997 Release 2 Standard. December 1996 Release 1 Standard.
Contents
About this document Technical support and information Introduction
Maintenance philosophy 1-1 Alarm indications 1-1 Element Controller 1-2 Craft access terminal 1-2 Unit indications 1-3 TN-1C multiplexer 1-3 TN-1P multiplexer 1-3 TN-1P Basestation multiplexer 1-3 Power Supply Unit 1-4 Rack Alarm Adapter (optional) 1-5 Alarm sequences 1-5 Rack alarms 1-6 Alarm masking 1-6 Alarm consequences 1-11 Alarm monitoring 1-13 Beginning fault finding 1-14 Responding to logs 1-15 Alarm category and severity 1-15
ix x 1-1
Clearing TN-1C/TN-1P equipment alarms Common procedures

Optical connector cleaning 3-2 Optical output power measurement 3-4 Optical input power measurement 3-6 Applying/clearing loopbacks 3-8
2-1 3-1
Diagnostic tools
Loopbacks 4-1 2 Mbit/s or 34/45 Mbit/s test pattern generator and detector 4-4
4-1
Index
5-1
vi
List of figures
Figure 1-1 Figure 1-2 Figure 1-3 Figure 1-4 Figure 1-5 Figure 4-1 Figure 4-2 TN-1P Craft Access Panel - front view 1-4 Rack alarm state sequence diagram 1-6 Masking hierarchy for TN-1C/TN-1P (part 1) 1-8 Masking hierarchy for TN-1C/TN-1P (part 2) 1-9 Masking hierarchy for TN-1C/TN-1P (part 3) 1-10 TN-1C/TN-1P loopbacks 4-3 TN-1C/TN-1P PRBS location 4-4
List of tables
Table 1-1 Table 1-2 Table 2-1 Alarm consequences TN-1C/TN-1P 1-12 TN-1C/TN-1P alarm category and alarm severity settings 1-15 List of alarm clearing procedures for TN-1C/TN-1P 2-3
List of 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 AU-AIS alarm clearing 2-9 HP-DEG alarm clearing 2-12 HP-EXC alarm clearing 2-14 HP-LOM alarm clearing 2-18 HP-PLM alarm clearing 2-21 HP-RDI alarm clearing 2-24 HP-REI alarm clearing 2-25 HP-TIM alarm clearing 2-28 INT-HP-IP_Buffer alarm clearing 2-34 INT-LP-IP_Buffer 2-36 INT-LP-OP_Buffer alarm clearing 2-37 INT-NE-Config_Corrupt alarm clearing 2-38 LP-DEG alarm clearing 2-46 LP-EXC alarm clearing 2-48 LP-PLM alarm clearing 2-52 LP-RDI alarm clearing 2-55 LP-REI alarm clearing 2-56 MS-AIS alarm clearing 2-58 MS-DEG alarm clearing 2-60 MS-EXC alarm clearing 2-62 MS-RDI alarm clearing 2-66 NE-Door_Open alarm clearing 2-68 NE-Ext_Card_Out alarm clearing 2-69 NE-Minor_Card_Mismatch alarm clearing 2-72 NE-Unexpected_Card alarm clearing 2-73 NE-Wrong_Card alarm clearing 2-74 PPI-Continuity_Test alarm clearing 2-79 PPI-DEG alarm clearing 2-84 PPI-EXC alarm clearing 2-85 PPI-Loopback_On alarm clearing 2-90 PPI-LOS alarm clearing 2-92 PPI-TF alarm clearing 2-93 PS-Battery_Low alarm clearing 2-97 PS-Door_Open alarm clearing 2-99 PS-Power_Fail alarm clearing 2-100 Qecc-Comms_Fail alarm clearing 2-102 RS-LOF alarm clearing 2-104 RS-Loopback_On alarm clearing 2-106 RS-LOS alarm clearing 2-108
323-1081-543 Release 5.1 Standard
vii Procedure 2-40 Procedure 2-41 Procedure 2-42 Procedure 2-43 Procedure 2-44 Procedure 2-45 Procedure 2-46 Procedure 2-47 Procedure 3-1 Procedure 3-2 Procedure 3-3 Procedure 3-4 Procedure 3-5 Procedure 4-1 RS-Realign_Phase alarm clearing 2-110 SYNC-Ext_Sync_LOS alarm clearing 2-112 SYNC-Source_Fail alarm clearing 2-113 SYNC-Source_Out_of_Limits alarm clearing 2-114 SYNC-SSMB_Unstable alarm clearing 2-116 SYNC-Holdover alarm clearing 2-117 TU-AIS alarm clearing 2-119 TU-LOP alarm clearing 2-121 Cleaning an optical plug 3-3 Cleaning an optical coupler 3-3 Optical output power measurement 3-4 Optical input power measurements 3-6 Applying/removing TN-1C/TN-1P loopbacks 3-8 Applying/stopping a TN-1C/TN-1P continuity test 4-5
Nortel TN-1C/TN-1P
ix
About this document

This document provides information on the alarm clearing procedures for Nortel Networks TN-1C, TN-1P, TN-1P Basestation and TN-1PH multiplexers. Note: Unless otherwise specified, the term TN-1P is used to refer to the standard TN-1P, the TN-1P Basestation and the TN-1PH multiplexers. The document is divided into the following chapters: Chapter 1: Provides general information regarding the maintenance philosophy and a guide to initial fault finding. Chapter 2: Provides details on each of the alarms generated by the TN-1C/ TN-1P and procedures for clearing each fault. Chapter 3: Provides details of common procedures used in the alarm clearing procedures for TN-1C/TN-1P. Chapter 4: Provides details of diagnostic tools available on the TN-1C/ TN-1P which may be used in the alarm clearing procedures.
Indication of trademarks in this document The asterisk after a name denotes a trademarked item. The title page and back cover acknowledge all trademarked items.
Audience
This document is intended for: Maintenance engineers Customer support engineers
Associated documents
TN-1C/TN-1P Documentation Overview and Safety, 323-1081-090 TN-1C/TN-1P Browser User Interface Guide, 323-1081-403. TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401. TN-1C/TN-1P Equipment Maintenance Procedures, 323-1081-547.
Technical support and information

So far as Nortel Networks is aware the information in this document is correct. If, however, you discover any errors or have comments regarding the presentation of the content, please send details by email to: IONNTPS@nortelnetworks.com Nortel Networks provides a comprehensive technical support service for its customers. The Nortel Networks Service Desk may be contacted Monday to Friday between the hours of 08:30 and 17:00 (UK local time), using the following FAX or telephone numbers: United Kingdom Freephone: 0800 626 881 Telephone: 020 8361 4693 FAX: 020 8945 3456 International Telephone: FAX: +44 20 8361 4693 +44 20 8945 3456
EMC conformance
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.
1
1-1
Introduction
Maintenance philosophy
1-
This chapter provides the field maintenance strategy for locating faulty TN-1C/TN-1P 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 traffic.
Alarm indications
When a defect is detected, the following occurs: When used in a managed environment, the defect is reported to the Element Controller (EC-1). 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 Preside Applications Platform (Preside AP), if applicable, for first-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 fitted (not applicable to wall mounted TN-1C, standard TN-1P, TN-1P Basestation or TN-1P Headend subrack), the appropriate LEDs on the Rack Alarm Adapter are lit and graded alarm extensions are provided to the station alarm system. For the TN-1P Headend subrack, lights the appropriate subrack alarm status LEDs on the Craft Access Panel (CAP) and provides graded alarm extensions to the station alarm system. The appropriate LEDs on the TN-1C/TN-1P units are lit. Where possible, services are re-established by performing path protection switching. When the alarm indicates a path failure or receipt of alarm indication signal (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/TN-1P 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-3).
Nortel TN-1C/TN-1P
1-2 Introduction
Element Controller
The Element Controller (EC-1) provides all the facilities needed for flexible management of synchronous digital networks based on Nortel Networks synchronous multiplexers. When a TN-1C/TN-1P multiplexer Network Element (NE) is brought within the EC-1 span of control, an Element Controller Association Session (ECAS) is set up between the TN-1C/TN-1P and the EC-1. This provides a communications channel through which unsolicited event and alarm messages are sent, performance monitoring reports are polled, and NE clocks are aligned. For configuration and monitoring facilities, the EC-1 also provides access for the following: the Browser user interface on the TN-1C/TN-1P the Command Line User Interface (UI) on the TN-1C/TN-1P
When used with the TN-1C/TN-1P, the EC-1 provides consolidated alarm reporting for all NEs within its span of control, providing alarm counts according to the severity of the alarms. The EC-1 also provides alarm/event logs which can be viewed, printed and archieved. The EC-1 requests performance monitoring reports from the TN-1C/TN-1P NE once every eight hours which are stored in a daily log. The logs are kept in a comma delimited file which simplifies the exporting to external spreadsheet programs. Viewing, filtering, printing and exporting of performance monitoring reports is carried out outside the EC-1. Logs are saved for seven days.
Craft access terminal

The craft access terminal (CAT) for the TN-1C/TN-1P is an IBM* compatible laptop PC running Microsoft* Windows* 95. Additional software, such as Netscape Navigator* and the Netscape FastTrack Server is also required. Access with the TN-1C/TN-1P is via an RS232 serial interface port. The TN-1C/TN-1P can be monitored and configured using the Browser User Interface or the Command Line User Interface. The Browser is a HTML interface to the TN-1C/TN-1P embedded application software and presents the results as an intuitive point-and-click interface inside the Netscape Navigator hypertext browser. The Command Line User Interface is accessed using terminal application software. Details of the craft access facilities are given in the TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 and TN-1C/TN-1P Browser User Interface Guide, 323-1081-403.
Introduction 1-3
Unit indications
TN-1C multiplexer The following indications are provided on the TN-1C multiplexers (not visible when cover is fitted): Red FAIL LED (main card). Indicates that a traffic or card alarm has been detected. Red FAIL LED (tributary extension card). Indicates that one of the following has been detected: a traffic alarm related directly to the tributary extension card (for example: PPI-LOS, PPI-EXC etc.) a card alarm (for example: NE-Wrong_Card, NE-Unexpected_Card or NE-Card_Fail). Green ACTIVE LED. Indicates that the +5 V supply is present on the unit.
TN-1P multiplexer The following indications are provided on the TN-1P multiplexers (not visible when cover is fitted to wall mounted version or headend subrack version): Red FAIL LED. Indicates that a traffic or card alarm has been detected. Green ACTIVE LED. Indicates that the +5 V supply is present on the unit.
TN-1P Basestation multiplexer The following indications are provided on the TN-1P Basestation multiplexer: Red FAIL LED. Indicates that a traffic or card alarm has been detected. Green ACTIVE LED. Indicates that the +5 V supply is present on the unit Note: TN-1P Basestation has no cover/enclosure. Subrack End Processor (SEP) (TN-1P Headend subrack) The following indications are provided on the SEP (not visible when cover is fitted to subrack): Green ACTIVE LED. Indicates that the +5 V supply is present on the SEP. Red FAIL LED. Indicates a LAN failure on one of the TN-1P units in the Headend subrack.
Craft Access Panel (CAP) (TN-1P Headend subrack) The following indications are provided on the CAP. A front view of the CAP is given in Figure 1-1. Red Fail LED. Green Receive Att LED.
The two LEDs indicate the overall alarm state of the subrack as follows: both LEDs off - the subrack has no alarms. red FAIL LED only on - the subrack has one or more unacknowledged alarms.
1-4 Introduction
green RCV ACK LED only on - the subrack has an acknowledged alarm that has not yet cleared. both LEDs on - the subrack had an acknowledged alarm that has cleared. The CAP contains a receive attention pushbutton (RCV ATTN) which provides an alarm/clear acknowledge facility for the subrack.
Figure 1-1 TN-1P Craft Access Panel - front view
FAIL RCV-ACK
RCV-ATTN
SELECTED CARD
SELECT
Power Supply Unit The following indications are provided on the Power Supply Unit (on alarm/ interface unit, not visible when cover is fitted) 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.
Introduction 1-5
Rack Alarm Adapter (optional) The following indications are provided on the Rack Alarm Adapter (optional unit on rack mounted TN-1C and standard TN-1P multiplexers) Red Alarm LED. Green Receive Att LED.
The two LEDs indicate the overall alarm state of the TN-1C and standard TN-1P 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.
The Rack Alarm Adapter contains a receive attention pushbutton WHICH provides an alarm/clear acknowledge facility for the TN-1C/TN-1P.
Alarm sequences
Each TN-1C/TN-1P NE maintains a state machine for every alarm instance in order to determine the subrack/rack alarm status. Each alarm instance can be in one of the following states: clear - alarm is not active unacknowledged alarm - alarm is active and has not been acknowledged acknowledged alarm - alarm is active and has been acknowledged unacknowledged clear - alarm has cleared and the clear has not been acknowledged
The sequencing between the alarm states is shown in Figure 1-2.
1-6 Introduction Figure 1-2 Rack alarm state sequence diagram
REC ATT pressed Alarm occurs
Clear
Clear of alarm
Unacknowledged Alarm
REC ATT pressed
REC ATT pressed
Acknowledged Alarm
Alarm occurs Clear of alarm
Unacknowledged Clear
Rack alarms
The Rack Alarm Adapter and the Craft Access Panel (CAP) provide graded alarm extensions to the station alarm system via the rack alarm bus as follows: prompt/deferred - an active unacknowledged alarm with a Prompt or Deferred rack priority is present. in-station - an active unacknowledged alarm with an In-station rack priority is present. receive attention - the multiplexer/subrack is being maintained by a craftsperson (i.e. the receive attention pushbutton has been pressed to acknowledge an alarm). fault clear - an acknowledged alarm has cleared but the clear has not yet been acknowledged.
The rack alarm priority are assigned default setting but can be configured via the UI, default settings are given in Table 1-2.
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 traffic 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.
Introduction 1-7
For example, if RS-LOS (regenerator section loss of signal) and AU-AIS (administrative unit alarm indication signal) are both detected, only RS-LOS is reported as AU-AIS is a consequence of RS-LOS, therefore the AU-AIS indication has a high probability of being caused by the RS-LOS. Note: The abbreviations used in the alarm names are explained fully in the list on page 2-1. Figure 1-3, Figure 1-4 and Figure 1-5 show the masking hierarchy for the TN-1C/TN-1P.
1-8 Introduction Figure 1-3 Masking hierarchy for TN-1C/TN-1P (part 1)
PSBattery_Low
INT-NE-SW _Corrupt
INT-NERAM_Fail
INT-SYNC-Trib _Line_Fail
SYNCHoldover
NEDoor_Open
PSDoorOpen
PS-Power_ Fail
INT-NEConfig_Corrupt
SYNC-Source _Out_of_Limits
SYNCSource_Fail
SYNC-Src_ Not_Primary
EAExt_inp
NECard_Fail
SYNC-SSMB _Unstable
NEHigh_Temp
INT-RSTx_Buffer
OS-Optical_ Power_High
RS-LOS
OS-Laser_ Bias_High
INT-OSLaser_Test
RS-LOS
NE-Fan_ Failed
INT-HPInsert_Bus
RS-Realign_ Phase
RS-LOF
RS-Loopback _on
OS-Laser_ Shutdown **-QOSV_** see note SYNC-Ext_ Sync_LOS
MS-RDI
MS-AIS
QeccComms_Fail
MS-EXC
Note: The QOSV alarms are:

MS-QOSV_24H MS-QOSV_15M HP-QOSV_24H HP-QOSV_15M HP-FE_QOSV_24H HP-FE_QOSV_15M LP-QOSV_24H LP-QOSV_15M LP-FE_QOSV_24H LP-FE_QOSV_15M PPI-CV_QOSV_24H PPI-CV_QOSV_15M PPI-TX_QOSV_24H PPI-TX_QOSV_15M PPI-Frm_QOSV_24H PPI-Frm_QOSV_15M PPI-CRC_QOSV_24H PPI-CRC_QOSV_15M
MS-DEG
AU-AIS
A
To Figure 1-4
TN-1C/TN-1P TN-1C only
Introduction 1-9 Figure 1-4 Masking hierarchy for TN-1C/TN-1P (part 2)
1
INT-HPIP_Buffer
From Figure 1-3
INT-AU_LOP
INT-AU_AIS
HP-EXC
HP-DEG
HP-RDI
HP-LOM
HP-TIM
HP-PLM
HP-REI
TU-LOP
TU-AIS
B
INT-TU_LOP From Figure 1-5
INT-TU_AIS
LP-EXC
INT-LPOP_Buffer
LP-PLM
LP-DEG
LP-RDI
LP-REI TN-1C/TN-1P
1-10 Introduction Figure 1-5 Masking hierarchy for TN-1C/TN-1P (part 3)
NE-Ext_ Card_Out
NE-Wrong_ Card
NE-Unexpected _Card
NE-Card_ Fail To Figure 1-4
NE-Minor_ Card_Mismatch
B
PPI-Continuity_ test PPI-Loopback_ on PPI-Unexp _Signal PPI-TF
PPI-LOS
INT-LPIP_Buffer
PPI-EXC
PPI-AIS
PPI-DEG TN-1C/TN-1P TN-1C only
PPI-LOF
PPI-LOM
Introduction 1-11
Alarm consequences
Certain defects result in automatic consequent actions, namely: Injection of a far end receive failure indication (MS-RDI, HP-RDI, or LP-RDI) to the far path/section end. LP-RDI 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 configured to send either Tx Trib AIS (standard default) or TU AIS (non-standard). When configured 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 (TN-1C only). 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. Configuration switch. The configuration switch is performed using the other configuration data bank, if available and updated. Otherwise software factory-set defaults are used.
Table 1-1 details the consequence of each traffic alarm for the TN-1C/TN-1P.
1-12 Introduction Table 1-1 Alarm consequences TN-1C/TN-1P Consequent Action Pass-through TU AIS Tx Trib or TU AIS Path Protection Switch Laser Shutdown Use other config bank or crash defaults Pass-through AU-AIS ( see Note 7)
LP-EXC
Alarm RS-LOS RS-LOF MS-AIS MS-EXC AU-AIS INT-AU-AIS INT-AU-LOP HP-LOM (see Notes 4 to 6) HP-TIM (see Note 3) HP-PLM (see Notes 3 and 6) TU-AIS TU-LOP INT-TU_AIS INT-TU_LOP LP-PLM (see Note 6) LP-EXC (see Note 1) PPI-LOS PPI-AIS (see Note 6)
continued
Trib AIS
MS-RDI
HP-RDI
LP-RDI
Introduction 1-13 Table 1-1 Alarm consequences TN-1C/TN-1P (continued) Consequent Action Pass-through TU AIS Tx Trib or TU AIS Path Protection Switch Laser Shutdown Use other config bank or crash defaults Pass-through AU-AIS ( see Note 7)
LP-EXC
Alarm PPI-Unexp_Signal (see Note 2) OS-Optical_Power_High INT-NE-Config_Corrupt
Note 1: LP-EXC can be user configured not to cause consequent actions (LP-RDI 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 configuration of Tx Trib AIS or TU AIS. In case of standard configuration (i.e. Tx Trib AIS), the PPI-Unexp_Signal will not cause any consequent action. In case of non-standard configuration (i.e. TU AIS), PPI-Unexp_Signal causes TU AIS injection, overriding the unequipped code. PPI-Unexp_Signal has no consequent actions when the traffic is set to Standby. Note 3: HP-TIM and HP-PLM can be user configured not to cause consequent actions (path protection switch, Trib AIS, HP-RDI and LP-RDI). Note 4: Applies to TN-1C only: HP-LOM causes LP-RDI, 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: Applies to TN-1C only: HP-LOM causes pass-through TU AIS for TU-12s only, not for TU-3s. Note 6: HP-LOM, HP-PLM, LP-PLM, and PPI-AIS monitoring can be disabled by the user. Note 7: Pass-through AU-AIS is only applicable if a VC-4 through connection is made.
Alarm monitoring
The user has the option of enabling/disabling the monitoring of some TN-1C and TN-1P alarms. This allows the reduction in alarm flooding and the reporting of spurious alarms. The following alarms can be enabled/disabled: MS-RDI (default = enabled) MS-DEG (default = enabled)
Trib AIS
MS-RDI
HP-RDI
LP-RDI
1-14 Introduction
HP-DEG (default = enabled) HP-RDI (default = enabled) (see Note 1) HP-LOM (default = enabled) HP-PLM (default = enabled) LP-DEG (default = enabled) LP-RDI (default = disabled) LP-PLM (default = enabled) INT-LP-OP-Buffer (default = disabled) PPI-AIS (default = enabled) EA-Ext-Inp (default = disabled) All Quality of Service Violations (QOSV) alarms (default = disabled) HP-TIM (default = disabled) (see Note 2) NE-Door-Open (default = enabled) (see Note 4) Note 1: If monitoring of the LP-RDI or HP-RDI are disabled, the equivalent REI alarm is also disabled. Note 2: This alarm is enabled/disabled using the Path Trace menu. Note 3: All alarms except EA-Ext-Inp and QOSV alarms are enabled/ disabled using the Config/Alarms/Monitoring menu. EA-Ext-Inp alarms are enabled/disabled using the Config/External_alarm menu. QOSV alarms are enabled/disabled using the Config/perF_mon menu. Note 4: The TN-1P Basestation does not support the NE-Door-Open alarm command.
Beginning fault finding

To locate and clear a fault in the TN-1C/TN-1P system, it is recommended to proceed as follows: Identify the TN-1C/TN-1P multiplexers on which the fault indications are present. This is achieved by: On managed systems: use the EC-1 to identify the TN-1C/TN-1P with the highest severity alarms. The EC-1 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: use the CAT (either locally or remotely using the reachthrough feature) to identify the TN-1C/TN-1P with the highest severity alarm. If the external output alarm is used to extend the TN-1C/TN-1P alarms to other external equipment, monitor the external equipment for TN-1C/TN-1P alarm conditions. Refer to Clearing TN-1C/TN-1P equipment alarms on page 2-1 for detailed, step-by-step procedures for clearing TN-1C/TN-1P 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-6).
Introduction 1-15
Responding to logs
TN-1C/TN-1P logs are informational messages that are generated by the TN-1C/TN-1P. The logs can be viewed using the CAT and the EC-1 element controller. 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 Networks personnel when providing further diagnostic support.
Alarm category and severity

For TN-1C and standard TN-1Ps fitted to a Headend subrack, each alarm instance is assigned a rack alarm category (prompt, deferred, or in-station) for extension to a rack alarm system. The default alarm categories for the TN-1C/ TN-1P are given in Table 1-2. These can be changed via the user interface. Alarm instances are assigned a severity, 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/TN-1P browser alarm reports. Alarm reports on the Element Controller use only the alarm severity. Note: The rack alarm categories are the conventional categories used by rack/station alarm systems. However, for the TN-1P subrack, the Prompt and Deferred rack alarm outputs will activate the Prompt bus line, while the Deferred bus line is not connected
Table 1-2 TN-1C/TN-1P alarm category and alarm severity settings Alarm AU-AIS EA-Ext_inp <1 to 8> HP-DEG HP-EXC HP-FE_QOSV_15M HP-FE_QOSV_24H HP-LOM HP-PLM HP-QOSV_15M HP-QOSV_24H Alarm category In-station Prompt Deferred Prompt In-station In-station Deferred Deferred In-station In-station
continued
Alarm severity Minor Critical Major Critical Minor Minor Major Major Minor Minor
1-16 Introduction Table 1-2 TN-1C/TN-1P alarm category and alarm severity settings (continued) Alarm HP-RDI HP-REI HP-TIM INT-AU-AIS INT-AU-LOP INT-HP-Insert_Bus INT-HP-IP_Buffer INT-LP-IP_Buffer INT-LP-OP_Buffer INT-NE-Config_Corrupt INT-NE-RAM_Fail INT-NE-SW_Corrupt INT-OS-Laser_Test INT-RS-Tx_Buffer INT-TU-AIS INT-TU-LOP LP-DEG LP-EXC LP-FE_QOSV_15M LP-FE_QOSV_24H LP-PLM LP-QOSV_15M LP-QOSV_24H LP-RDI LP-REI MS-AIS MS-DEG MS-EXC MS-QOSV_15M MS-QOSV_24H MS-RDI NE-Card_Fail NE-Door_Open Alarm category Deferred Deferred Deferred In-station Deferred Prompt Deferred Deferred Deferred Prompt Prompt Prompt In-station Prompt In-station Deferred Deferred Deferred In-station In-station Deferred In-station In-station Deferred Deferred In-station Deferred Prompt In-station In-station Deferred Prompt Prompt
continued
Alarm severity Major Major Major Minor Major Critical Major Major Major Critical Critical Critical Minor Critical Minor Major Major Major Minor Minor Major Minor Minor Major Major Minor Major Critical MInor MInor Major Critical Critical
Introduction 1-17 Table 1-2 TN-1C/TN-1P alarm category and alarm severity settings (continued) Alarm NE-Ext_Card_Out NE-Fan_Failed NE-High_Temp NE-Minor_Card_Mismatch NE-Unexpected_Card NE-Wrong_Card OS-Laser_Bias_High OS-Laser_Shutdown OS-Optical_Power_High PPI-AIS PPI-Continuity_test PPI-CRC_QOSV_15M PPI-CRC_QOSV_24H PPI-CV_QOSV_15M PPI-CV_QOSV_24H PPI-DEG PPI-EXC PPI-Frm_QOSV_15M PPI-Frm_QOSV_24H PPI-LOM PPI-LOS PPI-LOF PPI-Loopback_on PPI-TF PPI-TX_QOSV_15M PPI-TX_QOSV_24H PPI-Unexp_Signal PS-Battery_Low PS-Door_Open PS-Power_Fail Qecc-Comms_Fail RS-LOF RS-Loopback_on Alarm category Prompt Deferred Prompt In-station In-station Prompt In-station Prompt Prompt In-station In-station In-station In-station In-station In-station Deferred Deferred In-station In-station Deferred Deferred Deferred In-station Deferred In-station In-station In-station Prompt Prompt Prompt Prompt Prompt In-station
continued
Alarm severity Critical Major Critical Minor Minor Critical Minor Critical Critical Minor Minor Minor Minor Minor Minor Major Major Minor Minor Major Major Major Minor Major Minor Minor Minor Critical Critical Critical Critical Critical Minor
1-18 Introduction Table 1-2 TN-1C/TN-1P alarm category and alarm severity settings (continued) Alarm RS-LOS RS-Realign_Phase SYNC-Ext_Sync_LOS SYNC-Holdover SYNC-Source_Fail SYNC-Source_Out_of_Limits SYNC-Src_Not_Primary SYNC-SSMB_Unstable TU-AIS TU-LOP Alarm category Prompt Prompt Deferred Prompt Deferred Deferred Prompt Deferred In-station Deferred
end
end of chapter
Alarm severity Critical Critical Major Critical Major Major Critical Major Minor Major
2-1
Clearing TN-1C/TN-1P equipment alarms

This chapter describes how to locate and clear alarms on TN-1C/TN-1P equipment.
2-
The alarm clearing procedures are based on the following configurations: TN-1C ring system TN-1P to TN-1P point-to-point system
If the TN-1C/TN-1P is used in other system configurations, the user should refer to the appropriate equipment handbooks for the appropriate alarm clearing procedures whenever references are made to the far multiplexer. ATTENTION A TN-1P upgraded with a ADM card reports its identity as a TN-1C and the user must follow alarm clearing procedures for a TN-1C. Note: In cases where an STM local loopback is performed and passed, it might be helpful to also perform a manual optical loopback (using a fibre pigtail) before investigating the problem in the fibre. Table 2-1 provides a list of alarms and the page where the alarm clearing information can be found. The alarm names use the following abbreviations: AIS AU BER Comms Config CV DEG EA EC ECC Alarm indication signal Administrative Unit Bit Error Ratio Communications Configuration Code Violation Degraded External alarm Element Controller Embedded Control Channel
2-2 Clearing TN-1C/TN-1P equipment alarms
EXC Ext FE HP INT IP LOF LOM LOP LOS LP MS NE OP OS PLM PPI PS QOSV RAI RAM RDI REI RS SETG Src SSM SW SYNC Temp TF TIM Trib TU TX
Excessive External Far End High Order Path Internal Input Loss of Frame Loss of Multiframe Loss of Pointer Loss of Signal Low Order Path Multiplex Section Network Element Output Optical Section Path Label Mismatch PDH Physical Interface Power Supply Quality of Service Violation Remote Alarm Indication Random Access Memory Remote Defect Indicator Remote Error Indicator Regenerator Section Synchronous Equipment Timing Generator Source Synchronous Status Messaging Software Synchronisation Temperature Traffic Fail Trace Identifier Mismatch Tributary Tributary Unit Transmit
Clearing TN-1C/TN-1P equipment alarms 2-3 Table 2-1 List of alarm clearing procedures for TN-1C/TN-1P Alarm AU-AIS EA-Ext_inpn<1-8> HP-DEG HP-EXC HP-FE_QOSV_15M HP-FE_QOSV_24H HP-LOM HP-PLM HP-QOSV_15M HP-QOSV_24H HP-RDI HP-REI HP-TIM INT-AU-AIS INT-AU-LOP INT-HP-Insert_Bus INT-HP-IP_Buffer INT-LP-IP_Buffer INT-LP-OP_Buffer INT-NE-Config_Corrupt INT-NE-RAM_Fail INT-NE-SW_Corrupt INT-OS-Laser_Test INT-RS-Tx_Buffer INT-TU-AIS INT-TU-LOP
continued
Page 2-7 2-10 2-11 2-13 2-15 2-16 2-17 2-19 2-22 2-23 2-24 2-25 2-26 2-29 2-31 2-33 2-34 2-36 2-37 2-38 2-40 2-41 2-42 2-43 2-44 2-45
2-4 Clearing TN-1C/TN-1P equipment alarms Table 2-1 List of alarm clearing procedures for TN-1C/TN-1P (continued) Alarm LP-DEG LP-EXC LP-FE_QOSV_15M LP-FE_QOSV_24H LP-PLM LP-QOSV_15M LP-QOSV_24H LP-RDI LP-REI MS-AIS MS-DEG MS-EXC MS-QOSV_15M MS-QOSV_24H MS-RDI NE-Card_Fail NE-Door_Open NE-Ext_Card_Out (TN-1C only) NE-Fan_Failed (TN-1C only) NE-High_Temp (TN-1C only) NE-Minor_Card_Mismatch (TN-1C only) NE-Unexpected_Card (TN-1C only) NE-Wrong_Card (TN-1C only) OS-Laser_Bias_High OS-Laser_Shutdown OS-Optical_Power_High
continued
Page 2-46 2-47 2-49 2-50 2-51 2-53 2-54 2-55 2-56 2-57 2-59 2-61 2-64 2-65 2-66 2-67 2-68 2-69 2-70 2-71 2-72 2-73 2-74 2-75 2-76 2-77
Clearing TN-1C/TN-1P equipment alarms 2-5 Table 2-1 List of alarm clearing procedures for TN-1C/TN-1P (continued) Alarm PPI-AIS PPI-Continuity_Test PPI-CRC_QOSV_15M PPI-CRC_QOSV_24H PPI-CV_QOSV_15M PPI-CV_QOSV_24H PPI-DEG PPI-EXC PPI-Frm_QOSV_15M PPI-Frm_QOSV_24H PPI-LOF PPI-LOM PPI-Loopback_On PPI-LOS PPI-TF PPI-TX_QOSV_15M PPI-TX_QOSV_24H PPI-Unexp_Signal PS-Battery_Low PS-Door_Open PS-Power_Fail Qecc-Comms_Fail RS-LOF RS-Loopback_On RS-LOS RS-Realign_Phase
continued
Page 2-78 2-79 2-80 2-81 2-82 2-83 2-84 2-85 2-86 2-87 2-88 2-89 2-90 2-91 2-93 2-94 2-95 2-96 2-97 2-98 2-100 2-101 2-103 2-106 2-107 2-110
2-6 Clearing TN-1C/TN-1P equipment alarms Table 2-1 List of alarm clearing procedures for TN-1C/TN-1P (continued) Alarm SYNC-Ext_Sync_LOS (TN-1C only) SYNC-Source_Fail SYNC-Source_Out_of_Limits SYNC-Src_Not_Primary SYNC-SSMB_Unstable SYNC-Holdover TU-AIS TU-LOP
end
Page 2-112 2-113 2-114 2-115 2-116 2-117 2-118 2-120
Clearing TN-1C/TN-1P equipment alarms 2-7
AU-AIS
Significance
An AIS has been detected in the H1 and H2 bytes indicating a failure in the upstream path.
Impact
Traffic affecting on unprotected paths. Temporary traffic hit on protected paths.
Consequent alarms/events (TN-1C)

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. HP source HP-RDI alarm. 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). Unprotected add/drop TU paths TU-AIS alarms. LP path source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.
Consequent alarms/events (TN-1P)

Local Protected TU paths Temporary AIS injection on all tributary outputs switched to aggregate containing alarm. If paths switched to aggregate containing alarm, protection switch to other aggregate (if valid). Unprotected TU paths AIS injection on all tributary outputs.
Far end Protected TU paths HP-RDI alarm. LP-RDI alarms if both paths have failed at local multiplexer. Unprotected TU paths HP-RDI and LP-RDI alarms.
Possible causes
AU AIS being generated by far multiplexer. Note: AU AIS is not intentionally generated by the TN-1C/TN-1P multiplexer and should not be raised in a TN-1C-to-TN-1C or TN-1P-to-TN-1P system.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-1.
Procedure 2-1 AU-AIS alarm clearing Step 1 Action Check far multiplexer and any intermediate regenerators for cause of AIS.
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 traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
If the alarm is still present, remove the Local loopback and replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
end
EA-Ext_inpn<1-8>
Significance
The external alarm n (where n = 1 to 8) is active. The alarms can be assigned names of up to eight characters. Note: This alarm does not apply to the TN-1P when it is used in the headend subrack.
Impact
Dependant on what the alarm represents.
Consequent alarms/events
None.
Possible causes
External device.
Corrective actions
Investigate external device.
HP-DEG
Significance
The BER of the VC-4 path (B3) BIP-8 error check has exceeded the configurable lower threshold (10-5, 10-6, or 10-7, default 10-5).
Impact
Traffic affecting.

Local Possible LP-DEG alarm. HP source Possible HP-REI alarm. LP source Possible LP-REI alarms.

Local Possible LP-DEG alarm. Far end Possible HP-REI alarm. Possible LP-REI alarms.
Possible causes
Faulty local TN-1C/TN-1P multiplexer. Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-2 HP-DEG alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
If the alarm is still present, remove the Local loopback and replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to step 3.
3 Replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
If the alarm is still present, replace the original far TN-1C/TN-1P multiplexer and escalate the problem.
end
HP-EXC
Significance
The BER of the VC-4 path (B3) BIP-8 error check has exceeded 10-3.
Impact
Traffic affecting.

HP source HP-REI alarm. LP source Possible LP-REI alarms.

Far end HP-REI alarm. Possible LP-REI alarms.
Possible causes
Faulty local TN-1C/TN-1P multiplexer. Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-3 HP-EXC alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
If the alarm is still present, remove the Local loopback and replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 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/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
If the alarm is still present, replace the original far TN-1C/TN-1P multiplexer.
end
HP-FE_QOSV_15M
Significance
One of the far-end HP parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
Consequent alarms/action
None.
Possible causes
Errors on the network.
Corrective action
Investigate network for cause of errors (view performance monitoring logs for additional information).
HP-FE_QOSV_24H
Significance
One of the far-end HP parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
HP-LOM
Significance
An illegal multiframe sequence has been detected in the H4 byte.
Impact
Traffic affecting on unprotected paths. Temporary traffic hit on protected paths if paths switched to aggregate containing alarm.

Note: When the TN-1C is used in a VC-3 only ring, the HP-LOM alarm is not applicable and should be disabled using the User Interface (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403). 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). 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-LOM alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Far end Protected TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected TU paths LP-RDI alarms.
Possible causes
Line errors. Faulty local TN-1C/TN-1P multiplexer. Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-4 HP-LOM alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback at the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
end
HP-PLM
Significance
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, 2 or 13 is expected).
Impact
Traffic affecting if incorrect connection (wrong traffic). Note: Consequent actions for the HP-PLM alarm can be disabled using the UI (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403). 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). Unprotected add/drop TU paths AIS injection on all tributary outputs.
HP source HP-RDI alarm. LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing HP-PLM alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Possible causes
Incorrect connection setup. Settings incorrectly set during configuration (the settings for the TN-1C/TN-1P are not configurable). Faulty local or far TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-5 HP-PLM alarm clearing Step 1 Action 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.
2 If applicable, check the far end HP signal label settings.
If settings are incorrect, reconfigure as necessary. If settings are correct, proceed to step 3.
3 Replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 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/TN-1P multiplexer and proceed to step 4.
end
HP-QOSV_15M
Significance
One of the HP parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
HP-QOSV_24H
Significance
One of the HP parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
HP-RDI
Significance
The VC-4 Path FERF (far end receive failure) 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.
None.
Possible causes
RS-LOS, RS-LOF, MS-EXC, AU-AIS, HP-TIM, HP-PLM, HP-EXC, INT-AU-AIS, or INT-AU-LOP alarm at the far multiplexer.
Corrective actions
Procedure 2-6 HP-RDI alarm clearing Step 1 Action Check far multiplexer for cause of alarm (RS-LOS, RS-LOF, MS-EXC, AU-AIS, HP-TIM, HP-PLM, HP-EXC, INT-AU-AIS, or INT-AU-LOP alarm).
If cause of alarm found, perform the appropriate alarm clearing procedure. If cause of alarm not found, proceed to step 2.
end
HP-REI
Significance
The BER of the FEBE (far end block error) bits in the VC-4 path status byte (G1), indicate that the far multiplexer has detected errors in the VC-4 path that have exceeded the configurable threshold of 10-5, 10-6, or 10-7 (default 10-5).
Impact
None.
None.
Possible causes
HP errors on the network.
Corrective actions
Procedure 2-7 HP-REI alarm clearing Step 1 Action Check far HP path termination for cause of errors (e.g. HP-DEG or HP-EXC alarm) and carry out fault finding procedures for appropriate alarm.
If cause of errors found, perform the appropriate alarm clearing procedure. If cause of errors not found, proceed to Step 2.
end
HP-TIM
Significance
The received string of the VC-4 path trace byte (J1) does not match the expected string.
Impact
Traffic affecting if incorrect connection (wrong traffic). Note: Consequent actions for the HP-TIM alarm can be disabled using the UI (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403). 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). Unprotected add/drop TU paths AIS injection on all tributary outputs.
HP source HP-RDI alarm. LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP path containing HP-TIM alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Possible causes
Incorrect connection setup. Settings incorrectly set during configuration (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/TN-1P multiplexer.
Corrective actions
Procedure 2-8 HP-TIM alarm clearing Step 1 Action Check the system path trace settings at both ends.
If settings are incorrect, reconfigure as necessary. Change the configured expected receive string to match the actual received string. If settings are correct, proceed to step 2.
2 If operating in the Single Fibre Working mode, check for fibre breaks, that is, the output signal is being reflected back to the input of the same TN-1C.
If fibre break detected, perform appropriate actions to repair fibre. If no fibre break detected, proceed to step 3.
3 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 4.
If the alarm clears, the alarm clearing procedures are complete. If the alarm is still present, replace the original local TN-1C/TN-1P multiplexer and proceed to step 5.
end
INT-AU-AIS
Significance
An internal AIS has been detected internally in the H1 and H2 bytes for three consecutive frames.
Impact

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. HP source HP-RDI alarm. 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). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Possible causes
Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original local TN-1C/TN-1P multiplexer and escalate the problem.
INT-AU-LOP
Significance
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

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. HP source HP-RDI alarm. 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). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Possible causes
Corrective actions
Replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original local TN-1C/TN-1P multiplexer and escalate the problem.
INT-HP-Insert_Bus
Significance
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
Traffic affecting.
None.
Possible causes
Corrective actions
Replace the TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
INT-HP-IP_Buffer
Significance
The AU FIFO (first-in-first-out) buffer, which allows the incoming STM-1 signal to be aligned to the local frame, has underflowed or overflowed.
Impact
Traffic affecting.
None. Note: If the alarm persists, protected paths may switch due to HP and LP defects.
Possible causes
Synchronisation problems in network. Incoming STM-1 signal out-of-limits. Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-9
Procedure 2-9 INT-HP-IP_Buffer alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Isolate the TN-1C/TN-1P from the synchronisation perspective (i.e. remove all external source from the hierarchy so that the TN-1C/TN-1P 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 3.
3 Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
If the alarm is still present, remove the Local loopback and replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original local TN-1C/TN-1P multiplexer and escalate the problem. If the alarm clears, remove the Local loopback and proceed to step 4.
continued
Clearing TN-1C/TN-1P equipment alarms 2-35 Procedure 2-9 INT-HP-IP_Buffer alarm clearing (continued) Step 4 Action Replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
end
INT-LP-IP_Buffer
Significance
The FIFO in the mapping/multiplexing direction is in an underflow or overflow state.
Impact
Traffic affecting.
None.
Possible causes
Incoming tributary signal out-of-limits. Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-10 INT-LP-IP_Buffer Step 1 Action Check if tributary input signal is within limits.
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/TN-1P from the synchronisation perspective (i.e. remove all external sources from the hierarchy so that the TN-1C/TN-1P is operating in the holdover mode).
If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem.
end
INT-LP-OP_Buffer
Significance
The FIFO in the demapping/demultiplexing direction is either in the underflow or overflow state.
Impact
Traffic affecting.
None.
Possible causes
Synchronisation problems in network. Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-11 INT-LP-OP_Buffer alarm clearing Step 1 Action Isolate the TN-1C/TN-1P from the synchronisation perspective (i.e. remove all external sources from the hierarchy so that the TN-1C/TN-1P is operating in the holdover mode).
If the alarm is still present, replace the original local TN-1C/TN-1P multiplexer and escalate the problem.
end
INT-NE-Config_Corrupt
Significance
The periodic checksum test on the configuration data held in the non-volatile memory has failed.
Impact
If alternate configuration bank not available, possibly traffic affecting.
If other configuration data bank is available and has been updated, a switch is made to the alternate configuration bank. If alternate configuration data bank not available, factory-set defaults are used.
Possible causes
Non-volatile store corrupt.
Corrective actions
Procedure 2-12 INT-NE-Config_Corrupt alarm clearing Step 1 Action Use the UI to view the configuration bank status.
If both banks contain the latest correct configuration and the multiplexer is operating correctly, no further action is required. If only one configuration bank contains the correct configuration, 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/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
2 Use the UI to commit the configuration to the other bank (see System and Software Administration Procedures, 323-1081-302).
If the commit process fails, replace the TN-1C/TN-1P multiplexer.

Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
continued
Clearing TN-1C/TN-1P equipment alarms 2-39 Procedure 2-12 INT-NE-Config_Corrupt alarm clearing (continued) Step 3 Action If a backup configuration is available, download and switch to backup configuration using the UI. If the backup configuration is acceptable, commit the configuration to the other bank. For details of the UI procedures, refer to System and Software Administration Procedures, 323-1081-302.
If the download, restore or commit process fails, replace the TN-1C/TN-1P multiplexer.
Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
end
INT-NE-RAM_Fail
Significance
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 traffic affecting.
None.
Possible causes
RAM failure on TN-1C/TN-1P multiplexer.
Corrective action
INT-NE-SW_Corrupt
Significance
The checksum of the application code is incorrect.
Impact
None.
None.
Possible causes
Download failure. Spurious software corruption.
Corrective action
Copy the current good software bank to the corrupted bank using the TN-1C/TN-1P UI (see System and Software Administration Procedures, 323-1081-302).
INT-OS-Laser_Test
Significance
The automatic laser shutdown (ALS) circuit has been disabled.
Impact
None.
None.
Possible causes
Laser forced_on from the TN-1C/TN-1P UI.
Corrective actions
Re-enable ALS by setting laser to normal operation from the UI (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403). If the alarm is still present, replace the TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
INT-RS-Tx_Buffer
Significance
The DSPI (dual serial-to-parallel interface) FIFO in the mapping/multiplexing direction is either in the underflow or overflow state.
Impact
Traffic affecting.
None.
Possible causes
Corrective actions
If alarm is persistent, replace the TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
INT-TU-AIS
Significance
An internal AIS has been detected internally in the pointer bytes of the TU.
Impact
Traffic affecting.
Local AIS injection on associated tributary output. LP source (TN-1C) or far end (TN-1P) LP-RDI alarm.
Possible causes
Corrective actions
Replace local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If alarm still present, replace original local TN-1C/TN-1P multiplexer and escalate problem.
INT-TU-LOP
Significance
The internal pointer value in the pointer bytes (V1 and V2 for TN-1P) of the TU is invalid for three consecutive frames.
Impact
Traffic affecting.
Local AIS injection on associated tributary output. LP source (TN-1C) or far end (TN-1P) LP-RDI alarm.
Possible causes
Faulty local TN-1C multiplexer.
Corrective actions
Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If alarm still present, replace original local TN-1C/TN-1P multiplexer and escalate problem.
LP-DEG
Significance
The BER of the BIP-2 (bit-interleaved parity) error check has exceeded the lower configurable threshold: 10-4 or 10-5 (default 10-5) for VC-12 (TN-1C/TN-1P) 10-5 or 10-6 or 10-7 (default 10-5) for VC-3 (TN-1C)
Impact
Traffic affecting.
Path source Possible LP-REI alarm (LP-REI alarm is not configurable to 10-3 (only 10-4 and 10-5).
Possible causes
Errors in network. Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-13 LP-DEG alarm clearing Step 1 Action Check if there are any MS or HP alarms in the network.
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.
If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem.
end
LP-EXC
Significance
The BER of the BIP-2 (VC-12) (TN-1C/TN-1P) or BIP-8 (VC-3) (TN-1C) error check has exceeded 10-3.
Impact
Local Protected (add/drop for TN-1C) TU path Temporary AIS injection on tributary output if protection switching enabled as a consequent action of an LP-EXC 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-EXC alarm. AIS injection on tributary output if LP-EXC is configured to cause consequent actions and protection switching and LP-EXC is received on both paths. Note: If LP-EXC 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 first switch). Unprotected (add/drop for TN-1C) TU path AIS injection on associated tributary output if LP-EXC configured to cause consequent actions. Path source (TN-1C) or far end (TN-1P) Protected TU path LP-RDI alarm if both paths have failed at local multiplexer. LP-REI alarm if LP-EXC is configured not to cause consequent actions. Unprotected TU path LP-RDI alarm if LP-EXC configured to cause consequent actions. LP-REI alarm if LP-EXC is configured not to cause consequent actions. Note: LP-RDI as a consequent action of LP-EXC is configurable by the user (default on).
Possible causes
Errors on network. Faulty local TN-1C/TN-1P multiplexer. Faulty far TN-1C/TN-1P multiplexer.
Corrective actions
Perform the fault finding procedure given in Procedure 2-14.
Procedure 2-14 LP-EXC alarm clearing Step 1 Action Check if there are any MS or HP alarms in the network.
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.
If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem.
end
LP-FE_QOSV_15M
Significance
One of the far-end LP parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
Investigate network for cause of errors (look at performance monitoring logs for additional information).
LP-FE_QOSV_24H
Significance
One of the far-end LP parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
LP-PLM
Significance
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: TN-1C/TN1-P for VC-12s a value of 1 or 2 is expected if the traffic is in the on, auto or standby mode, a value of 0 is expected if the traffic is off. TN-1C for VC-3s a value of 1 or 4 is expected if the traffic is in the on, auto or standby mode, a value of 0 is expected if the traffic is off.
Impact
Traffic affecting.
Local AIS injection on tributary output. LP source (TN-1C) or far end (TN-1P) LP-RDI alarm.
Possible causes
Incorrect traffic settings. Incorrect path connection. Faulty local or far TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-15 LP-PLM alarm clearing Step 1 Action Ensure that the system path configuration at both ends is correct as follows: VC-12s (TN-1C/TN1P) if no traffic expected, both ends should be configured to send a value of 0 (traffic-off). if traffic is expected, both ends should be configured to send a value of 1 or 2 (traffic-on). if no traffic expected, both ends should be configured to send a value of 0 (traffic-off). if traffic is expected, both ends should be configured to send a value of 1 or 4 (traffic-on).
VC-3s (TN-1C)
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/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 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 4.
end
LP-QOSV_15M
Significance
One of the LP parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
LP-QOSV_24H
Significance
One of the LP parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
LP-RDI
Significance
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.
None.
Possible causes
If alarm raised for all tributaries, RS-LOS, RS-LOF, MS-AIS, MS-EXC, AU-AIS, INT-AU-AIS, INT-AU-LOP, HP-TIM, HP-PLM or HP-LOM alarm present at the far multiplexer. If alarm raised for one tributary only, TU-AIS, TU-LOP, INT-TU-AIS, INT-TU-LOP, LP-PLM or LP-EXC alarm present at far path termination.
Corrective actions
Procedure 2-16 LP-RDI alarm clearing Step 1 Action Investigate far multiplexer/path termination for cause of alarm and carry out fault finding procedures for appropriate alarm.
3 4 Replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original far TN-1C/TN-1P multiplexer and escalate the problem.
end
LP-REI
Significance
The BER of the FEBE bits in the V5 byte of the incoming VC-12 indicate that the far station has detected errors in the VC-12 path, exceeding the configurable threshold of 10-3, 10-4, or 10-5 (default 10-5).
Impact
None.
None.
Possible causes
TU errors on network.
Corrective actions
Procedure 2-17 LP-REI alarm clearing Step 1 Action Investigate far path termination for cause of errors and carry out fault finding procedures for appropriate alarm (e.g. LP-DEG alarm).
2 Replace the local TN-1C/TN-P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
If the alarm is still present, replace the original far end TN-1C/TN-1P multiplexer and escalate the problem.
end
MS-AIS
Significance
An AIS has been detected in the K2 byte in the section overhead indicating a failure at the far multiplexer.
Impact

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. HP source MS-RDI and HP-RDI alarms. 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). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Local Protected 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). Unprotected TU paths AIS injection on all tributary outputs.
Far end Protected TU paths MS-RDI and HP-RDI alarms. LP-RDI alarms if both paths have failed at local multiplexer. Unprotected TU paths MS-RDI, HP-RDI and LP-RDI alarms.
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/TN-1P multiplexer and should not be raised in a TN-1C-to-TN-1C or a TN-1P-to-TN-1P system.
Corrective actions
Procedure 2-18 MS-AIS alarm clearing Step 1 Action Check far multiplexer and any intermediate regenerators for cause of AIS.
2 If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1). If the alarm is still present, remove the Local loopback and replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm clears, replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
end
MS-DEG
Significance
The BER of the BIP-24 error check has exceeded the configurable lower threshold (10-5, 10-6, or 10-7, default 10-5).
Impact
Traffic affecting.

Local Possible intermittent HP-DEG and LP-DEG alarms. HP source Possible intermittent HP-REI alarms. LP source Possible intermittent LP-REI alarms.

Local Possible intermittent HP-DEG and LP-DEG alarms. Far end Possible intermittent HP-REI and LP-REI alarms.
Possible causes
Faulty optical fibre/connections. Faulty local TN-1C/TN-1P multiplexer. Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-19 MS-DEG alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
3 Clean the receive optical connections at the local TN-1C/TN-1P multiplexer and verify that the received optical power is in the correct range (see Common procedures on page 3-1).
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.
If the alarm is still present, replace the original TN-1C/TN-1P 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/TN-1P multiplexer and verify that the transmit optical power at the far multiplexer is in the correct range (see Common procedures on page 3-1).
If the transmit optical power is within range, the fault is associated with the optical fibre. Use appropriate methods to isolate fibre fault. If the transmit optical power is not within range, proceed to step 7.
end
MS-EXC
Significance
The BER of the BIP-24 error check has exceeded 10-3.
Impact

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. HP source MS-RDI and HP-RDI alarms. LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing MS-EXC alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Possible causes
Faulty optical fibre/connections. Faulty local TN-1C/TN-1P multiplexer. Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-20 MS-EXC alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
continued
Clearing TN-1C/TN-1P equipment alarms 2-63 Procedure 2-20 MS-EXC alarm clearing (continued) Step 3 Action Clean the receive optical connections at the local TN-1C/TN-1P multiplexer and verify that the received optical power is in the correct range (see Common procedures on page 3-1).
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.
If the alarm is still present, replace the original TN-1C/TN-1P 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/TN-1P multiplexer and verify that the transmit optical power at the far multiplexer is in the correct range (see Common procedures on page 3-1).
end
MS-QOSV_15M
Significance
One of the MS parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
MS-QOSV_24H
Significance
One of the MS parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
MS-RDI
Significance
An RDI 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.
None.
Possible causes
RS-LOS, RS-LOF, MS-AIS, or MS-EXC alarm at the far multiplexer.
Corrective actions
Procedure 2-21 MS-RDI alarm clearing Step 1 Action Check far multiplexer for cause of alarm (RS-LOS, RS-LOF, MS-AIS, or MS-EXC alarm).
end
NE-Card_Fail
Significance
Failure of the on-board application-specific integrated circuit (ASIC) tests or any other hardware tests which are performed on initialisation and subsequently at regular intervals (approximately every 30 seconds).
Impact
May be traffic affecting, depending on the type of failure.
None.
Possible causes
Failure of the one of the on-board ASICs. Hardware checksum failure. Phase-Locked Loop problems. Unrecognised PEC codes (ADM, BP) (for TN-1C).
Corrective actions
TN-1C 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, 323-1081-547, for replacement procedures. TN-1P Replace the TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
NE-Door_Open
Significance
The cover on the TN-1C/TN-1P multiplexer unit has been removed. Note 1: The alarm remains active for approximately 5 minutes once the cover is fitted. Note 2: This alarm does not apply to the TN-1P when it is used in the headend subrack.
Impact
None.
None.
Possible causes
TN-1C/TN-1P cover removed or not fitted correctly. Tab broken on plastic cover. Faulty microswitch.
Corrective actions
If cover removal is 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-22. Note: If the cover is not fitted, the alarm can be disabled either via a hardware jumper (if applicable to hardware) on the connection panel or via the CLUI/Browser.
Procedure 2-22 NE-Door_Open alarm clearing Step 1 Action Check that the plastic tab is not broken on the plastic cover and that the cover is properly fitted.
If the cover is not correctly fitted, refit 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/TN-1P multiplexer. If microswitch is not damaged, escalate the problem.
end
NE-Ext_Card_Out (TN-1C only)

Significance
The tributary extension card is provisioned as equipped but is not physically present.
Impact
Loss of tributary traffic carried by tributary extension card.
TU-AIS injection on all channels that are connected to the tributary extension card.
Possible causes
Tributary extension card removed. System incorrectly configured. Faulty local TN-1C multiplexer.
Corrective actions
Procedure 2-23 NE-Ext_Card_Out alarm clearing Step 1 Action Check if tributary extension card is expected.
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 TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403).
If alarm still present, proceed to step 3.

3 Replace local TN-1C multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
If alarm still present, replace original local TN-1C multiplexer and escalate problem.
end
NE-Fan_Failed (TN-1C only)

Significance
The fan has been detected as faulty (i.e. on the first time it is used). The alarm is only cleared when the fan is proved to be operating or is removed. Note 1: The NE-Fan_Failed alarm is raised after approximately 30 seconds from detecting the condition and remains active for approximately 30 seconds after the cause is removed. Note 2: The NE-Fan_Failed alarm is also applicable to a TN-1P or TN-1P Basestation upgraded with a TN-1C ADM card.
Impact
Possible overheating of TN-1C.
None.
Possible causes
Faulty fan module. 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, 323-1081-547, for replacement procedures.
NE-High_Temp (TN-1C only)

Significance
The NE temperature has exceeded 55C. The alarm is cleared if the temperature falls below 39C. Note: The NE-Fan_Failed alarm is also applicable to a TN-1P or TN-1P Basestation upgraded with a TN-1C ADM card.
Impact
Possible overheating of TN-1C.
If fan is fitted, fan will operate.
Possible causes
Fan module required. Faulty fan module. Ambient temperature too high.
Corrective actions
If fan not fitted, fit fan module. Refer to the Installation Procedures, 323-1081-200, for installation procedures. If fan fitted, use UI to force fan on. If fan does not operate, replace fan module. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
NE-Minor_Card_Mismatch (TN-1C only)

Significance
The tributary extension card belongs to the same family but is a different type, that is, the same Major type but a different Minor type. A subset of ports are supported, these are common to the actual card and the equipped card. If more ports are equipped than physically exist, these are in the equipped - not present state.
Impact
Possible loss of tributary traffic carried by tributary extension card.
The Equipped - not present state implies: TU-AIS injection on all channels connected to those ports. The ports are invalidated from being a synchronisation source. All PMs on those ports are Unavailable.
Possible causes
Tributary extension card incorrectly fitted. System incorrectly configured. Faulty local TN-1C multiplexer.
Corrective actions
Procedure 2-24 NE-Minor_Card_Mismatch alarm clearing Step 1 Action Check what tributary extension card/connector panel should be fitted.
If the correct tributary extension card is not fitted, fit the correct tributary extension card in the TN-1C. If alarm still present, proceed to step 3. If the correct tributary extension card is fitted, proceed to step 2.
2 Provision the equipment to equip the tributary extension card of the correct type (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403).

end
NE-Unexpected_Card (TN-1C only)

Significance
The tributary extension card is physically present but is provisioned as unequipped.
Impact
Loss of tributary traffic carried by tributary extension card.
None.
Possible causes
Tributary extension card incorrectly fitted. System incorrectly configured. Faulty local TN-1C multiplexer.
Corrective actions
Procedure 2-25 NE-Unexpected_Card alarm clearing Step 1 Action Check if tributary extension card is expected.
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 TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403).

end
NE-Wrong_Card (TN-1C only)

Significance
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. Loss of tributary traffic carried by tributary extension card. TU-AIS injection on all channels that are connected to the tributary extension card.
Impact

None.
Possible causes
Wrong tributary extension card fitted. System incorrectly configured. Faulty local TN-1C multiplexer. Unrecognised PEC code (extension card).
Corrective actions
Procedure 2-26 NE-Wrong_Card alarm clearing Step 1 Action Check what tributary extension card/connector panel should be fitted.
If the correct tributary extension card is not fitted, fit the correct tributary extension card in the TN-1C/TN-1P. If alarm still present, proceed to step 3. If the correct tributary extension card is fitted, proceed to step 2.
2 Provision the equipment to equip the correct tributary extension card (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403).

3 Replace local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
If alarm still present, replace original local TN-1C/TN-1P multiplexer and escalate problem.
end
OS-Laser_Bias_High
Significance
The laser bias current is out-of-limits, indicating that the laser performance has degraded and that the laser end-of-life is near.
Impact
Non-traffic affecting. Note: The alarm indicates that a maintenance action is needed, otherwise an Optical Source Low Power condition will occur, which is service affecting.
None.
Possible causes
Aging of laser.
Corrective actions
OS-Laser_Shutdown
Significance
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
If shutdown by a RS-LOS alarm, automatic laser shutdown mechanism initiated. Laser restart attempted every 70 seconds until RS-LOS 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-LOS 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-LOS or OS-Optical_Power_High alarm.
OS-Optical_Power_High
Significance
The optical output power has exceeded the nominal output level by more than 4 dB, or has exceeded +4 dBm within 600 ms.
Impact
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/TN-1P transmit circuit.
Corrective actions
PPI-AIS
Significance
An AIS has been detected in the incoming 2 Mbit/s signal. PPI-AIS is detected for either unframed, framed or cyclic redundancy check (CRC) 2 Mbit/s signals. The monitoring of the alarm may be disabled by the user. Note 1: .If the 2 Mbit/s signal is unstructured (e.g. does not conform to ITU-T recommendation G732), AIS may be a valid signal. If the port is configured for an unframed signal, monitoring of the alarm must be disabled. Note 2: This alarm is not raised for 34/45 Mbit/s tributaries for the TN-1C.
Impact
Invalidates the synchronisation source.
None.
Possible causes
AIS being generated by preceding 2 Mbit/s equipment.
Corrective action
If the signal is structured, investigate preceding equipment for the cause of AIS. If the signal is unstructured, reconfigure the port for an unframed signal (refer to the TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403 for details).
PPI-Continuity_Test
Significance
A continuity test is in progress or is being incorrectly reported as being in progress.
Impact
A continuity test overwrites all signals on the tributary to which it is applied.
None.
Possible causes
Continuity test is applied. Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedures given in Procedure 2-27.
Procedure 2-27 PPI-Continuity_Test alarm clearing Step 1 Action Establish using UI commands whether a continuity test is in progress.
If the test status is active, a continuity test is in progress. Stop the Continuity test if it is not required. Proceed to step 2. If no test is active, proceed to step 2.
2 If the alarm is still present, replace the local TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem.
end
PPI-CRC_QOSV_15M
Significance
One of the tributary, framed with CRC, parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-CRC_QOSV_24H
Significance
One of the tributary, framed with CRC, parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-CV_QOSV_15M
Significance
One of the tributary code violation parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-CV_QOSV_24H
Significance
One of the tributary code violation parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-DEG
Significance
The BER of the code violations in the incoming tributary signal has exceeded 10-5.
Impact
Traffic affecting.
None.
Possible causes
Errored input signal. Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-28 PPI-DEG alarm clearing Step 1 Action Investigate preceding 2 Mbit/s (or 34 Mbit/s or 45 Mbit/s for TN-1C) equipment for cause of errors.
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/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem. If the alarm clears, remove the external loopback and escalate problem.
end
PPI-EXC
Significance
The BER of the code violations in the incoming tributary signal has exceeded 10-3.
Impact
Traffic affecting.
None.
Possible causes
Errored input signal. Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-29 PPI-EXC alarm clearing Step 1 Action Investigate preceding 2 Mbit/s (or 34 Mbit/s or 45 Mbit/s for TN-1C) equipment for cause of errors.
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/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem. If the alarm clears, remove the external loopback and escalate problem.
end
PPI-Frm_QOSV_15M
Significance
One of the tributary framed parameter counts for the 15 minute performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-Frm_QOSV_24H
Significance
One of the tributary framed parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-LOF
Significance
The G.704 frame synchronisation has been lost. Note: This alarm is not raised for 34/45 Mbit/s tributaries on the TN-1C. or for 2 Mbit/s unframed tributaries.
Impact
Traffic affecting.
None.
Possible causes
Errored input signal.
Corrective actions
Investigate preceding 2 Mbit/s equipment for a valid signal.
PPI-LOM
Significance
An illegal multiframe sequence has been detected. Note: This alarm is not raised for 34/45 Mbit/s tributaries on the TN-1C or for 2 Mbit/s unframed and framed tributaries.
Impact
Traffic affecting.
None.
Possible causes
Errored input signal.
Corrective actions
Investigate preceding 2 Mbit/s equipment for a valid signal.
PPI-Loopback_On
Significance
A loopback has been applied or is being incorrectly reported as being applied.
Impact
A loopback blocks all signals on the tributary to which it is applied.
None.
Possible causes
A loopback is applied. Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-30 PPI-Loopback_On alarm clearing Step 1 Action Establish using UI commands whether a loopback is applied.
If a loopback is active and is not required, remove it using UI commands. Proceed to step 2. If no loopback is active, proceed to step 2.
end
PPI-LOS
Significance
Loss of the tributary input signal, raised if: 2 Mbit/s HDB3 tributary: no marks (ones or violations) are detected for 11 clock periods (TN-1C/TN-1P). 34 Mbit/s HDB3 tributary: input is low for 256 bit periods (TN-1C only). 45 Mbit/s B3ZS tributary: no transitions for 200 bit periods (TN-1C only).
Impact
Traffic affecting.
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 configurable by the user (default Tx Trib AIS). Note 2: If TU AIS is configured as a consequence action of PPI-LOS, TU-AIS is transmitted on both aggregates of a protected path. At the far multiplexer, TU AIS may be detected on the working path first, 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 first, causing a path protection switch at the far multiplexer.
Possible causes
Input connector not properly terminated. Preceding equipment failure. Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-31 PPI-LOS alarm clearing Step 1 Action If the tributary is a 2 Mbit/s signal (TN-1C/TN-1P), use the UI to check that the 2 Mbit/s port is configured for the correct impedance (75 or 120 ).
If the tributary is a 34 Mbit/s (TN-1C only) or 45 Mbit/s (TN-1C only) signal, use the UI to check that the port is configured for the correct bit rate (34 Mbit/s or 45 Mbit/s)
Refer to the TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403 for details.
If the port is configured incorrectly, reconfigure as appropriate. If the port is correctly configured, 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 verified by connecting the cable to the spare port. If a signal is present, a PPI-Unexp_Signal alarm will be raised for the spare 2 Mbit/s port.
For TN-1C 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.
If the alarm is still present, replace the original local TN-1C/TN-1P multiplexer and escalate the problem
end
PPI-TF
Significance
The output tributary signal has fallen below a predefined threshold.
Impact
Loss of 2 Mbit/s (or 34/45 Mbit/s for TN-1C) traffic output.
None.
Possible causes
Corrective actions
Procedure 2-32 PPI-TF alarm clearing Step 1 Action Ensure that the 2 Mbit/s (or 34/45 Mbit/s for TN-1C) traffic 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/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem.
end
PPI-TX_QOSV_15M
Significance
One of the tributary output parameter counts for the 15 minutes performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-TX_QOSV_24H
Significance
One of the tributary output parameter counts for the 24 hour performance monitoring period has exceeded the configurable threshold.
Impact
None.
None.
Possible causes
Corrective action
PPI-Unexp_Signal
Significance
A 2 Mbit/s (or 34/45 Mbit/s for TN-1C) signal has been detected on a tributary which is configured not to expect traffic (i.e. traffic off or traffic auto without a connection). A signal has been detected on a tributary which is configured as traffic standby. Traffic is carried by the tributary in this state.
Impact
None.
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. No consequent actions are provided when the traffic state is auto. Note: Tx Trib AIS/TU AIS is configurable by the user (default Tx Trib AIS).
Possible causes
Cable mis-connection/system configuration. A signal is detected on a tributary which is configured as traffic standby.
Corrective actions
If a 2 Mbit/s (or 34/45 Mbit/s for TN-1C) signal is expected on this port, reconfigure system (i.e. turn traffic on or auto for port). If a 2 Mbit/s (or 34/45 Mbit/s for TN-1C) signal is not expected on this port, check cable connections to ensure that cables are connected to the correct input terminations.
PS-Battery_Low
Significance
The battery voltage has dropped below 21 V 0.5 V, indicating that only a few minutes of operation remain. Note 1: This alarm is only applicable when using Nortel Networks TN-1C/TN-1P Power Supply Unit. Note 2: This alarm does not apply to the TN-1P when it is used in the Headend subrack.
Impact
Imminent traffic loss.
None.
Possible causes
a.c. mains failure. Input connector not properly connected. Faulty power unit.
Corrective action
Perform the alarm clearing procedures detailed in Procedure 2-33.
Procedure 2-33 PS-Battery_Low alarm clearing Step 1 Action Check if a PS-Power_Fail alarm is present.
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/TN-1P Power Supply Unit batteries.
end
PS-Door_Open
Significance
The cover on the TN-1C/TN-1P Power Supply Unit (PSU) has been removed. Note 1: The alarm remains active for approximately 5 minutes once the cover is fitted. Note 2: On some versions of the TN-1C, the alarm will not be raised if the PS-Door_Open jumper is shorted. Note 3: This alarm does not apply to the TN-1P when it is used in the headend subrack.
Impact
None.
None.
Possible causes
TN-1C/TN-1P PSU cover removed or not correctly fitted. Tab broken on plastic cover. Faulty microswitch.
Corrective actions
Note: If the Nortel Networks PSU is not being used, check that the alarm is disabled on the TN-1C/TN-1P (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-34.
Clearing TN-1C/TN-1P equipment alarms 2-99 Procedure 2-34 PS-Door_Open alarm clearing Step 1 Action Check that the plastic tab is not broken on the plastic cover and that the cover is properly fitted.
If the cover is not correctly fitted, refit 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 the microswitch is damaged, replace the PSU. If the microswitch is not damaged, proceed to step 3.
3 Replace the d.c./alarm cable between the TN-1C/TN-1P and the PSU.
If the alarm clears, no further action is required. If the alarm is still present, replace the PSU.
end
PS-Power_Fail
Significance
The a.c. mains supply or the external charger to the TN-1C/TN-1P Power Supply Unit has failed (fallen below set level). Note 1: This alarm is only applicable when using a Nortel Networks TN-1C/TN-1P Power Supply Unit. Note 2: This alarm does not apply to the TN-1P when it is used in the headend subrack.
Impact
None immediately. Minimum 3 hours of operation is available from battery backup.
None.
Possible causes
a.c. mains failure. a.c. fuse blown. Input connector not properly connected. Faulty TN-1C/TN-1P Power Supply Unit.
Corrective action
Perform the alarm clearing procedures detailed in Procedure 2-35.
Procedure 2-35 PS-Power_Fail alarm clearing Step 1 2 3 Action Check that the a.c. mains connector is properly connected. Re-connect the connector if required. If the alarm is still present, proceed to step 2. Check a.c. fuse, replace if blown.
If fuse blows again, proceed to step 4.

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/TN-1P Power Supply Unit. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures.
end
Qecc-Comms_Fail
Significance
Communication over the Embedded Control Channel (ECC) has been lost with the adjacent multiplexer on a specific STM-1 link.
Impact
Non-traffic affecting. Inter-site data communications are unavailable.
None.
Possible causes
Faulty local or far end TN-1C/TN-1P multiplexer. Remote or local aggregate loopback on the local or far end multiplexer. If the alarm is temporary, cold or warm restart on the local or far TN-1C/TN-1P multiplexer.
Corrective actions
If the alarm is persistent, perform the alarm clearing procedure given in Procedure 2-36.
Procedure 2-36 Qecc-Comms_Fail alarm clearing Step 1 Action Disable faulty link at the local TN-1C/TN-1P by disconnecting optical fibres and then reconnecting them.
If the alarm clears, report the occurrence (no other action is required). If the alarm is still present, proceed to step 2.
2 Reboot the software using a cold restart from the UI.
If the alarm clears, report the occurrence (no other action is required). If the alarm is still present, proceed to step 3.
If the alarm still present, replace the original local TN-1C/TN-1P multiplexer and proceed to step 4. If the alarm clears, the alarm clearing procedures are complete.
4 Replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original far TN-1C/TN-1P multiplexer.
end
RS-LOF
Significance
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

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. HP source MS-RDI and HP-RDI alarms. LP path termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing RS-LOF alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms. LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Far end Protected TU paths MS-RDI and HP-RDI alarms. LP-RDI alarms if both paths have failed at local multiplexer. Unprotected TU paths MS-RDI, HP-RDI and LP-RDI alarms
Possible causes
Invalid incoming STM-1 signal. Faulty local or remote TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-37 RS-LOF alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
continued
Clearing TN-1C/TN-1P equipment alarms 2-105 Procedure 2-37 RS-LOF alarm clearing (continued) Step 3 Action Perform a Local loopback on the appropriate aggregate at the far TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
If an RS-LOF alarm is present at the far multiplexer, remove the Local loopback and replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance Procedures, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem. If an RS-LOF 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/TN-1P multiplexer and verify that the received optical power is in the correct range (see Common procedures on page 3-1).
5 Clean the transmit optical connections at the far TN-1C/TN-1P multiplexer and verify that the transmit optical power at the far TN-1C/TN-1P multiplexer is in the correct range (see Common procedures on page 3-1).
end
RS-Loopback_On
Significance
A loopback has been applied or is being incorrectly reported as being applied.
Impact
A loopback blocks all signals on the aggregate to which it is applied.
None.
Possible causes
A loopback is applied. Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-38 RS-Loopback_On alarm clearing Step 1 Action Establish using UI commands whether a loopback is applied.
If a loopback is active, remove it using UI commands. Proceed to step 2. If no loopback is active, proceed to step 2.
end
RS-LOS
Significance
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

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). Unprotected add/drop TU paths AIS injection on all tributary outputs. Laser shutdown.
HP source MS-RDI and HP-RDI alarms. LP termination Protected add/drop TU paths TU-AIS alarms. If TUs switched to HP containing RS-LOS alarm, protection switch to other aggregate (if valid). Unprotected add/drop TU paths TU-AIS alarms.
LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Local Protected 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). Unprotected TU paths AIS injection on all tributary outputs. Laser shutdown.
Possible causes
Fibre break/bad termination. Transmitter failure at far TN-1C/TN-1P multiplexer. Receiver failure on local TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-39 RS-LOS alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback on the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1). Use the UI to issue a laser restart command.
continued
Clearing TN-1C/TN-1P equipment alarms 2-109 Procedure 2-39 RS-LOS alarm clearing (continued) Step 3 Action Clean the receive optical connections at the local TN-1C/TN-1P multiplexer and verify that the received optical power is in the correct range (see Common procedures on page 3-1).
If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem. If the alarm clears, the alarm clearing procedures are complete.
end
RS-Realign_Phase
Significance
The STM-1 processor has realigned to a new phase without going out of frame alignment.
Impact
Possible traffic hit.
None.
Possible causes
Faulty local or remote TN-1C/TN-1P multiplexer.
Corrective actions
If the alarm is persistent, perform the alarm clearing procedure given in Procedure 2-40.
Procedure 2-40 RS-Realign_Phase alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Perform a Local loopback at the appropriate aggregate at the local TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
3 Perform a Local loopback on the appropriate aggregate at the far TN-1C/TN-1P multiplexer (see Common procedures on page 3-1).
If an 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, 323-1081-547, for replacement procedures. If the alarm is still present, replace the original TN-1C/TN-1P multiplexer and escalate the problem. If an RS-Realign_Phase alarm is not present at the far multiplexer, remove the Local loopback and proceed to step 4.
continued
Clearing TN-1C/TN-1P equipment alarms 2-111 Procedure 2-40 RS-Realign_Phase alarm clearing (continued) Step 4 Action Clean the receive optical connections at the local TN-1C/TN-1P multiplexer and verify that the received optical power is in the correct range (see Common procedures on page 3-1).
If the transmit optical power is within range, the fault is associated with the optical fibre. Use appropriate methods to isolate fibre fault. If the transmit optical power is not within range, proceed step 6.
end
SYNC-Ext_Sync_LOS (TN-1C only)

Significance
The external synchronisation source has failed. Note 1: The external source must be in the synchronisation hierarchy for the alarm to be raised. Note 2: The SYNC-Ext_Sync_LOS alarm is also applicable to a TN-1P or TN-1P Basestation upgraded with a TN-1C ADM card.
Impact
None.
None.
Possible causes
Input connector not properly terminated. External synchronisation source failure. Faulty TN-1C multiplexer.
Corrective action
Procedure 2-41 SYNC-Ext_Sync_LOS alarm clearing Step 1 Action Check that the external synchronisation input connector is properly connected.
If the connector is not properly connected, re-insert connector. If the connector is properly connected, go to step 2.
2 Check that a valid signal is present at the output of the station cable.
If a valid signal is not present, check interconnecting cable and external synchronisation source If a valid signal is present, go to step 3.
3 Escalate problem or replace TN-1C. Refer to the Module Replacement Procedures, 323-1081-547, for replacement procedures.
end
SYNC-Source_Fail
Significance
The synchronisation source has become invalid.
Impact
None.
None.
Possible causes
Loss of selected synchronisation signal. Receipt of AIS on aggregate selected as synchronisation source. Source out-of-limits. EXC on selected source (see Note). Loss of frame alignment on selected STM signal (see Note). HP-TIM alarm present. Note: EXC, LOF and HP-TIM are user configurable criteria for synchronisation source switching.
Corrective actions
Procedure 2-42 SYNC-Source_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).
If the source is out-of-limits, fix the source frequency, then use the UI to clear the out-of-limits alarm (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403). If the source is not out-of-limits, proceed to step 2
2 Investigate the cause of the source failure.
If the cause is identified, perform the alarm clearing procedures for the appropriate alarm. When the synchronisation source is recovered, the SYNC-Source_Fail alarm clears.
If the alarm is still present, escalate the problem.
end
SYNC-Source_Out_of_Limits
Significance
Loss of synchronisation signal.
Impact
None.
None.
Possible causes
This alarm is raised against the port in the SS Hierarchy that the PLL fails to lock to.
Corrective actions
Verify that if control_ss_hierarchy_change is called and port with Out Of Limits alarm is left out from the SS Hierarchy, the alarm is cleared. Synchronisation source out of limits requires manual clearing. Perform the alarm clearing procedure given in Procedure 2-43.
Procedure 2-43 SYNC-Source_Out_of_Limits alarm clearing Step 1 2 Action Use the UI to call ss_defect_status_update function to view the status, and control_ss_hierarchy_change function to clear the Out Of Limits alarm. Verify that if function ss_defect_status_update is called with Out Of Limits alarm, it raises or clears the alarm according to the supplied parameters (ports and status). This alarm is cleared only if the port is taken out from the SS Hierarchy or by a user command (~ m o s c). If the alarm is still present, escalate the problem.
end
SYNC-Src_Not_Primary
Significance
The primary synchronisation source is not currently selected.
Impact
None.
None.
Possible causes
Failure of primary source. Manual switch away from primary source.
Corrective action
Investigate primary source for possible faults/synchronisation source switching actions.
SYNC-SSMB_Unstable
Significance
The SYNC-SSMB_Unstable alarm defects are active against the aggregate, its QL is not read, considered as 0, treated as 15 and reported as unknown.
Impact
None
None.
Possible causes
This alarm is raised when the QL of aggregate is not stable (S1 defect is active). This alarm is raised only if SSM_mode=ON and only if the aggregate is in the SS Hierarchy.
Corrective action
Procedure 2-44 SYNC-SSMB_Unstable alarm clearing Step 1 Action Use the UI (ss_ssm_aggr_rx_ql_change) to change the source. (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403).
If the alarm is not cleared, proceed to step 2

2 Use control_ss_ssm_select to trigger selection of new SS.
If the cause is identified, perform the alarm clearing procedures for the appropriate alarm. When the synchronisation source recovers or the synchronisation source changes, the SYNC-SSMB_Unstable alarm clears.
end
SYNC-Holdover
Significance
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.
None.
Possible causes
No valid external synchronisation sources available. Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Procedure 2-45 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 the alarm. If synchronisation is non-revertive, perform a manual switch back to the required source. If the multiplexer cannot synchronise to any valid source, proceed to step 2.
2 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). If the SS_OUT_OF_LIMITS is present, clear the alarm. Refer to TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 or TN-1C/TN-1P Browser User Interface Guide, 323-1081-403.
Note: The SS_OUT_OF_LIMITS alarm does not appear on the Active Alarm list. The SS_OUT_OF_LIMITS alarm is masked by the Sync Holdover alarm and must be checked and cleared, see step 2.
end
TU-AIS
Significance
An AIS has been detected in the pointer bytes of the TU (V1 and V2 pointer bytes for TN-1P).
Impact
Traffic affecting on unprotected paths. Temporary traffic hit on protected paths if paths switched to the aggregate containing the alarm.

Local Protected add/drop TU path Temporary AIS injection on the associated tributary output if switched to the aggregate containing the alarm. If paths switched to the aggregate containing the alarm, protection switch to the other aggregate (if valid). Unprotected add/drop TU path AIS injection on the associated tributary output.
LP source Protected add/drop TU path LP-RDI alarm if both paths have failed at local multiplexer. Unprotected add/drop TU path LP-RDI alarm.

Local Protected TU path Temporary AIS injection on the associated tributary output if switched to the aggregate containing the alarm. If paths switched to the aggregate containing the alarm, protection switch to the other aggregate (if valid). Unprotected TU path AIS injection on the associated tributary output. Far end Protected TU path LP-RDI alarm if both paths have failed at the local multiplexer. Unprotected TU path LP-RDI alarm.
Possible causes
TU AIS being generated by another multiplexer on the network.
Corrective actions
Procedure 2-46 TU-AIS alarm clearing Step 1 Action Is traffic expected on the indicated channel.
If traffic is expected, proceed to step 2. If traffic is not expected, use the UI to set the channel to Traffic Off (this will disable the alarm).
2 Investigate network (LP path source, far end and intermediate locations) for cause of AIS (e.g. PPI-LOS or PPI-Unexp_Signal alarm at far multiplexer or alarms that cause pass-through TU-AIS injection).
end
TU-LOP
Significance
The pointer value in the pointer bytes (V1 and V2 for TN-1P) of the TU is invalid for three consecutive frames.
Impact

Local Through path TU-AIS injection on associated TU. Protected add/drop TU path Temporary AIS injection on the associated tributary output if switched to the aggregate containing the alarm. If paths switched to the aggregate containing the alarm, protection switch to the other aggregate (if valid). Unprotected add/drop TU path AIS injection on the 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). Unprotected add/drop TU paths TU-AIS alarms.
LP source Protected add/drop TU paths LP-RDI alarms if both paths have failed at local multiplexer. Unprotected add/drop TU paths LP-RDI alarms.

Local Protected TU path Temporary AIS injection on the associated tributary output if switched to the aggregate containing the alarm.
If paths switched to the aggregate containing the alarm, protection switch to the other aggregate (if valid). Unprotected TU path AIS injection on the associated tributary output. Far end Protected TU path LP-RDI alarm if both paths have failed at the local multiplexer. Unprotected TU path LP-RDI alarms.
Possible causes
Faulty local TN-1C/TN-1P multiplexer. Faulty far TN-1C/TN-1P multiplexer. Incorrect connection settings (e.g. VC-3 against a VC-12 connection).
Corrective actions
Procedure 2-47 TU-LOP alarm clearing Step 1 2 Action If the route is protected, ensure that the traffic is switched to the other aggregate port. Check that the correct network connection settings have been made.
If network connection settings are incorrect, correct as necessary. If network connection settings are correct, proceed to step 3.
end
end of chapter
3-1
Common procedures
3-
This chapter provides a list of common task procedures to which the user is referred when performing certain alarm clearing procedures.
Nortel TN-1C/TN-1P
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 fibre. Invisible laser light can blind. Keep all optical connectors capped. Ensure that the far end of the fibre 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, flakes, or even fibres (from clothes or hair). Grease appears as smears or blobs and is most commonly introduced from the finger tips. The procedures for cleaning optical plugs and optical couplers are described in Procedure 3-1 and Procedure 3-2.
Common procedures 3-3 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 fibre. The fibre 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 fibre, 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 (finger 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
6 7
Procedure 3-2 Cleaning an optical coupler Step 1 2 3 4 5 Action Inspect and, if necessary, proceed with step 2 to step 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
Optical output power measurement

WARNING
Avoid direct exposure to laser beam or fibre. Invisible laser light can blind. Keep all optical connectors capped.
The procedure for measuring the optical output power of TN-1C/TN-1P equipment is given in Procedure 3-3. Note: The procedure assumes that the Browser user interface (UI) is used. The procedure is similar if the Command Line UI is used (see TN-1C/ TN-1P Command Line User Interface Guide, 323-1081-401 for details)
Procedure 3-3 Optical output power measurement Step 1 2 3 4 Action Connect the Craft Access Terminal (CAT) to the TN-1C/TN-1P . Login to the TN-1C/TN-1P by entering your user name, password and identification in the login fields. Select the Submit button. The UI main menu is displayed. Turn the laser off (forced_off) by selecting: Config Laser state Forced off 5 A dialogue is displayed with a drop down selector enabling you to select the required laser to turn off. Select the required laser and then select the Submit button. 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. Use the UI to allow a laser force on (allow_force) by selecting: Config Laser state Allow_force 9 A dialogue is displayed with a drop down selector enabling you to select the required laser. Select the required laser and then select the Submit button.
continued
6 7 8
Common procedures 3-5 Procedure 3-3 Optical output power measurement (continued) Step 10 Action Use the UI to turn the laser on (forced_on) by selecting: Config Laser state Forced on 11 A dialogue is displayed with a drop down selector enabling you to select the required laser to turn on. Select the required laser and then select the Submit button. Measure the optical output power of the unit. The limits are: S1.1 8 dBm to 15 dBm. L1.1 0 dBm to 5 dBm. L1.2 0 dBm to 5 dBm. 13 Use the UI to turn the laser off (forced_off) by selecting: Config Laser state Forced off 14 A dialogue is displayed with a drop down selector enabling you to select the required laser to turn off. Select the required laser and then select the Submit button. 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 condition by selecting: Config Laser state Normal 18 A dialogue is displayed with a drop down selector enabling you to select the required laser to return to the normal operating condition. Select the required laser and then select the Submit button. Logout of the UI by selecting the Logout button. Disconnect the Craft Access Terminal from the TN-1C/TN-1P .
end
12
15 16 17
19 20
Optical input power measurement

WARNING
Avoid direct exposure to laser beam or fibre. Invisible laser light can blind. Keep all optical connectors capped.
The procedure for measuring the optical input power for TN-1C/TN-1P equipment is given in Procedure 3-4. Note: The procedure assumes that the Browser UI is used. The procedure is similar if the Command Line UI is used (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 for details).
Procedure 3-4 Optical input power measurements Step 1 2 3 Action Open a UI session with the remote TN-1C/TN-1P . Login to the TN-1C/TN-1P by entering your user name, password and identification in the login fields. Select the Submit button. Turn the laser off (forced_off) at the remote TN-1C/TN-1P by selecting: Config Laser state Forced off 4 A dialogue is displayed with a drop down selector enabling you to select the required laser to turn off. Select the required laser and then select the Submit button.
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 6 Disconnect the receive optical fibre from the receive optical input and connect the optical receive fibre to the input of an optical power meter. Use the UI to allow a laser force on (allow_force) at the far end by selecting: Config Laser state Allow_force 7 A dialogue is displayed with a drop down selector enabling you to select the required laser. Select the required laser and then select the Submit button.
continued
Common procedures 3-7 Procedure 3-4 Optical input power measurements (continued) Step 8 Action Use the UI to turn the laser on (forced_on) at the far end by selecting: Config Laser state Forced on 9 A dialogue is displayed with a drop down selector enabling you to select the required laser to turn on. Select the required laser and then select the Submit button. Measure the optical input power from the fibre. The limits are: S1.1 0 dBm to 28 dBm. L1.1 3 dBm to 34 dBm. L1.2 3 dBm to 34 dBm. 11 Turn the laser off (forced_off) at the far by selecting: Config Laser state Forced off 12 A dialogue is displayed with a drop down selector enabling you to select the required laser to turn off. Select the required laser and then select the Submit button. Disconnect the receive optical fibre from the optical power meter and reconnect the fibre to the receive optical input connector. Use the UI to return the laser at the far end to the normal operating state by selecting: Config Laser state Normal 15 A dialogue is displayed with a drop down selector enabling you to select the required laser to return to the normal operating condition. Select the required laser and then select the Submit button. Logout of the UI by selecting the Logout button.
end
10
13 14
16
Applying/clearing loopbacks
The TN-1C/TN-1P has a number of loopback facilities which can be used in the alarm clearing/maintenance procedures, see Diagnostic tools on page 4-1 for details. CAUTION
STM-1 local loopback
Activating the STM-1 local loopback will cause loss of traffic.

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 TN-1C/TN-1P loopbacks is given in Procedure 3-5. Note: The procedure assumes that the Browser is used. The procedure is similar is the Command Line User Interface is used (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 for details).
Procedure 3-5 Applying/removing TN-1C/TN-1P loopbacks Step 1 2 3 Action Open a UI session with the TN-1C/TN-1P via the CAT or the element controller EC-1. Login to the TN-1C/TN-1P by entering your user name, password and identification in the login fields. Select the Submit button. Access the loopback menu by selecting: Diagnostic Loopback 4 To apply a local loopback select: Set_remote To apply a local loopback select: Set_local
Note: Whenever a loopback is applied, a loopback alarm is raised (RS-Loopback_on or PPI-Loopback_on).

continued
Common procedures 3-9 Procedure 3-5 Applying/removing TN-1C/TN-1P loopbacks (continued) Step Action
A dialogue is displayed that is divided into two panes. The left hand pane has two radio buttons enabling you to select an aggregate or tributary loopback. The right hand pane provides a drop down selector when the aggregate radio button is selected or a text entry field for the tributary port if the tributary radio button is selected. The dialogue also provides a Submit and a Cancel button.
5 To apply an aggregate loopback, select the aggregate radio button. The right hand pane is refreshed with a drop down selector. Select the required aggregate and then select the Submit button. To apply a tributary loopback, select the tributary radio button. The right hand pane is refreshed with a text entry field. Enter the required tributary in the following format: S<m>-<n> for tributaries <m> is the slot number 1 or 2, (1 only for TN-1P) <n> is the tributary port 1 to 8 (TN-1C 2 Mbit/s tributary ports) <n> is the tributary port 1 or 2 (TN-1C 34/45 Mbit/s tributary ports) <n> is the tributary port 1 to 4 (TN-1P 2 Mbit/s tributary ports) 6 To clear a loopback select: Clr
A dialogue is displayed that is divided into two panes. The left hand pane has two radio buttons enabling you to select an aggregate or tributary loopback. The right hand pane provides a drop down selector when the aggregate radio button is selected or a text entry field for the tributary port if the tributary radio button is selected. The dialogue also provides a Submit and a Cancel button.
7 To clear an aggregate loopback, select the aggregate radio button. The right hand pane is refreshed with a drop down selector. Select the required aggregate and then select the Submit button. S<m>-<n> for tributaries <m> is the slot number 1 or 2, (1 only for TN-1P) <n> is the tributary port 1 to 8 (TN-1C 2 Mbit/s tributary ports) <n> is the tributary port 1 or 2 (TN-1C 34/45 Mbit/s tributary ports) <n> is the tributary port 1 to 4 (TN-1P 2 Mbit/s tributary ports) 8 Logout of the UI by selecting the Logout button.
end
end of chapter
4-1
Diagnostic tools
This section details the diagnostic tools available on the TN-1C/TN-1P multiplexer for maintenance purposes, namely: Loopbacks Tributary Test Pattern Generator and Detector
44
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 (near-end or loop to mux) loopback can be performed on a selected STM-1 link, i.e. the outgoing (towards the optics) STM-1 data is routed back to the STM-1 receiver on the same link, as well as being transmitted towards the line. While an STM-1 local loopback is in operation, an RS-Loopback_On alarm is raised. This loopback should be activated with caution as it causes traffic loss. An STM-1 local loopback is not permitted in an unprotected system. It is also not permitted on both aggregates in a protected system (see Figure 4-1). CAUTION
ECC communication loss
An STM-1 local loopback must not be activated remotely as it leads to ECC communication loss and a site visit will be required to remove the loopback condition. CAUTION
Loss of traffic
An STM-1 local loopback causes traffic loss, the user should ensure that the aggregate to be looped back is not carrying traffic.
4-2 Diagnostic tools
Note: When a local STM loopback is raised, the TN-1C/TN-1P detects a temporary loss of signal during the switch and raises an RS-LOS alarm (which will be cleared after the switch). This causes PPS on all tributaries fed from this aggregate. STM-1 remote loopback (Loop to Line) A remote (far-end or loop to line) loopback can be performed on a selected STM-1 link, i.e. the incoming (from the optics) STM-1 data is routed back to the optical connections on the same link, as well as being transmitted towards the line. While an STM-1 remote loopback is in operation, an RS-Loopback_On alarm is raised (see Figure 4-1). CAUTION
ECC communication loss
An STM-1 local loopback must not be activated remotely as it leads to ECC communication loss and a site visit will be required to remove the loopback condition. CAUTION
Loss of traffic
An STM-1 local loopback causes traffic loss, the user should ensure that the aggregate to be looped back is not carrying traffic. Note: When activating the STM-1 remote loopback, a temporary RS-LOS 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 2 Mbit/s (or 34/45 Mbit/s for TN-1C) tributary loopback 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). This loopback is implemented in the tributary line driver in Release 3 hardware and in the tributary mapper in Release 1 hardware. While a tributary local loopback is in operation, a PPI-Loopback_On alarm is raised. Tributary remote loopback (Loop to Line) A remote 2 Mbit/s (or 34/45 Mbit/s for TN-1C) tributary loopback 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). This loopback is implemented in the tributary electrical line driver in Release 3 hardware and in the tributary mapper in Release 1 hardware. While a tributary remote loopback is in operation, a PPI-Loopback_On alarm is raised.
Diagnostic tools 4-3
Simultaneous loopbacks STM-1 and tributary loopbacks can be performed independently. On a specific 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.
Figure 4-1 TN-1C/TN-1P loopbacks
STM-1 Section Termination Module DSPI STM-1 local loopback ElectroOptical Module
STM-1 Section Termination Module DSPI STM-1 remote loopback ElectroOptical Module
2 Mbit/s or 34/45 Mbit/s (TN-1C only)
Trib Electrical Line Driver
Trib Mapper
Tributary local loopback
Trib Electrical Line Driver Tributary remote loopback
Trib Mapper
Nortel TN-1C/TN-1P
4-4 Diagnostic tools
2 Mbit/s or 34/45 Mbit/s test pattern generator and detector The following in-built test pattern generator and detector are available: TN-1C 2 Mbit/s or 34/45 Mbit/s test pattern generator and detector TN-1P 2 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/45 Mbit/s (TN-1C only) 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 TN-1C/TN-1P PRBS location
PRBS Generator
towards optical line Trib electrical line driver PRBS Detector Trib mapper
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/45 Mbit/s (TN-1C only) PRBS to line is applied, the downstream traffic (to 34/45 Mbit/s line) is broken and PRBS is injected instead. Note 3: For 34/45 Mbit/s (TN-1C only) tributaries, PRBS to line does not operate if a PPI-LOS 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 defined in ITU-T O.151. The pattern may be injected towards the aggregate on a specific 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. 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 1: If an * is shown at the end of the PRBS report (as above), it indicates that synchronisation was lost or a counter overflow occurred while the test was running (this invalidates the whole test). Note 2: The following procedure assumes that the Browser UI is used. The procedure is similar if the Command Line UI is used (see TN-1C/TN-1P Command Line User Interface Guide, 323-1081-401 for details).
Procedure 4-1 Applying/stopping a TN-1C/TN-1P continuity test Step 1 2 3 Action Open a UI session with the TN-1C/TN-1P via the CAT or the element controller EC-1. Login to the TN-1C/TN-1P by entering your user name, password and identification in the login fields. Select the Submit button. Access the loopback menu by selecting: Diagnostic Continuity 4 To apply a continuity test towards the optical line, select: To_fiber To apply a continuity test towards the tributary line, select: To_line 5 A dialogue is displayed that provides a text entry field for the tributary port and an integer value for the report frequency.
continued
Nortel TN-1C/TN-1P
4-6 Diagnostic tools Procedure 4-1 Applying/stopping a TN-1C/TN-1P continuity test (continued) Step 6 Action Enter the required tributary in the following format: 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. Enter the required report frequency. Select the Submit button. 7 8 To stop a continuity test, type the following: Stop Logout of the UI by selecting the Logout button.
end
end of chapter
5-1
Index
2 Mbit/s test pattern 4-4 34/45 Mbit/s test pattern 4-4
5HP-FE_QOSV_24H 2-16 HP-LOM 2-17 HP-PLM 2-19 HP-QOSV_15M 2-22 HP-QOSV_24H 2-23 HP-RDI 2-24 HP-REI 2-25 HP-TIM 2-26
A
alarm category 1-15 consequences 1-11 indications 1-1 masking 1-3 sequences 1-5 severity 1-15 subrack 1-6 associated documents ix AU-AIS 2-7 audience ix
I
INT-AU-AIS 2-29 INT-AU-LOP 2-31 INT-HP-Insert_Bus 2-33 INT-HP-IP_Buffer 2-34 INT-LP-IP_Buffer 2-36 INT-LP-OP_Buffer 2-37 INT-NE-Config_Corrupt 2-38 INT-NE-RAM_Fail 2-40 INT-NE-SW_Corrupt 2-41 INT-OS-Laser_Test 2-42 INT-RS-Tx_Buffer 2-43 INT-SYNC-Oscillator_Fail 2-44 INT-SYNC-Trib_Line_Fail 2-44 INT-TU-AIS 2-44 INT-TU-LOP 2-45
C
cards indications 1-3 cleaning optical connector 3-2
D
E
EA-Ext_inpn 2-10 element controller 1-2
L
logs 1-15 loopbacks 4-1 applying/removing 3-8 LP-DEG 2-46 LP-EXC 2-47 LP-FE_QOSV_15M 2-49 LP-FE_QOSV_24H 2-50 LP-PLM 2-51 LP-QOSV_15M 2-53 LP-QOSV_24H 2-54 LP-RDI 2-55 LP-REI 2-56
F
fault finding beginning 1-14
H
HP-DEG 2-11 HP-EXC 2-13 HP-FE_QOSV_15M 2-15
5-2 Index
M
maintenance philosophy 1-1 masking 1-3 measurement optical input power 3-6 optical output power 3-4 MS-AIS 2-57 MS-DEG 2-59 MS-EXC 2-61 MS-QOSV_15M 2-64 MS-QOSV_24H 2-65 MS-RDI 2-66
PPI-Loopback_On 2-90 PPI-LOS 2-91 PPI-TF 2-93 PPI-TX_QOSV_15M 2-94 PPI-TX_QOSV_24H 2-95 PPI-Unexp_Signal 2-96 PS-Battery_Low 2-97 PS-Door_Open 2-98 PS-Power_Fail 2-100
Q
Qecc-Comms_Fail 2-101
N
NE-Card_Fail 2-67 NE-Door_Open 2-68 NE-Ext_Card_Out (TN-1C only) 2-69 NE-Fan_Failed (TN-1C only) 2-70 NE-High_Temp (TN-1C only) 2-71 NE-Minor_Card_Mismatch (TN-1C only) 2-72 NE-Unexpected_Card (TN-1C only) 2-73 NE-Wrong_Card (TN-1C only) 2-74
R
RS-LOF 2-103 RS-Loopback_On 2-106 RS-LOS 2-107 RS-Realign_Phase 2-110
S
SYNC-Ext_Sync_LOS (TN-1C only) 2-112 SYNC-Holdover 2-117 SYNC-Source_Fail 2-113 SYNC-Src_Not_Primary 2-115
O
optical connector cleaning 3-2 optical input power measurement 3-6 optical output power measurement 3-4 OS-Laser_Bias_High 2-75 OS-Laser_Shutdown 2-76 OS-Optical_Power_High 2-77
T
TU-AIS 2-118 TU-LOP 2-120
P
PPI-AIS 2-78 PPI-Continuity_Test 2-79 PPI-CRC_QOSV_15M 2-80 PPI-CRC_QOSV_24H 2-81 PPI-CV_QOSV_15M 2-82 PPI-CV_QOSV_24H 2-83 PPI-DEG 2-84 PPI-EXC 2-85 PPI-Frm_QOSV_15M 2-86 PPI-Frm_QOSV_24H 2-87 PPI-LOF 2-88 PPI-LOM 2-89
International Optical Networks Technical Documentation Group Nortel Networks Oakleigh Road South London, N11 1HB So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.
* NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are trademarks of Nortel Networks.
Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation. IBM is a registered trademark of International Business Machines Corporation. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation.
SDH TRANSMISSION
Nortel TN-1C/TN-1P
Copyright 1996 2000 Nortel Networks, All Rights Reserved. The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever. NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. Document Number: 323-1081-543 Product Release Number: 5.1 Document Status: Standard Date: September 2000 Printed in England

Cảnh Báo SDH

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cảnh Báo SDH

Uploaded by

Copyright:

Available Formats

323-1081-543

Release 5.1 Standard September 2000

Nortel TN-1C/TN-1P Alarm Clearing Procedures

Nortel TN-1C/TN-1P Alarm Clearing Procedures

Clearing TN-1C/TN-1P equipment alarms Common procedures

Nortel TN-1C/TN-1P Alarm Clearing Procedures

323-1081-543 Release 5.1 Standard

Alarm Clearing Procedures

About this document

Nortel TN-1C/TN-1P Alarm Clearing Procedures

Technical support and information

323-1081-543 Release 5.1 Standard

Alarm Clearing Procedures

Craft access terminal

323-1081-543 Release 5.1 Standard

Figure 1-1 TN-1P Craft Access Panel - front view

323-1081-543 Release 5.1 Standard

The sequencing between the alarm states is shown in Figure 1-2.

Nortel TN-1C/TN-1P Alarm Clearing Procedures

1-6 Introduction Figure 1-2 Rack alarm state sequence diagram

REC ATT pressed Alarm occurs

REC ATT pressed

323-1081-543 Release 5.1 Standard

Nortel TN-1C/TN-1P Alarm Clearing Procedures

1-8 Introduction Figure 1-3 Masking hierarchy for TN-1C/TN-1P (part 1)

OS-Laser_ Shutdown **-QOSV_** see note SYNC-Ext_ Sync_LOS

Note: The QOSV alarms are:

TN-1C/TN-1P TN-1C only

323-1081-543 Release 5.1 Standard

Introduction 1-9 Figure 1-4 Masking hierarchy for TN-1C/TN-1P (part 2)

From Figure 1-3

Nortel TN-1C/TN-1P Alarm Clearing Procedures

1-10 Introduction Figure 1-5 Masking hierarchy for TN-1C/TN-1P (part 3)

NE-Card_ Fail To Figure 1-4

PPI-DEG TN-1C/TN-1P TN-1C only

323-1081-543 Release 5.1 Standard

Nortel TN-1C/TN-1P Alarm Clearing Procedures

323-1081-543 Release 5.1 Standard

Alarm PPI-Unexp_Signal (see Note 2) OS-Optical_Power_High INT-NE-Config_Corrupt

Beginning fault finding

323-1081-543 Release 5.1 Standard

Alarm category and severity

Nortel TN-1C/TN-1P Alarm Clearing Procedures

323-1081-543 Release 5.1 Standard

Nortel TN-1C/TN-1P Alarm Clearing Procedures

323-1081-543 Release 5.1 Standard

Clearing TN-1C/TN-1P equipment alarms

2-2 Clearing TN-1C/TN-1P equipment alarms

323-1081-543 Release 5.1 Standard

Nortel TN-1C/TN-1P Alarm Clearing Procedures

323-1081-543 Release 5.1 Standard

Nortel TN-1C/TN-1P Alarm Clearing Procedures

Page 2-112 2-113 2-114 2-115 2-116 2-117 2-118 2-120

323-1081-543 Release 5.1 Standard

Clearing TN-1C/TN-1P equipment alarms 2-7

Consequent alarms/events (TN-1C)

Nortel TN-1C/TN-1P Alarm Clearing Procedures

2-8 Clearing TN-1C/TN-1P equipment alarms

Consequent alarms/events (TN-1P)

323-1081-543 Release 5.1 Standard

Clearing TN-1C/TN-1P equipment alarms 2-9

Nortel TN-1C/TN-1P Alarm Clearing Procedures

2-10 Clearing TN-1C/TN-1P equipment alarms

OS-Laser_ Shutdown -QOSV_ see note SYNC-Ext_ Sync_LOS