Documentos de Académico
Documentos de Profesional
Documentos de Cultura
SDH TRANSMISSION
Nortel TN-1C/TN-1P
Alarm Clearing Procedures
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.
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 ix
Technical support and information x
Introduction 1-1
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
Index 5-1
List of figures
Figure 1-1 TN-1P Craft Access Panel - front view 1-4
Figure 1-2 Rack alarm state sequence diagram 1-6
Figure 1-3 Masking hierarchy for TN-1C/TN-1P (part 1) 1-8
Figure 1-4 Masking hierarchy for TN-1C/TN-1P (part 2) 1-9
Figure 1-5 Masking hierarchy for TN-1C/TN-1P (part 3) 1-10
Figure 4-1 TN-1C/TN-1P loopbacks 4-3
Figure 4-2 TN-1C/TN-1P PRBS location 4-4
List of tables
Table 1-1 Alarm consequences TN-1C/TN-1P 1-12
Table 1-2 TN-1C/TN-1P alarm category and alarm severity settings 1-15
Table 2-1 List of alarm clearing procedures for TN-1C/TN-1P 2-3
List of procedures
Procedure 2-1 AU-AIS alarm clearing 2-9
Procedure 2-2 HP-DEG alarm clearing 2-12
Procedure 2-3 HP-EXC alarm clearing 2-14
Procedure 2-4 HP-LOM alarm clearing 2-18
Procedure 2-5 HP-PLM alarm clearing 2-21
Procedure 2-6 HP-RDI alarm clearing 2-24
Procedure 2-7 HP-REI alarm clearing 2-25
Procedure 2-8 HP-TIM alarm clearing 2-28
Procedure 2-9 INT-HP-IP_Buffer alarm clearing 2-34
Procedure 2-10 INT-LP-IP_Buffer 2-36
Procedure 2-11 INT-LP-OP_Buffer alarm clearing 2-37
Procedure 2-12 INT-NE-Config_Corrupt alarm clearing 2-38
Procedure 2-13 LP-DEG alarm clearing 2-46
Procedure 2-14 LP-EXC alarm clearing 2-48
Procedure 2-15 LP-PLM alarm clearing 2-52
Procedure 2-16 LP-RDI alarm clearing 2-55
Procedure 2-17 LP-REI alarm clearing 2-56
Procedure 2-18 MS-AIS alarm clearing 2-58
Procedure 2-19 MS-DEG alarm clearing 2-60
Procedure 2-20 MS-EXC alarm clearing 2-62
Procedure 2-21 MS-RDI alarm clearing 2-66
Procedure 2-22 NE-Door_Open alarm clearing 2-68
Procedure 2-23 NE-Ext_Card_Out alarm clearing 2-69
Procedure 2-24 NE-Minor_Card_Mismatch alarm clearing 2-72
Procedure 2-25 NE-Unexpected_Card alarm clearing 2-73
Procedure 2-26 NE-Wrong_Card alarm clearing 2-74
Procedure 2-27 PPI-Continuity_Test alarm clearing 2-79
Procedure 2-28 PPI-DEG alarm clearing 2-84
Procedure 2-29 PPI-EXC alarm clearing 2-85
Procedure 2-30 PPI-Loopback_On alarm clearing 2-90
Procedure 2-31 PPI-LOS alarm clearing 2-92
Procedure 2-32 PPI-TF alarm clearing 2-93
Procedure 2-33 PS-Battery_Low alarm clearing 2-97
Procedure 2-34 PS-Door_Open alarm clearing 2-99
Procedure 2-35 PS-Power_Fail alarm clearing 2-100
Procedure 2-36 Qecc-Comms_Fail alarm clearing 2-102
Procedure 2-37 RS-LOF alarm clearing 2-104
Procedure 2-38 RS-Loopback_On alarm clearing 2-106
Procedure 2-39 RS-LOS alarm clearing 2-108
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.
Audience
This document is intended for:
• Maintenance engineers
• Customer support engineers
Associated documents
TN-1C/TN-1P Documentation Overview and Safety, 323-1081-090
IONNTPS@nortelnetworks.com
United Kingdom
Freephone: 0800 626 881
Telephone: 020 8361 4693
FAX: 020 8945 3456
International
Telephone: +44 20 8361 4693
FAX: +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
Introduction 1-
Maintenance philosophy
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.
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 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.
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.
Unit indications 1
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.
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.
• 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
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.
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.
Figure 1-2
Rack alarm state sequence diagram
Alarm Clear of
occurs alarm
Unacknowledged
Alarm
REC ATT
pressed
Acknowledged
REC ATT
pressed Alarm
Alarm Clear of
occurs 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.
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.
Figure 1-3
Masking hierarchy for TN-1C/TN-1P (part 1)
**-QOSV_** SYNC-Ext_
MS-RDI MS-AIS Qecc-
see note Sync_LOS
Comms_Fail
Figure 1-4
Masking hierarchy for TN-1C/TN-1P (part 2)
1
A
From Figure 1-3
INT-HP-
IP_Buffer
INT-AU_LOP
INT-AU_AIS
HP-EXC
HP-REI TU-LOP
TU-AIS
B
From Figure 1-5
INT-TU_LOP
INT-TU_AIS
LP-EXC
INT-LP-
OP_Buffer
LP-REI
TN-1C/TN-1P
Figure 1-5
Masking hierarchy for TN-1C/TN-1P (part 3)
NE-Ext_
Card_Out
NE-Wrong_
Card
NE-Unexpected
_Card
NE-Card_ NE-Minor_
Fail Card_Mismatch
To Figure 1-4
B
PPI-LOS
PPI-DEG PPI-LOF
TN-1C/TN-1P
PPI-LOM
TN-1C only
Alarm consequences 1
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.
Table 1-1
Alarm consequences TN-1C/TN-1P
or crash defaults
Action
Path Protection
Pass-through
( see Note 7)
Shutdown
Tx Trib or
LP-EXC
Trib AIS
MS-RDI
HP-RDI
LP-RDI
TU AIS
TU AIS
Switch
Laser
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—
Table 1-1
Alarm consequences TN-1C/TN-1P (continued)
1
or crash defaults
Action
Path Protection
Pass-through
( see Note 7)
Shutdown
Tx Trib or
LP-EXC
Trib AIS
MS-RDI
HP-RDI
LP-RDI
TU AIS
TU AIS
Switch
Laser
Alarm
PPI-Unexp_Signal ✔
(see Note 2)
OS-Optical_Power_High ✔
INT-NE-Config_Corrupt ✔
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)
Responding to logs 1
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.
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
Table 1-2
TN-1C/TN-1P alarm category and alarm severity settings (continued)
Alarm Alarm category Alarm severity
HP-RDI Deferred Major
HP-REI Deferred Major
HP-TIM Deferred Major
INT-AU-AIS In-station Minor
INT-AU-LOP Deferred Major
INT-HP-Insert_Bus Prompt Critical
INT-HP-IP_Buffer Deferred Major
INT-LP-IP_Buffer Deferred Major
INT-LP-OP_Buffer Deferred Major
INT-NE-Config_Corrupt Prompt Critical
INT-NE-RAM_Fail Prompt Critical
INT-NE-SW_Corrupt Prompt Critical
INT-OS-Laser_Test In-station Minor
INT-RS-Tx_Buffer Prompt Critical
INT-TU-AIS In-station Minor
INT-TU-LOP Deferred Major
LP-DEG Deferred Major
LP-EXC Deferred Major
LP-FE_QOSV_15M In-station Minor
LP-FE_QOSV_24H In-station Minor
LP-PLM Deferred Major
LP-QOSV_15M In-station Minor
LP-QOSV_24H In-station Minor
LP-RDI Deferred Major
LP-REI Deferred Major
MS-AIS In-station Minor
MS-DEG Deferred Major
MS-EXC Prompt Critical
MS-QOSV_15M In-station MInor
MS-QOSV_24H In-station MInor
MS-RDI Deferred Major
NE-Card_Fail Prompt Critical
NE-Door_Open Prompt Critical
—continued—
Table 1-2
TN-1C/TN-1P alarm category and alarm severity settings (continued)
1
Alarm Alarm category Alarm severity
NE-Ext_Card_Out Prompt Critical
NE-Fan_Failed Deferred Major
NE-High_Temp Prompt Critical
NE-Minor_Card_Mismatch In-station Minor
NE-Unexpected_Card In-station Minor
NE-Wrong_Card Prompt Critical
OS-Laser_Bias_High In-station Minor
OS-Laser_Shutdown Prompt Critical
OS-Optical_Power_High Prompt Critical
PPI-AIS In-station Minor
PPI-Continuity_test In-station Minor
PPI-CRC_QOSV_15M In-station Minor
PPI-CRC_QOSV_24H In-station Minor
PPI-CV_QOSV_15M In-station Minor
PPI-CV_QOSV_24H In-station Minor
PPI-DEG Deferred Major
PPI-EXC Deferred Major
PPI-Frm_QOSV_15M In-station Minor
PPI-Frm_QOSV_24H In-station Minor
PPI-LOM Deferred Major
PPI-LOS Deferred Major
PPI-LOF Deferred Major
PPI-Loopback_on In-station Minor
PPI-TF Deferred Major
PPI-TX_QOSV_15M In-station Minor
PPI-TX_QOSV_24H In-station Minor
PPI-Unexp_Signal In-station Minor
PS-Battery_Low Prompt Critical
PS-Door_Open Prompt Critical
PS-Power_Fail Prompt Critical
Qecc-Comms_Fail Prompt Critical
RS-LOF Prompt Critical
RS-Loopback_on In-station Minor
—continued—
Table 1-2
TN-1C/TN-1P alarm category and alarm severity settings (continued)
Alarm Alarm category Alarm severity
RS-LOS Prompt Critical
RS-Realign_Phase Prompt Critical
SYNC-Ext_Sync_LOS Deferred Major
SYNC-Holdover Prompt Critical
SYNC-Source_Fail Deferred Major
SYNC-Source_Out_of_Limits Deferred Major
SYNC-Src_Not_Primary Prompt Critical
SYNC-SSMB_Unstable Deferred Major
TU-AIS In-station Minor
TU-LOP Deferred Major
—end—
end of chapter
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.
Table 2-1 provides a list of alarms and the page where the alarm clearing
information can be found.
EXC Excessive
Ext External
FE Far End
HP High Order Path
INT Internal
IP Input
LOF Loss of Frame
LOM Loss of Multiframe
LOP Loss of Pointer
LOS Loss of Signal
LP Low Order Path
MS Multiplex Section
NE Network Element
OP Output
OS Optical Section
PLM Path Label Mismatch
PPI PDH Physical Interface
PS Power Supply
QOSV Quality of Service Violation
RAI Remote Alarm Indication
RAM Random Access Memory
RDI Remote Defect Indicator
REI Remote Error Indicator
RS Regenerator Section
SETG Synchronous Equipment Timing Generator
Src Source
SSM Synchronous Status Messaging
SW Software
SYNC Synchronisation
Temp Temperature
TF Traffic Fail
TIM Trace Identifier Mismatch
Trib Tributary
TU Tributary Unit
TX Transmit
Table 2-1
List of alarm clearing procedures for TN-1C/TN-1P
Alarm Page
AU-AIS 2-7
2
EA-Ext_inpn<1-8> 2-10
HP-DEG 2-11
HP-EXC 2-13
HP-FE_QOSV_15M 2-15
HP-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
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-TU-AIS 2-44
INT-TU-LOP 2-45
—continued—
Table 2-1
List of alarm clearing procedures for TN-1C/TN-1P (continued)
Alarm Page
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
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
NE-Card_Fail 2-67
NE-Door_Open 2-68
OS-Laser_Bias_High 2-75
OS-Laser_Shutdown 2-76
OS-Optical_Power_High 2-77
—continued—
Table 2-1
List of alarm clearing procedures for TN-1C/TN-1P (continued)
Alarm Page
PPI-AIS 2-78
2
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
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
Qecc-Comms_Fail 2-101
RS-LOF 2-103
RS-Loopback_On 2-106
RS-LOS 2-107
RS-Realign_Phase 2-110
—continued—
Table 2-1
List of alarm clearing procedures for TN-1C/TN-1P (continued)
Alarm Page
SYNC-Source_Fail 2-113
SYNC-Source_Out_of_Limits 2-114
SYNC-Src_Not_Primary 2-115
SYNC-SSMB_Unstable 2-116
SYNC-Holdover 2-117
TU-AIS 2-118
TU-LOP 2-120
—end—
AU-AIS
Significance
An AIS has been detected in the H1 and H2 bytes indicating a failure in the
upstream path. 2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths.
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.
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.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-1.
Procedure 2-1
AU-AIS alarm clearing
2
Step Action
1 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). 2
Impact
Traffic affecting.
HP source
Possible HP-REI alarm.
LP source
Possible LP-REI alarms.
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
Perform the alarm clearing procedure given in Procedure 2-2.
Procedure 2-2
HP-DEG alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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.
2
Impact
Traffic affecting.
LP source
Possible LP-REI alarms.
Possible causes
• Faulty local TN-1C/TN-1P multiplexer.
• Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-3.
Procedure 2-3
HP-EXC alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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. 2
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.
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-LOM
Significance
An illegal multiframe sequence has been detected in the H4 byte.
2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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
Perform the alarm clearing procedure given in Procedure 2-4.
Procedure 2-4
HP-LOM alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 Perform a ‘Local’ loopback at 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 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-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). 2
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.
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.
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
• 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
Perform the alarm clearing procedure given in Procedure 2-5.
Procedure 2-5
HP-PLM alarm clearing
2
Step Action
—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.
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-QOSV_24H
Significance
One of the HP parameter counts for the 24 hour performance monitoring
period has exceeded the configurable threshold. 2
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-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.
Consequent alarms/events
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
Perform the alarm clearing procedure given in Procedure 2-6.
Procedure 2-6
HP-RDI alarm clearing
Step Action
—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 2
that have exceeded the configurable threshold of 10-5, 10-6, or 10-7 (default
10-5).
Impact
None.
Consequent alarms/events
None.
Possible causes
HP errors on the network.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-7.
Procedure 2-7
HP-REI alarm clearing
Step Action
1 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.
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—
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.
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.
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
• 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
Perform the alarm clearing procedure given in Procedure 2-8.
Procedure 2-8
HP-TIM alarm clearing
Step Action
—end—
INT-AU-AIS
Significance
An internal AIS has been detected internally in the H1 and H2 bytes for three
consecutive frames. 2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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.
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
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 2
frames.
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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.
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
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-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 2
frames.
Impact
Traffic affecting.
Consequent alarms/events
None.
Possible causes
Faulty local TN-1C/TN-1P multiplexer.
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.
Consequent alarms/events
None.
Note: If the alarm persists, protected paths may switch due to HP and LP
defects.
Possible causes
• Synchronisation problems in network.
• 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 Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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—
Procedure 2-9
INT-HP-IP_Buffer alarm clearing (continued)
Step Action
—end—
INT-LP-IP_Buffer
Significance
The FIFO in the mapping/multiplexing direction is in an underflow or
overflow state.
Impact
Traffic affecting.
Consequent alarms/events
None.
Possible causes
• Incoming tributary signal out-of-limits.
• Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-10.
Procedure 2-10
INT-LP-IP_Buffer
Step Action
—end—
INT-LP-OP_Buffer
Significance
The FIFO in the demapping/demultiplexing direction is either in the
underflow or overflow state. 2
Impact
Traffic affecting.
Consequent alarms/events
None.
Possible causes
• Synchronisation problems in network.
• Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-11.
Procedure 2-11
INT-LP-OP_Buffer alarm clearing
Step Action
—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.
Consequent alarms/events
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
Perform the alarm clearing procedure given in Procedure 2-12.
Procedure 2-12
INT-NE-Config_Corrupt alarm clearing
Step Action
—continued—
Procedure 2-12
INT-NE-Config_Corrupt alarm clearing (continued)
Step Action
—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.
Consequent alarms/events
None.
Possible causes
RAM failure on TN-1C/TN-1P multiplexer.
Corrective action
Replace the TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance
Procedures, 323-1081-547, for replacement procedures.
INT-NE-SW_Corrupt
Significance
The checksum of the application code is incorrect.
2
Impact
None.
Consequent alarms/events
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.
Consequent alarms/events
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. 2
Impact
Traffic affecting.
Consequent alarms/events
None.
Possible causes
Faulty local TN-1C/TN-1P multiplexer.
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.
Consequent alarms/events
Local
AIS injection on associated tributary output.
Possible causes
Faulty local TN-1C/TN-1P multiplexer.
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. 2
Impact
Traffic affecting.
Consequent alarms/events
Local
AIS injection on associated tributary output.
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.
Consequent alarms/events
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
Perform the alarm clearing procedure given in Procedure 2-13.
Procedure 2-13
LP-DEG alarm clearing
Step Action
—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. 2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths.
Consequent alarms/events
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).
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 Action
—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. 2
Impact
None.
Consequent alarms/action
None.
Possible causes
Errors on the network.
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.
Consequent alarms/action
None.
Possible causes
Errors on the network.
Corrective action
Investigate network for cause of errors (look at performance monitoring logs
for additional information).
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: 2
• 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.
Consequent alarms/events
Local
AIS injection on tributary output.
Possible causes
• Incorrect traffic settings.
• Incorrect path connection.
• Faulty local or far TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-15.
Procedure 2-15
LP-PLM alarm clearing
Step Action
1 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).
VC-3s (TN-1C)
• 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).
If the settings are not correct, proceed to step 2.
2 Verify that the path is correctly connected at all intermediate multiplexers.
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, proceed to step 4.
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-QOSV_15M
Significance
One of the LP parameter counts for the 15 minute performance monitoring
period has exceeded the configurable threshold. 2
Impact
None.
Consequent alarms/action
None.
Possible causes
Errors on the network.
Corrective action
Investigate network for cause of errors (look at performance monitoring logs
for additional information).
LP-QOSV_24H
Significance
One of the LP parameter counts for the 24 hour 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).
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 2
termination.
Impact
None.
Consequent alarms/events
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
Perform the alarm clearing procedure given in Procedure 2-16.
Procedure 2-16
LP-RDI alarm clearing
Step Action
1 Investigate far multiplexer/path termination for cause of alarm and carry out
fault finding procedures for appropriate alarm.
If cause of alarm found, perform the appropriate alarm clearing procedure.
If cause of alarm not found, proceed to step 2.
2 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.
3 Replace the far TN-1C/TN-1P multiplexer. Refer to the Equipment
Maintenance Procedures, 323-1081-547, for replacement procedures.
4 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.
Consequent alarms/events
None.
Possible causes
TU errors on network.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-17.
Procedure 2-17
LP-REI alarm clearing
Step Action
1 Investigate far path termination for cause of errors and carry out fault finding
procedures for appropriate alarm (e.g. LP-DEG alarm).
If cause of alarm found, perform the appropriate alarm clearing procedure.
If cause of alarm not found, proceed to step 2.
2 Replace the local TN-1C/TN-P 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 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 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. 2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths.
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.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-18.
Procedure 2-18
MS-AIS alarm clearing
Step Action
1 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).
3 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.
4 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). 2
Impact
Traffic affecting.
HP source
Possible intermittent HP-REI alarms.
LP source
Possible intermittent LP-REI 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
Perform the alarm clearing procedure given in Procedure 2-19.
Procedure 2-19
MS-DEG alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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 TN-1C/TN-1P multiplexer and escalate the problem.
If the alarm clears, remove the ‘Local’ loopback and proceed to step 3.
3 Clean the receive optical connections at the local TN-1C/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.
5 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 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.
7 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—
MS-EXC
Significance
The BER of the BIP-24 error check has exceeded 10-3.
2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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.
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
• Faulty optical fibre/connections.
• Faulty local TN-1C/TN-1P multiplexer.
• Faulty far end TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-20
Procedure 2-20
MS-EXC alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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 TN-1C/TN-1P multiplexer and escalate the problem.
If the alarm clears, remove the ‘Local’ loopback and proceed to step 3.
—continued—
Procedure 2-20
MS-EXC alarm clearing (continued)
Step Action
—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.
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).
MS-QOSV_24H
Significance
One of the MS parameter counts for the 24 hour performance monitoring
period has exceeded the configurable threshold. 2
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).
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.
Consequent alarms/events
None.
Possible causes
RS-LOS, RS-LOF, MS-AIS, or MS-EXC alarm at the far multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-21
Procedure 2-21
MS-RDI alarm clearing
Step Action
—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 2
subsequently at regular intervals (approximately every 30 seconds).
Impact
May be traffic affecting, depending on the type of failure.
Consequent alarms/events
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.
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.
Consequent alarms/events
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 Action
1 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—
Consequent alarms/events
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
Perform the alarm clearing procedure given in Procedure 2-23.
Procedure 2-23
NE-Ext_Card_Out alarm clearing
Step Action
—end—
Consequent alarms/events
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.
Impact
Possible overheating of TN-1C.
Consequent alarms/events
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.
Impact
Possible loss of tributary traffic carried by tributary extension card.
Consequent alarms/events
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
Perform the alarm clearing procedure given in Procedure 2-24.
Procedure 2-24
NE-Minor_Card_Mismatch alarm clearing
Step Action
—end—
Consequent alarms/events
None.
Possible causes
• Tributary extension card incorrectly fitted.
• System incorrectly configured.
• Faulty local TN-1C multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-25.
Procedure 2-25
NE-Unexpected_Card alarm clearing
Step Action
—end—
Possible causes
• Wrong tributary extension card fitted.
• System incorrectly configured.
• Faulty local TN-1C multiplexer.
• Unrecognised PEC code (extension card).
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-26.
Procedure 2-26
NE-Wrong_Card alarm clearing
Step Action
—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. 2
Impact
Non-traffic affecting.
Consequent alarms/events
None.
Possible causes
Aging of laser.
Corrective actions
Replace the TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance
Procedures, 323-1081-547, for replacement procedures.
OS-Laser_Shutdown
Significance
The laser has been shutdown by the automatic laser shutdown (ALS) circuit
or by OS-Optical_Power_High alarm.
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
Consequent alarms/events
• 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. 2
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
Consequent alarms/events
Laser shutdown. This is a safety feature, although the laser output is still
within the standard safe range.
Note: The laser shutdown is latched, the laser will remain off until the
multiplexer is powered-up.
Possible causes
Faulty TN-1C/TN-1P transmit circuit.
Corrective actions
Replace the TN-1C/TN-1P multiplexer. Refer to the Equipment Maintenance
Procedures, 323-1081-547, for replacement procedures.
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.
Consequent alarms/action
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. 2
Impact
A continuity test overwrites all signals on the tributary to which it is applied.
Consequent alarms/events
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 Action
—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.
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).
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. 2
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).
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.
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).
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. 2
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).
PPI-DEG
Significance
The BER of the code violations in the incoming tributary signal has exceeded
10-5.
Impact
Traffic affecting.
Consequent alarms/events
None.
Possible causes
• Errored input signal.
• Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedures given in Procedure 2-28.
Procedure 2-28
PPI-DEG alarm clearing
Step Action
—end—
PPI-EXC
Significance
The BER of the code violations in the incoming tributary signal has exceeded
10-3. 2
Impact
Traffic affecting.
Consequent alarms/events
None.
Possible causes
• Errored input signal.
• Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-29.
Procedure 2-29
PPI-EXC alarm clearing
Step Action
—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.
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).
PPI-Frm_QOSV_24H
Significance
One of the tributary framed parameter counts for the 24 hour performance
monitoring period has exceeded the configurable threshold. 2
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).
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.
Consequent alarms/action
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.
2
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.
Consequent alarms/action
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.
Consequent alarms/events
None.
Possible causes
• A loopback is applied.
• Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedures given in Procedure 2-30.
Procedure 2-30
PPI-Loopback_On alarm clearing
Step Action
—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
2
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.
Consequent alarms/events
• Tx Trib AIS or TU AIS
— If Tx Trib AIS selected as consequent action, no indication will be
provided at the far path termination.
— If TU AIS selected as consequent action, TU AIS indication will be
provided at far path termination.
Note 1: Tx Trib AIS/TU AIS is 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
Perform the alarm clearing procedures given in Procedure 2-31.
Procedure 2-31
PPI-LOS alarm clearing
Step Action
1 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.
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.
4 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
—end—
PPI-TF
Significance
The output tributary signal has fallen below a predefined threshold.
2
Impact
Loss of 2 Mbit/s (or 34/45 Mbit/s for TN-1C) traffic output.
Consequent alarms/events
None.
Possible causes
Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedures given in Procedure 2-32.
Procedure 2-32
PPI-TF alarm clearing
Step Action
1 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.
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.
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).
PPI-TX_QOSV_24H
Significance
One of the tributary output parameter counts for the 24 hour performance
monitoring period has exceeded the configurable threshold. 2
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).
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.
Consequent alarms/events
• Tx Trib AIS or TU AIS
— If Tx Trib AIS selected as consequent action, no indication will be
provided at the far path termination.
— If TU AIS selected as consequent action, TU AIS indication will be
provided at far path termination.
— No consequent actions are provided when the traffic state is auto.
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. 2
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.
Consequent alarms/events
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 Action
—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.
Consequent alarms/events
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).
Procedure 2-34
PS-Door_Open alarm clearing
Step Action
1 Check that the plastic tab is not broken on the plastic cover and that the cover 2
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).
Impact
None immediately. Minimum 3 hours of operation is available from battery
backup.
Consequent alarms/events
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 Action
1 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.
2 Check a.c. fuse, replace if blown.
If fuse blows again, proceed to step 4.
3 Verify that the a.c. mains supply is present.
If the a.c. mains supply is not present, investigate loss.
If the a.c. mains supply is present, proceed to step 4.
4 Replace the TN-1C/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. 2
Impact
• Non-traffic affecting.
• Inter-site data communications are unavailable.
Consequent alarms/events
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 Action
—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 2
consecutive frames).
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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
Perform the alarm clearing procedure given in Procedure 2-37.
Procedure 2-37
RS-LOF alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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 TN-1C/TN-1P multiplexer and escalate the problem.
If the alarm clears, remove the ‘Local’ loopback and proceed to step 3.
—continued—
Procedure 2-37
RS-LOF alarm clearing (continued)
Step Action
—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.
Consequent alarms/events
None.
Possible causes
• A loopback is applied.
• Faulty input circuit on TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedures given in Procedure 2-38.
Procedure 2-38
RS-Loopback_On alarm clearing
Step Action
—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 2
detected for at least 6.5 µs ± 1 µs.
Impact
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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.
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
• Fibre break/bad termination.
• Transmitter failure at far TN-1C/TN-1P multiplexer.
• Receiver failure on local TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-39.
Procedure 2-39
RS-LOS alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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.
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.
—continued—
Procedure 2-39
RS-LOS alarm clearing (continued)
Step Action
—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.
Consequent alarms/events
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 Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 Perform a ‘Local’ loopback at 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 TN-1C/TN-1P multiplexer and escalate the problem.
If the alarm clears, remove the ‘Local’ loopback and proceed to step 6.
3 Perform a ‘Local’ loopback on the appropriate aggregate at the far
TN-1C/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—
Procedure 2-40
RS-Realign_Phase alarm clearing (continued)
Step Action
—end—
Consequent alarms/action
None.
Possible causes
• Input connector not properly terminated.
• External synchronisation source failure.
• Faulty TN-1C multiplexer.
Corrective action
Perform the alarm clearing procedures given in Procedure 2-41.
Procedure 2-41
SYNC-Ext_Sync_LOS alarm clearing
Step Action
—end—
SYNC-Source_Fail
Significance
The synchronisation source has become invalid.
2
Impact
None.
Consequent alarms/events
None.
Possible causes
• Loss of selected synchronisation signal.
• Receipt of AIS on aggregate selected as synchronisation source.
• Source out-of-limits.
• 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
Perform the alarm clearing procedure given in Procedure 2-42.
Procedure 2-42
SYNC-Source_Fail alarm clearing
Step Action
—end—
SYNC-Source_Out_of_Limits
Significance
Loss of synchronisation signal.
Impact
None.
Consequent alarms/events
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.
Step Action
—end—
SYNC-Src_Not_Primary
Significance
The primary synchronisation source is not currently selected.
2
Impact
None.
Consequent alarms/action
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
Consequent alarms/action
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
Perform the alarm clearing procedure given in Procedure 2-44.
Procedure 2-44
SYNC-SSMB_Unstable alarm clearing
Step Action
—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 2
during switching between external sources.
Note: The alarm is not raised if the internal clock is selected as the primary
source.
Impact
The multiplexer is not traceable to the network synchronisation, which may
cause problems depending on the system synchronisation architecture.
Consequent alarms/events
None.
Possible causes
• No valid external synchronisation sources available.
• Faulty local TN-1C/TN-1P multiplexer.
Corrective actions
Perform the alarm clearing procedure given in Procedure 2-45
Procedure 2-45
SYNC-Holdover alarm clearing
Step Action
1 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.
If the alarm is still present, escalate the problem.
—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.
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.
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
Perform the alarm clearing procedure given in Procedure 2-46. 2
Procedure 2-46
TU-AIS alarm clearing
Step Action
—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
• Traffic affecting on unprotected paths.
• Temporary traffic hit on protected paths if paths switched to aggregate
containing alarm.
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.
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
Perform the alarm clearing procedure given in Procedure 2-47.
Procedure 2-47
TU-LOP alarm clearing
Step Action
1 If the route is protected, ensure that the traffic is switched to the other
aggregate port.
2 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.
3 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 TN-1C/TN-1P multiplexer and escalate the problem.
If the alarm clears, remove the ‘Local’ loopback and proceed to step 4.
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—
end of chapter
Common procedures 3-
3
This chapter provides a list of common task procedures to which the user is
referred when performing certain alarm clearing procedures.
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.
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.
Procedure 3-1
Cleaning an optical plug
Step Action
—end—
Procedure 3-2
Cleaning an optical coupler
Step Action
—end—
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.
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 Action
—continued—
Procedure 3-3
Optical output power measurement (continued)
Step Action
11
Forced on
A dialogue is displayed with a drop down selector enabling you to select the
3
required laser to turn on. Select the required laser and then select the
‘Submit’ button.
12 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.
—end—
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.
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 Action
—continued—
Procedure 3-4
Optical input power measurements (continued)
Step Action
8 Use the UI to turn the laser on (forced_on) at the far end by selecting:
Config
Laser state
9
Forced on
A dialogue is displayed with a drop down selector enabling you to select the
3
required laser to turn on. Select the required laser and then select the
‘Submit’ button.
10 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.
—end—
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.
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 Action
1 Open a UI session with the TN-1C/TN-1P via the CAT or the element
controller EC-1.
2 Login to the TN-1C/TN-1P by entering your user name, password and
identification in the login fields. Select the ‘Submit’ button.
3 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—
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.
3
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
Diagnostic tools 4-
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
4
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.
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.
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.
Simultaneous loopbacks
STM-1 and tributary loopbacks can be performed independently.
STM-1
Section
Termination
Module
4
DSPI Electro-
Optical
STM-1 local loopback Module
STM-1
Section
Termination
Module
DSPI Electro-
Optical
STM-1 remote loopback Module
2 Mbit/s
or Trib Trib
34/45 Mbit/s Electrical Mapper
(TN-1C only) Line Driver
2 Mbit/s Trib
or Electrical Trib
34/45 Mbit/s Line Mapper
(TN-1C only) Driver
PRBS
Generator
2 Mbit/s towards
or optical
34/45 Mbit/s line
(TN-1C only) Trib
electrical Trib
line driver mapper
PRBS
Detector
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.
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 Action
1 Open a UI session with the TN-1C/TN-1P via the CAT or the element
controller EC-1.
2 Login to the TN-1C/TN-1P by entering your user name, password and
identification in the login fields. Select the ‘Submit’ button.
3 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—
Procedure 4-1
Applying/stopping a TN-1C/TN-1P continuity test (continued)
Step Action
—end—
end of chapter
Index 5-
2 Mbit/s test pattern 4-4 HP-FE_QOSV_24H 2-16
34/45 Mbit/s test pattern 4-4 HP-LOM 2-17
HP-PLM 2-19
A HP-QOSV_15M 2-22
alarm HP-QOSV_24H 2-23
category 1-15 HP-RDI 2-24
consequences 1-11 HP-REI 2-25
indications 1-1
masking 1-3
HP-TIM 2-26 5
sequences 1-5 I
severity 1-15 INT-AU-AIS 2-29
subrack 1-6 INT-AU-LOP 2-31
associated documents ix INT-HP-Insert_Bus 2-33
AU-AIS 2-7 INT-HP-IP_Buffer 2-34
audience ix INT-LP-IP_Buffer 2-36
INT-LP-OP_Buffer 2-37
C INT-NE-Config_Corrupt 2-38
cards INT-NE-RAM_Fail 2-40
indications 1-3 INT-NE-SW_Corrupt 2-41
cleaning INT-OS-Laser_Test 2-42
optical connector 3-2 INT-RS-Tx_Buffer 2-43
INT-SYNC-Oscillator_Fail 2-44
INT-SYNC-Trib_Line_Fail 2-44
D INT-TU-AIS 2-44
Diagnostic tools 4-1 INT-TU-LOP 2-45
E L
EA-Ext_inpn 2-10 logs 1-15
element controller 1-2 loopbacks 4-1
applying/removing 3-8
F LP-DEG 2-46
fault finding LP-EXC 2-47
beginning 1-14 LP-FE_QOSV_15M 2-49
LP-FE_QOSV_24H 2-50
H LP-PLM 2-51
HP-DEG 2-11 LP-QOSV_15M 2-53
HP-EXC 2-13 LP-QOSV_24H 2-54
HP-FE_QOSV_15M 2-15 LP-RDI 2-55
LP-REI 2-56
M PPI-Loopback_On 2-90
maintenance PPI-LOS 2-91
philosophy 1-1 PPI-TF 2-93
masking 1-3 PPI-TX_QOSV_15M 2-94
measurement PPI-TX_QOSV_24H 2-95
optical input power 3-6 PPI-Unexp_Signal 2-96
optical output power 3-4 PS-Battery_Low 2-97
MS-AIS 2-57 PS-Door_Open 2-98
MS-DEG 2-59 PS-Power_Fail 2-100
MS-EXC 2-61
MS-QOSV_15M 2-64 Q
MS-QOSV_24H 2-65 Qecc-Comms_Fail 2-101
MS-RDI 2-66
R
N RS-LOF 2-103
NE-Card_Fail 2-67 RS-Loopback_On 2-106
NE-Door_Open 2-68 RS-LOS 2-107
NE-Ext_Card_Out (TN-1C only) 2-69 RS-Realign_Phase 2-110
NE-Fan_Failed (TN-1C only) 2-70
NE-High_Temp (TN-1C only) 2-71 S
NE-Minor_Card_Mismatch (TN-1C SYNC-Ext_Sync_LOS (TN-1C only) 2-112
only) 2-72 SYNC-Holdover 2-117
NE-Unexpected_Card (TN-1C only) 2-73 SYNC-Source_Fail 2-113
NE-Wrong_Card (TN-1C only) 2-74 SYNC-Src_Not_Primary 2-115
O T
optical connector TU-AIS 2-118
cleaning 3-2 TU-LOP 2-120
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
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
Nortel TN-1C/TN-1P
Alarm Clearing Procedures
Copyright 1996 – 2000 Nortel Networks, All Rights Reserved.