Fault Detection

323-1801-541
Nortel Networks
OPTera Long Haul 1600
Optical Line System
Fault Detection
Rel 3 Standard July 2000
What’s inside...
Local alarm indicators
Surveillance interfaces
Support tools
Copyright  2000 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
*Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, S/DMS TransportNode, OPTera, Preside,
and Unified Networks are trademarks of Nortel Networks.
UNIX is a trademark of X/Open Company, Ltd.

VT100 is a trademark of Digital Equipment Corporation.
Printed in Canada and in the United Kingdom

iii
Contents 0
About this document v
Local alarm indicators 1-1

Alarm and alert severity 1-1
Service code 1-2
Time filtering 1-2
Alarm inhibiting 1-2
Alarm provisioning 1-3
System initiated conditions 1-3
System initiated actions 1-3
User initiated actions 1-4
LCAP LEDs and push buttons 1-4
Alarm cutoff (ACO) push button 1-5
Lamp test 1-5
ACO LED 1-5
Power LED 1-6
Critical, Major, Minor LEDs 1-6
Circuit breaker trip LED 1-6
Bay lamps and contacts 1-7
Critical alarm 1-8
Major alarm 1-8
Minor alarm 1-8
Circuit pack LEDs 1-9
LED Definitions 1-12
Surveillance interfaces 2-1

Network element user interface 2-1
Alarm related menus 2-3
Operations controller 2-6
OPC network surveillance environment 2-6
TL1 interface 2-10
Preside, Network Management software 2-11
Parallel telemetry 2-11
Support tools 3-1

Logs 3-1
Log types supported 3-1
Log numbering 3-2
Fault Detection 323-1801-541 Rel 3 July 2000

iv Contents
Description of log record fields 3-3

System initiated actions 3-3
User initiated actions 3-3
Performance monitoring 3-4
OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

v
About this document 0

This document describes the various alarm reporting tools and indicators
available on the Nortel Networks OPTera Long Haul 1600 Optical Line
System (formerly OPTera LH) Repeater, Combiner, and Amplifier network
elements. Topics covered include the following:
• alarm severity level definitions
• local fault detection tools
• remote fault detection tools
• support tools for troubleshooting purposes
Audience
This document is for the following members of the operating company:
• planners
• provisioners
• network administrators
• transmission standards engineers
• maintenance personnel
References
This document refers to the following OPTera Long Haul 1600 Optical Line
System NTPs:
• Alarm Reference Guide, 323-1801-542
• Trouble Clearing and Module Replacement, 323-1801-543
• Log Reference, 323-1801-840

vi About this document
OPTera Long Haul 1600 NTP Library

The following figure shows the documentation structure of the OPTera Long
Haul 1600 NTP Library.
Network
16 OR r
Applications
00
G Plu
M
Supported
C
R
om r
Am s
ep
ea
bi
pl
ne
ifi
te
er
Library Introduction, List of Terms, and Master Topical Index
323-1801-091 About the OPTera Long Haul 1600 Library
Engineering and Planning
NTY311AX Repeater Network Application Guide

NTY312AX Combiner Network Application Guide
NTY314AX 1600G Amplifier Network Application Guide
NTY312DX 100 GHz MOR Plus 2 to 32-λ Optical Layer Applications Guide
NTY311DX 200 GHz MOR/MOR Plus 2 to 16-λ Optical Layer Applications Guide
NTY313DX MOR Plus Optical Add/Drop Applications Guide
NTY314DX MOR Plus Optical Layer OAM&P Guide
NTY315DX 1600G Amplifier Optical Layer Applications Guide
NTY317DX 1600G Amplifier Optical Layer OAM&P Guide
NTCA66CA SONET Orderwire User Guide
NTCA66DA SDH Orderwire User Guide
323-1801-190 TL1 Interface Description
323-1801-195 Network Element User Interface Description
323-1801-196 OPC User Interface Description
323-1801-197 1600G Amplifier Fiber Assist Tool Description
Installation, Commissioning, and Testing
323-1801-201 Installation Procedures

323-1801-220 Powering Up and Commissioning Procedures
323-1801-221 Site Testing Procedures
323-1801-222 System Commissioning and Testing Procedures
323-1801-225 MOR Plus SLAT and Upgrade Procedures
323-1801-226 1600G Amplifier SLAT and Upgrade Procedures
Operations, Administration, and Provisioning
323-1801-301 User Interface Connection Procedures

323-1801-302 External Interface Configuration Procedures
323-1801-303 Software Administration Procedures
323-1801-304 Data Administration Procedures
323-1801-305 Security Management Procedures
323-1801-310 Provisioning and Operations Procedures
323-1801-311 Protection Switching Procedures
323-1801-315 MOR Plus Provisioning Procedures
323-1801-316 1600G Amplifier Provisioning Procedures
-continued-

About this document vii
Network
16
Applications
00 R P
G
M
Supported
C
R
O
om r
Am s
ep
ea
bi
pl
ne
lu
ifi
te
er
r
Maintenance
323-1801-520 Performance Monitoring Procedures

323-1801-541 Fault Detection
323-1801-542 Alarm Reference Guide
323-1801-543 Trouble Clearing and Module Replacement
323-1801-545 MOR Plus Alarm Clearing and Module Replacement
323-1801-546 1600G Amplifier Alarm Clearing and Module Replacement
323-1801-840 Log Reference
Supporting Documentation to the OPTera Long Haul 1600 Library (not part of this library)
323-1301-XXX OC-192 NTP Library
323-1321-XXX TN-64X NTP Library
323-1201-XXX OC-48 NTP Library
323-1211-XXX TN-16X NTP Library
450-3101-XXX Preside Documentation
NTR710AM Optical Networks Data Communications Planning Guide
NTCA65DA OPTera Connect DX NTP Library (OPTera Connect DX SONET platform)
NTCA65FA OPTera Connect DX NTP Library (OC-192 platform)
NTCA65GA OPTera Connect DX NTP Library (OPTera Connect DX SONET & OC-192 platforms)
NTCA65JA OPTera Connect DX NTP Library (OPTera Connect DX SDH platform)
NTCA65AC TN-64X Rel 3 NTP Library
NTCA65KA OPTera Connect DX NTP Library (OPTera Connect DX SDH & TN-64X platforms)

viii About this document
Fault Detection Summary

Main tasks:
• Local Alarm Indicators
— Read Chapter 1, “Local Alarm Indicators”
• Access the NE UI from the VT-100 terminal

— Select the alarm menu from the main menu
— Select the active alarms option
— Select the Historical alarms option to view detailed list of alarms that occurred
• Access the OPC UI from the VT-100 terminal

— Select OPC network surveillance environment
— Select alarm monitor to view alarm counts for all OPTera Long Haul 1600 NEs in the OPC
span of control
— Select event browser to see records of OPC logs, OPC and NE alarms, and alerts
— Select network summary to monitor the status of the network from the main window
— Select network browser to view network status information
• Access TL1 interface

— Get autonomous alarm reports in real time
— Retrieve threshold crossing alerts, events, and logs
— Manually retrieve alarms
• Access the Network Manager

— Get a status view of a large S/DMS transport node network
— Local fault condition down to the circuit pack level
— Analyze the whole network
— Get access to the OAM&P functions of the OPC
— Get login access to the NE and the OPCs
• Access the Parallel telemetry

— Select parallel input telemetry to allow the customer to connect external equipment (detectors)
to the NE
— Select parallel input telemetry to allow the customer to connect external equipment (reactors)
to the NE

1-1
Local alarm indicators 1-

This chapter defines the various levels of alarms and alerts along with LED
locations and definitions for the local craft access panel (LCAP) and the
various circuit packs supported on the OPTera Long Haul 1600 network
element.
The OPTera Long Haul 1600 network element features a number of alarm
indicators that provide visual and audible indications required for maintenance
purposes.
For information on how to display alarm details, refer to Alarm Reference

Guide, 323-1801-542. For information on how to clear alarms that pertain to
specific network elements or circuit packs, refer to Table 1-1 for the
appropriate OPTera Long Haul 1600 NTP:
Table 1-1
Network Element NTP Title & Number

/ Circuit Pack
Repeater Trouble Clearing and Module Replacement,

323-1801-543
Combiner Trouble Clearing and Module Replacement,

323-1801-543
Amplifier 1600G Amplifier Alarm Clearing and Module

Replacement, 323-1801-546
MOR Plus alarms MOR Plus Alarm Clearing and Module Replacement,
323-1801-545
Alarm and alert severity

Four severity levels are available for the alarms: critical, major, minor, and
warning. Each alarm has a default severity level.
• Critical: these alarms are the most severe, and are always traffic affecting.
A “Circuit Pack Fail” alarm on an unprotected OC-192/STM-64 XR
transmit interface is an example of a critical alarm.

1-2 Local alarm indicators
• Major: these alarms indicate failures less severe than critical alarms, but
the failures can be traffic affecting. An “Intercard Fail Alarm” on an
unprotected 2.5G WT circuit pack is an example of a major alarm.
• Minor: minor alarms indicate a protected circuit pack failure, or an
exceeded performance monitoring threshold. Minor alarms do not indicate
traffic loss.
• Warning: A warning refers to conditions less severe than minor alarms, but
still require analysis. A “Duplicate network element name” alarm on an
OPTera Long Haul 1600 network element is an example of a warning.
Alerts are events that do not require direct maintenance action. These event
indications appear in event reports (alerts). The Network Element User
Interface (NE UI) receives these alerts on detection of an event condition.
Service code
The service code for alarms at all severity levels indicates if the alarm is
service affecting (SA), or non-service affecting (NSA). For example, an
unprotected optical unit failure alarm is SA, and a protected optical unit failure
is NSA.
Time filtering
The OPTera Long Haul 1600 network element can support time filtering of
alarms. Each alarm has a default hold-off period and hold-on time period.
Hold-off time period indicates the predetermined amount of time before the
alarm is raised to ensure the alarm condition is stable. Hold-on period indicates
the predetermined amount of time the alarm condition must not be present
before the alarm indication clears.
Alarm inhibiting
The OPTera Long Haul 1600 network element can support alarm inhibiting.
With alarm inhibiting, the system does not generate an alarm report after
detection of the condition. An inhibited alarm does not appear in the alarm
counts at the user interface and does not change status indications. The
inhibiting feature is provisionable through the NE UI.
A generated log shows whether alarm provisioning is inhibited. This log warns
the user of alarm inhibiting. You can retrieve information about all alarms and
find out if any alarm is an inhibited alarm. Each alarm has a default setting to
indicate if it is an inhibited alarm or not.

Alarm provisioning
The OPTera Long Haul 1600 network element can support alarm provisioning.
Default status for alarms is ‘alarmed’, with the exception of the following
alarms (their default status is ‘not alarmed’):
• reference switch complete, and reference switch fail (BITS facilities)
• timing generation entry to normal, equipment protection switch complete,
and equipment protection switch fail (ESI circuit pack group)
• reference switch complete (OC-192 facilities)
A default status of ‘alarmed’ means an alarm is generated with its default
severity. An alarm provisioned as ‘not alarmed’ is generated with a severity of
‘warning’.
System initiated conditions

Conditions detected by the OPTera Long Haul 1600 network element (such as
failures) trigger visual and audible indicators. System initiated conditions are
the following:
• circuit pack failure
• loss of signal
• alarms (critical, major, minor)
• power supply monitoring
System initiated actions
The following is a list of system initiated actions from the OPTera Long Haul
1600 network element alarm reporting:
• alarm and event reporting (alarms are reported first in order of severity,
followed by reporting of events).
• flow control (to prevent the network element from potentially flooding the
UI with too many reports during periods of high alarm and alert activity,
the alarm reporting component stops sending reports temporarily)
Note: Even under flow control, the alarms are visible at the NE UI
(however the alarm counts may not be accurate). The operation controller
(OPC) and Network Manager do not receive the alarms or events until the
flow control is inactive.
• system restarts (all active alarms and alerts set to off during a restart are
re-evaluated after the restart, and the appropriate alarms and alerts are
raised).
Note: All alarm/alert history and alarm provisioning change logs are
maintained after restarts.

User initiated actions

The user generated actions that cause visual and audible indicators result from
a user command or by way of a button controlled by the user.
The local craft access panel (LCAP) contains the following buttons that can
change the state of visual and audible indicators:
• alarm cutoff (ACO): to acknowledge an alarm condition and turn off the
audible indicator
• lamp test: to test light emitting diodes (LED) and lamps on all the circuit
packs, LCAP, and on the OPTera Long Haul 1600 bay
Also, the following commands entered at the NE UI level change the state of
the alarm indicators:
• alarm cutoff: same function as the ACO push button located on the LCAP
• lamp test: same function as the lamp test push button located on the LCAP
• circuit pack service state: capability for the user to select the service state
of a circuit pack (a circuit pack that is not in-service has no LEDs ‘on’)
You can perform the following actions on alarm event information:
• retrieval of alarm information and alarm counts
• provisioning of alarm information
• retrieval of alarm logs and event logs
• operation of the alarm cutoff
LCAP LEDs and push buttons
The LCAP contains several LEDs and push buttons, directly available to
maintenance personnel. For a look at the actual layout of the LCAP and the
positioning of its LEDs and pushbuttons, see Figure 1-1.

Figure 1-1
OPTera Long Haul 1600 local craft access panel alarm related indicators and push buttons
F3181
RS232
Headset
Call
Local
Express
Handset
Lamp test
Alarm cutoff
FW-3181
Power
Critical
Major
Minor
Breaker trip
ESD
Alarm cutoff (ACO) push button

The ACO push button mutes the audible alarm condition. The ACO indicates
the alarm acknowledgment to the network element software. The ACO also
clears the critical, major, and minor audible alarms. The ACO LED present on
the ACO button turns on when the user acknowledges an alarm.
Note: You can issue the ACO with the NE UI.
Lamp test
The lamp test button activates all the circuit packs, LCAP, and bay LEDs for a
fixed period of 30 seconds.
ACO LED
This green LED is on the ACO push button. When the user presses the ACO
push button, software activates the ACO LED. The ACO LED remains on until
the alarm clears. The ACO LED turns off, and the audible indication turns on
if a new alarm occurs.

Power LED
This green LED is hardware controlled and indicates the power status of the
OPTera Long Haul 1600 bay.
Critical, Major, Minor LEDs

These LEDs indicate that an alarm is active on the network element, and
indicate the severity of the alarm.
Circuit breaker trip LED

This red LED indicates one or more circuit breaker trips on the power breaker
modules that equip the OPTera Long Haul 1600 control shelf.

Bay lamps and contacts

The synchronization, alarms, and telemetry termination module (SATT), along
with the bay lamps are located at the top of the OPTera Long Haul 1600 bay,
as indicated in Figure 1-2. The SATT module gives access to the bay lamps and
audible alarm relays. The OPTera Long Haul 1600 network element supports
critical, major, and minor visual and audible alarms. Critical, major, and minor
alarms have an effect on all the bay lamps. Figure 1-3 shows the LED locations
on the various circuit packs supported by the OPTera Long Haul 1600.
Figure 1-2
OPTera Long Haul 1600 SATT module and bay lamps
OTP0326.eps
SATT wire wrap

connector field
Critical
Major
Minor
Bay lamps
FW-3153_iss2

Critical alarm
This red lamp indicates that one or more critical alarms exist on the network
element. The critical audible alarm activates under the same condition. (To
disable the audible alarm, press the ACO button.) The critical alarm lamp
remains active until the alarm condition clears. The OPTera Long Haul 1600
maintenance interface circuit pack contains relays for both visual and audible
critical alarms.
Major alarm
This alarm represents the second highest severity level of alarms on the
OPTera Long Haul 1600 network element. The major visual (red lamp) and
audible alarm indicators operate the same way as the critical alarms indicator.
The SATT contains the major alarm relays. A power failure on the OPTera
Long Haul 1600 maintenance interface raises a major alarm. This lamp is on
when one or more major alarms exist on the network element. The lamp
remains active until the alarm conditions clear.
Minor alarm
This yellow lamp is on when one or more minor alarms are present on the
network element. Both visual and audible minor alarms operate the same way
as the critical and major indicators. The OPTera Long Haul 1600 maintenance
interface circuit pack contains relays for both visual and audible minor alarms.
Note 1: A warning condition on the network element does not activate any
visual or audible indications.
Note 2: Alerts have no effect on any of the LEDs located on the OPTera
Long Haul 1600 bay.

Circuit pack LEDs

This section deals with the location and meaning of the various light emitting
diodes (LEDs) that are on the front of every circuit pack.
CAUTION
Risk of service interruption
Do not take any trouble clearing actions based only on
the LED states. Always review the active alarms and
follow the required alarm-clearing procedures. Before
you remove a circuit pack, use the NE UI to make sure
that the circuit pack does not carry any live traffic.
Control shelf circuit packs, and the Timing Distribution Card (TDC)
introduced in Release 2 on the OPTera Long Haul 1600 combiner network
element, have two LEDs to indicate the status of the circuit pack. A green LED
indicates that the circuit pack is active and a red LED indicates a failure.
The following optical circuit packs have a third LED, which is yellow and
represents a loss of signal (LOS):
• 2.5G WT (Rel. 1.2)
• 10G WT (Rel. 1.5)
• OC-192/STM-64 XR (Rel. 1.5)
• OC-48/STM-16 T/R (Rel. 2.0)
• OC-192/STM-64 T/R (Rel. 2.0)
The MOR Plus circuit pack has four LEDs. There are two yellow LEDs, in
which one represents a LOS on the blue band, the other, a LOS on the red band.
For a graphic representation on the LED locations of the various supported
circuit packs on the OPTera Long Haul 1600 Repeater and Combiner network
elements, refer to Figure 1-3.
For the Amplifier, there are a number of new circuit packs that are supported
in addition to the Control Shelf circuit packs which are identical to the
Repeater configuration. The new circuit packs all have the active and fail
LEDs. The Dual amplifier (D-AMP), the Optical Service Channel (both Uni
and Bi OSC ), and booster +18/+21 circuit packs also have two yellow LEDs.
The upper representing a LOS for traffic in, and the lower LED representing a
LOS for the OSC.
For a graphic representation on the LED locations of the various supported

circuit packs on the Amplifier network element, refer to Figure 1-4.

Figure 1-3
LED locations on supported circuit packs for the OPTera Long Haul 1600 Repeater and Combiner
OTP0327.eps
Control shelf TDC circuit pack MOR Plus 2.5G WT (Rel. 1.2)
circuit pack (Rel. 2.0) (All releases) 10G WT (Rel. 1.5)
OC-192/STM-64 XR (Rel. 1.5)
OC-48/STM-16 T/R (Rel. 2.0)
OC-192/STM-64 T/R (Rel. 2.0)
Legend
- Yellow (LOS Blue) MOR Plus

- Yellow (LOS Red) MOR Plus
- Yellow (LOS)
- Red (Fail)
- Green (Active)

Figure 1-4
LED locations on supported circuit packs for the Amplifier
OTP0906
1 Amp
2 OS
Uni-OSC Circuit Pack Booster +18/+21

Bi-OSC Circuit Pack Circuit Pack
DAMP Circuit Pack
Legend
- Red (Fail)
- Green (Active)
- The label '1' or 'Amp' represents a LOS for traffic
- The label '2' or 'OS' represents a LOS for the OSC

LED Definitions
Red LED
Each circuit pack has a red LED. When turned on, the red LED indicates that
the circuit pack has partially or completely failed. The red LED turns off when
the circuit pack is out of service.
Yellow LED
Only cards that receive a signal external to the shelf (for example, the 2.5G
WT) have a yellow LED. When turned on, the yellow LED indicates a loss of
signal condition on the card where the signal terminates. The facility state has
an effect on the yellow LED. When the facility is out of service, the yellow
LED turns off.
Green LED
When turned on, this LED indicates the service providing status of the circuit
pack. Normally the green LED is off when the red LED is on. If there is an
unprotected failure on the circuit pack, both the green and red LEDs are on.

2-1
Surveillance interfaces 2-
This chapter describes the different surveillance interfaces available for the
OPTera Long Haul 1600 network element.
Network element user interface

The OPTera Long Haul 1600 network element user interface (NE UI) allows
the user to perform alarm monitoring and analysis tasks. OPTera Long Haul
1600 Release 3 encompasses four network elements. They are, the Repeater,
Combiner, Optical Amplifier Shelf (OAS), and the Amplifier. Each network
element offers a slightly different variation of the NE UI.
You can access the NE UI by way of a VT-100 terminal connected to the

network element. Alarm reports sent to the NE UI provide alarm indications.
The following illustrations present the various OPTera Long Haul 1600 NE UI
main menu windows:
Figure 2-1
NE UI main menu for the OPTera Long Haul 1600 Repeater
OTP1038.eps
Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 11:45
Main Menu
---------
1. ALarMs
2. Performance Monitoring
3. PRotection
4. EQuipment
5. FAcility
6. Optical FAcility
7. ADministration
8. LOGOUT
9. HELP

2-2 Surveillance interfaces
Figure 2-2
NE UI main menu for the OPTera Long Haul 1600 Combiner
OTP1037.eps
Main Menu
---------
1. ALarMs
2. Performance Monitoring
3. PRotection
4. EQuipment
5. FAcility
6. Optical FAcility
7. PayLoad
8. ADministration
9. LOGOUT
10. HELP
Figure 2-3
NE UI main menu for the OPTera Long Haul 1600 Amplifier
OTP1037.eps
Main Menu
---------
1. ALarMs
2. PRotection
3. EQuipment
4. OTR FAcility
5. ADministration
6. LOGOUT
7. HELP
Note: In each of the NE UI main menus shown above, the top line contains
the existing alarm counts for the different severities. For example, the
alarm counts in any of the above samples are:
• 0 Critical alarms
• 1 Major alarm
• 36 minor alarms
• 0 warning alarms

Alarm related menus

The NE UI is menu driven. You can move through these menus to access alarm
information.
Alarm menu
Select the alarm menu from the main menu to display either all active alarms
or historical alarms. This screen shows the alarm menu and the options
available to you.
Figure 2-4
Network Element User Interface Alarm menu
OTP1041.eps
Alarm Menu
----------
0. Quit
1. list all active ALarms
2. list all active ALarms by Severity
3. list all active ALarms by Class
4. ALarm Details
5. List all Historical alarms
NE 2128>

Active alarms
From the active alarms option, you have the option to view the following:
• the total list of alarms
• a list of alarms sorted by severity or class
• alarm details related to each alarm
The first of the following screens shows an example of a list all active alarms.
The second screen shows an example of an alarm details display.
Figure 2-5
“list all active ALarms” menu option
OTP0361.eps
Alarm Menu
----------
0. Quit
4. ALarm Details
5. List all Historical alarms
NE 2128> a1
Alm# Cls Sh Type Unit Reason Sev

28 Eqp 1 OPC G1 OPC storage circuit pack missing m,nsa
27 Eqp 1 OPC G1 OPC controller circuit pack missing m,nsa
1 Env 1 CE High shelf temperature m,nsa
NE 2128>
Figure 2-6
“ALarm Details” menu option
OTP0358.eps
xterm
----------------
8. LOGOUT
9. HELP
NE 20> ALM
Alarm Menu
----------
0. Quit
4. ALarm Details
5. list all Historical alarms
NE 20> ALD
Enter the alarm ID:
[ 1-9999]
? 27
Alm Rpt: 27 Minor
Unit: OPC G1 nsa
Address: 2048 Shelf: 1 10:48:36
Location: Frame: - shPos: 1 Slot: 5 01-11-99
Reason: OPC controller circuit pack missing EQP
Equip ID: PEC:
NE 20>

Historical alarms
The historical alarms list displays a detailed list of alarms that occurred. The
historical alarms list also displays active alarms. See the following figure.
Figure 2-7
“list all Historical alarms” menu option
OTP0357.eps
xterm
Alarm Menu
----------
0. Quit
4. ALarm Details
5. list all Historical alarms
NE 2128> LH
ALM300 MAY 10-2000 18:49:50 8692 Facility alarm

Initiated by: SYSTEM
AlmRpt: 14 Cleared
Unit: OTR G0 2 nsa
Address: 2128 Shelf: 2 18:49:50
Location: Frame: ShPos: 2 10-05-00
Reason: OSC loss of signal FAC
Fac ID:
ALM300 MAY 10-2000 00:34:00 8318 Facility alarm

AlmRpt: 92 Cleared
Unit: OTR G5 1 nsa
Address: 2128 Shelf: 2 00:34:00
Location: Frame: ShPos: 2 10-05-00
Reason: OSC DCC link fail FAC
Fac ID:
- More ('ht' to halt; <CR> to print next screen; n <CR> to print next n lines)-

Operations controller
The operations controller user interface (OPC UI) provides central operations,
administration, maintenance, and provisioning (OAM&P) for multiple OPTera
Long Haul 1600 network elements. Network elements controlled by the same
OPC are all in the same OPC span of control. The OPC communicates with the
shelf controller and the maintenance interface to provide system control,
network surveillance, and alarm correlation.
Note: The status line at the bottom of the OPC UI screen displays a set of
alarm and protection counts. Any count that is greater than 999 appears in
the status line as 999. The 999 code means the real count is 999 or greater.
Other tools display the full numbers. For example, the Alarm Monitor tool
has a banner line at the top of the screen to display the full numbers.
OPC network surveillance environment

The network surveillance functions of the OPC UI allow for quick trouble
clearing of a failure in the network. The surveillance functions of the OPC UI
provide alarm reporting capabilities by the following tools: Alarm Monitor,
Event Browser, Network Summary, and the Network Browser. These tools are
available under the Network Surveillance toolset as shown in Figure 2-8.
Figure 2-8
OPC UI - User Session Manager menu
OTP0377.eps
FW-20358
>. User Session Manager : netsurv
Available tools Open tools
Toolset/Tools ID State Tool

Network Surv. 2 >.OK OPC Status:Primary/Active
Alarm Monitor 3 >.OK Alarm Monitor
Network Summary 4 >.OK NE Login Manager
Event Browser
Network Browser
Utilities
NE Login Manager
Password Update
[ Logout ]
C 0 M 0 m 1 w 2 FailProt - Lckt 0 ActProt 0 PrfAlrt - 16:33

Alarm Monitor
The Alarm Monitor tool allows you to view alarm counts for all OPTera Long
Haul 1600 network elements in the OPC span of control. The tool provides
submenus to display or print detail information about each alarm. For a
description of the various submenus, see Figure 2-9.
Note 1: An asterisk (*) in the Time column of this tool indicates the alarm
occurred at least one day before the current date of the OPC.
Note 2: When you put an entity out of service (OOS), and that entity has
an alarm against it, the alarm clears. When you put this same entity back
in service (IS) without correcting the cause of the alarm, the alarm raises
again. The time stamp of the alarm has the same value as the time stamp
when the alarm was first raised.
Note 3: When you provision an entity as ‘not reported’, and that entity has
an alarm against it, the alarm clears. When you provision this same entity
back to ‘reported’ without correcting the cause of the alarm, the alarm
raises again. The time stamp of the alarm has the same value as the time
stamp when the alarm was first raised.
Figure 2-9
Alarm monitor window with available submenus
OTP1098.eps
Options menu
>. Alarm Monitor Options
Window menu Critical Major1 Minor
Exit Warning
) FailProt Lockout ActProt PrfAlrt
1 Clear highlighting Ctrl+X F
Network View Network View . 4 . . 2 .Show all
. . .
2 Help H
banner 3 Display options... >>
4 Help
Alarms sorted by severity [*] Auto Update List
Showing: All Severities, All NEs, OPC
Alarm list NE# NE Name Alm# Cls Sh UnitDS3 Reason Time Sev
? 71 radstone 0 Eqp 1 CE 1 Circuit
Filter... F
pack missing 09:20:29 M,SA
? 16 Amsterd 1306Details...
Env 1 DS3 D 2 Circuit
Sort pack missing 09:12:38 m,nsa
3 Circuit 1 by
Update Lpack severity
missing
List menu ? 71 radstone 23 Fac 1 DS3 09:20:30 m,nsa
2 by network element
? 71 radstone 2 22
Select
Fac 1 DS3 >> Circuit pack missing 09:20:30 m,nsa
3 by time
? 71 radstone 3 21
Deselect
Fac 1 DS3 >> 4 Circuit
Help pack missing 09:20:30 m,nsa
? 71 radstone 20 Fac 1 DS3 Circuit pack missing 09:20:29 m,nsa
? 71 radstone 4 19
Print
Fac Details
1 DS3 Circuit pack missing 09:20:29 m,nsa
? 71 radstone 18 Fac 1 DS3 Circuit pack missing 09:20:29 m,nsa
List item menu ? 71 radstone 17 Fac 1 OC48 G8H
5 Help Circuit pack missing 09:20:29 m,nsa
? 71 radstone 16 Eqp 1 OC192 G5 Circuit pack missing 09:20:29 m,nsa
? 71 radstone 13 Eqp 1 Circuit pack missing 09:20:29 m,nsa

Event Browser
The Event Browser tool allows you to see records of OPC logs, OPC and
network element alarms, and alerts. The tool provides submenus to display or
print detailed information about each alarm. For a description of the various
submenus, see Figure 2-10.
Note 1: An asterisk (*) in the Time column of this tool indicates the alarm
occurred at least one day before the current date of the OPC.
Note 2: When you put an entity out of service (OOS), and that entity has
an alarm against it, the alarm clears. When you put this same entity back
in service (IS) without correcting the cause of the alarm, the alarm raises
again. The time stamp of the alarm has the same value as the time stamp
when the alarm was first raised.
Note 3: When you provision an entity as ‘not reported’, and that entity has
an alarm against it, the alarm clears. When you provision this same entity
back to ‘reported’ without correcting the cause of the alarm, the alarm
raises again. The time stamp of the alarm has the same value as the time
stamp when the alarm was first raised.
Figure 2-10
Event browser window and available submenus
OTP1087.eps
> . Event Browser 1 Exit )

Window menu Auto-update: [OFF]
25 Events sorted by time 2 Help H [ Update List ]
Showing: OPC logs,all NE logs, alarms, alerts, all sev, and all NEs
Event list NE# NE Name Evt# Cls Unit Reason Date Time Sv
9215 292 Stat log COM501 OPC to NE 12 17
1 Filter... F Jul 15:34:10 w
9215 291 Stat log COM502 OPC to NE 12 17
2 Sort... : Jul 15:33:40 M
9215 290 Trbl log NAD351
3 ShowCannot colle 17 Jul
details... 15:12:52 m
9215 289 Cmpl log GEN618 Log/Alarm da 17
4 Auto-update... W Jul 15:06:20 w
List menu 9215 288 Stat log COM501 OPC to NE 12 17 Jul 15:06:16 w
9215 287 Cmpl log 5 HelpLoc/Alarm da 17
GEN618 H Jul 14:43:32 w
9215 286 Stat log COM501 OPC to NE 12 17 Jul 14:43:26 w
1 Details... D
9215 284 Stat log COM502 OPC to NE 12 17 Jul 14:31:09 M
2 Select >>
9215 283 Cmpl log GEN618 Log/Alarm da 17 Jul 14:28:36 w
List item menu 3 Deselect
9215 282 1>>to here
Stat log COM501 OPC to NE 12 17 Jul 14:28:31 w
9215 281 2Trbl
thislog
item NAD351 Cannot colle 17 Jul 14:11:47 m
4 Print Details 3Trbl
all log A
9215 280 NAD351 Cannot colle 17 Jul 13:11:29 m
9215 279 Trbl log NAD351 Cannot colle 17 Jul 12:11:29 m
5 Help H
9215 278 Cmpl log GEN618 Log/Alarm da 17 Jul 11:35:58 w

Network Summary
The Network Summary tool allows you to monitor the status of the network
from the main window. The total count of alarms, protection switches, and
performance alerts indicates status changes for network elements in the OPC
span of control. See Figure 2-11 for an example of the Network Summary
window.
Figure 2-11
Network summary window and available submenus
F20669-192_R60
FW 20669(O
>. Network Summary

Window menu 1 Exit )
Critical Major Minor Warning FailProt Lockout ActProt PrfAlrt
Network View Network View . . *1* . . . . .
2 Help
banner
Show Alarm Showing alarms: active and (*) New since reset (*) Cleared since reset
boxes
Network Element Reset Crit Major Minor 1 Warn
Reset Fail
All Counts
Lock Ctrl+X F
Act Prf
Network 0 OPCM2266P 14:46 Act . . . . . . . .
New . . 2 2 Help
. . . . H
.
Element list
Clr . . . . . . . .
+70 18:46 Act . . . . . . . .
List menu New . . . . . . . .
Clr . . 1 . Reset .Counts . . . .
2 Select >>
List item menu 3 Deselect >>
4 Help H
Status line C 0 M 0 m 2 w 2 FailProt - Lckt 2 ActProt 1 PrfAlrt - 15:58

Network Browser
This tool allows you to view network status information. Information on
alarms, protection, and performance data for all network elements in the OPC
span of control is displayed. The Network Browser also allows you to display
details about each network element. See Figure 2-12 for an example of the
Network Browser window.
Figure 2-12
Network Browser window and available submenus
OTP0427.eps
>• Network Browser

1 Exit )
Window menu
Network: Atlantic Canada
System: Atlantic 1 2 Help H
Network element Network Element Fac Eqp Env FailPro Lockout ActProt PrfAlrt
list 0 OPCM2266P . . . - . . -
9215 1 Sort >>
. 1 by
. alarm
. . . 3DS3 -
severity
9216 . 2 by
. network
. .
element . . -
List menu 9217 2 Help .H . . . . . -
9218 . . . - . . -
2000 . 2M+ . - 10DS3 . -
2001 . . . - . . -
2002 . . . - . . -
2003 . . . . . . -
2004 . . . . . . -
2005 1 Shelf
. details
. . D. . . -
2 Select 1>>
to here
2>>
this item
List item menu 3 Deselect
3 all A
4 Help H
TL1 interface
The network surveillance functions of the Transaction Language 1 (TL1)
Interface allow you to:
• get autonomous alarm reports in real time
• retrieve threshold crossing alerts, events, and logs
• manually retrieve alarms
The OPC generates TL1 autonomous messages caused by activity on the
network elements included in the OPC span of control. The operations system
(OS) automatically receives reports of alarms, protection switching activity,
threshold alerts, and warnings.
Non-autonomous messages are requests from the operations system and

responses from the OPC. For example, the message from the OS can be a user
request for any minor alarms from a network element. The OPC then sends the
required response. For more detailed information about TL1, refer to
TL1 Interface Description, 323-1801-190.

Preside, Network Management software

Preside is a graphic surveillance tool providing network management for the
S/DMS TransportNode product line. The tool provides a single point of access
for all the operation, administration, maintenance and provisioning (OAM&P)
functions of a multispan transport network. Preside also provides a complete
view of all network alarms through a graphic representation of the network
topology. The network can contain several subnetworks of OPTera Long Haul
1600, OC-192, OC-48, OC-12, and OC-3 network elements. The OPCs
(primary and backup) manage each subnetwork. A subnetwork (or span of
control) is an area wherein the same primary and backup OPCs manage all the
network elements.
The graphic representation provides a visual tool to manage multi-span

transmission systems. The graphic representation also allows the network
administrator to:
• get a complete status view of a large S/DMS TransportNode network
• locate fault conditions down to the circuit pack level
• analyze the whole network through a graphic view of alarm status for all
network elements managed by several OPCs
• get full access to the OAM&P functions of the OPCs and network elements
• get login access to the network elements and the OPCs
Preside is an optional software application, and operates on a workstation
platform. For more information, see Preside Application Management User
Guide, 450-3101-221.
Parallel telemetry
Parallel telemetry is a common type of surveillance that allows a network
element to monitor or control customer equipment. The network element can
support parallel telemetry on a dedicated circuit pack. This parallel telemetry
card can support up to 32 parallel inputs and eight parallel outputs. See Figure
2-13 for an example of parallel telemetry applications.
Parallel inputs
The parallel input telemetry points (or scan points) allow the customer to
connect external equipment (detectors) to the network element. When the
customer connected equipment triggers a parallel input point, it raises a minor
non-service affecting alarm.
Parallel outputs
The parallel output telemetry points allow the customer to connect external
equipment (reactors) to the network element. The network element can trigger
the operation of the connected external equipment.

Figure 2-13
Parallel telemetry applications
F0048
External customer inputs Relay outputs
(Monitor external alarm (Executable commands

and status points) for external control)
Power
failure
Fire Lights and

flashers
Open Bells
door TransportNode TransportNode
network network
element element
Flood Generators,
heaters and
air conditioners
High
temperature
Low
temperature

3-1
Support tools 3-
This chapter describes the various support tools that are provided by the
OPTera Long Haul 1600 network element. In addition to alarm indicators and
surveillance interfaces, these tools provide information to help the user
perform trouble clearing tasks.
Logs
Log reports are sources of information. Logs provide information about
changes of state and other important events that occur on the OPTera Long
Haul 1600 network element.
A log often indicates a problem with the system. A log can provide additional
information to alarm reports. Both the OPC and the OPTera Long Haul 1600
network element generate logs.
See Log Reference, 323-1801-840 parts 1 & 2, for a complete list and
description of network element logs and OPC logs.
Log types supported

For the OPTera Long Haul 1600 network element, the supported types of
network element logs are:
• alarm (ALM): events related to a raised or cleared alarm
• alarm provisioning (ALP): events related to the provisioning of alarms
• alert (ALT): events related to a raised or cleared alert
• communication (COML): events related to communication setup and to
call-clearing between network element to network element, and network
element to OPC
• environment (ENV): events related to environmental occurrences
• equipment (EQP): events related to circuit packs, circuit pack groups,
shelves and hardware
• facility (FAC): events related to facility provisioning (for example: create,
delete, state change, and parameter editing)

3-2 Support tools
• FiberWorld database (FWDB): events related to database operations of

FiberWorld network element (for example: database backup, database
restore, and journal entry)
• network element (NE): events related to the creation, deletion, or
modification of a network element
• payload (PLD): events related to payload faults
• performance monitoring (PM): events related to performance monitoring
• security (SECU): events related to user account related changes, logins,
logouts, forced logouts, attempts to execute unauthorized commands, alias
or superuser commands
• software, configuration, upgrades and downloads (SCUD): events that
relates to software management, uploads, and downloads
For the OPTera Long Haul 1600 network element, the supported types of OPC
logs are:
• communication (COM): logs related to communication between the
network element and the OPC
• general (GEN): logs related to OPC software problems
• network administration (NAD): logs related to the administration of
subnetworks
• software data administration (SDA): logs related to software load requests
and software load downloads, between network elements and the OPC
• standby (STBY): logs related to the primary and backup OPCs in a span of
control
Log numbering
Table 3-1 shows the types of log events.
Table 3-1
Log numbering scheme
Number Log Description
300-399 Trouble Trouble indicates a problem.
400-499 Usage Usage indicates the use of a resource or service.
500-599 State State Changes indicates an important change in status.

Changes
600-699 Completion Completion indicates the completion of a process.
700-799 Progress Progress indicates that a process started.
800-899 Debug log Debug log for internal use only.

Support tools 3-3
Description of log record fields

Here is an example of a typical log record:
NE402 MAY12-1999 22:30:28 0263 Data Change
Parameter Changed: TMSECR
Present Value: 0
Previous Value: 101
Network ID:
system ID
NE ID: 9213
Other fields provide a description and the location of the event.
In the previous example, the first line (also called the “header”) of the log
record contains the following fields:
• report name: NE402, network element log, number 402
• date: MAY12-1999
• time: 22:30:28, where the time format is HH:MM:SS (HH is the hour on a
24-hour clock, MM is minutes, and SS is seconds)
• sequence number: 0263, the sequence of actions that occurred (the number
increases for an event that occurred later)
• description: Data Change, a short description of the log report
System initiated actions
To prevent the loss of log records in the event of a restart, the system restores
the data from the FLASH file.
User initiated actions

The user can initiate log record queries in the login domain.

3-4 Support tools
Performance monitoring
The performance monitoring (PM) capabilities of the OPTera Long Haul 1600
network element provide monitoring of transmission quality. This feature
allows early detection and isolation of signal degradation, to improve system
troubleshooting. See Performance Monitoring Procedures, 323-1801-520 for
more information.
The purpose of performance monitoring is to:

• gather performance indicators
• get parameter counts from the unformatted indicators
• store performance statistics
• check and report threshold crossings for groups of monitored entities for
the enabled thresholds
Performance monitoring allows you to find faults, without a change in service.
Performance monitoring information is available from the NE UI or OPC UI.
This information is available from the OPC through the TL1 interface or
through the Network Manager.
Valid PM parameters are:

• code violations (CV)
• errored seconds (ES)
• severely errored seconds (SES)
• severely errored frame seconds (SEFS)
• unavailable seconds (UAS)
• failure counts (FC)
• forward error corrections (FEC)
The following are the performance monitoring parameters of traffic carrying
facilities:
• line PM parameters (CV, ES, SES, UAS, FC, and FEC)
Note 1: The FEC parameter is for OC-192/STM-64 only.
Note 2: Line PM is only supported for OPTera Long Haul 1600 Combiner,
Release 2.
• section PM parameters (CV, ES, SES, and SEFS)
• intermediate path PM parameters (CV, ES, SES, UAS, and FC)

Support tools 3-5
The following are the parameters of physical performance monitoring:

• optical power received (OPR) on OC-192/STM-64 only
• indication of quality (IQ) on OC-192/STM-64 only
There can be a crossing of a parameter provisioning threshold during a current
collection period. In this event, the PM system raises a Threshold Crossing
Alert (TCA). The user interface receives this alert as an event report.

3-6 Support tools

Nortel Networks
OPTera Long Haul 1600

Optical Line System
Fault Detection
Copyright  2000 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel

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

the World Shares Ideas, S/DMS TransportNode, OPTera,
Preside, and Unified Networks are trademarks are trademarks of
Nortel Networks.
VT100 is a trademark of Digital Equipment Corporation.

UNIX is a trademark of X/Open Company Ltd.
323-1801-541
Rel 3 Standard
July 2000
Printed in Canada and in the United Kingdom

Fault Detection

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fault Detection

Uploaded by

Copyright:

Available Formats

323-1801-541

Rel 3 Standard July 2000

UNIX is a trademark of X/Open Company, Ltd.

Printed in Canada and in the United Kingdom

Local alarm indicators 1-1

Surveillance interfaces 2-1

Support tools 3-1

Fault Detection 323-1801-541 Rel 3 July 2000

Description of log record fields 3-3

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

About this document 0

Fault Detection 323-1801-541 Rel 3 July 2000

OPTera Long Haul 1600 NTP Library

323-1801-091 About the OPTera Long Haul 1600 Library

Engineering and Planning

NTY311AX Repeater Network Application Guide

Installation, Commissioning, and Testing

323-1801-201 Installation Procedures

Operations, Administration, and Provisioning

323-1801-301 User Interface Connection Procedures

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

323-1801-520 Performance Monitoring Procedures

Fault Detection 323-1801-541 Rel 3 July 2000

Fault Detection Summary

• Access the NE UI from the VT-100 terminal

• Access the OPC UI from the VT-100 terminal

• Access TL1 interface

• Access the Network Manager

• Access the Parallel telemetry

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

Local alarm indicators 1-

For information on how to display alarm details, refer to Alarm Reference

Network Element NTP Title & Number

Repeater Trouble Clearing and Module Replacement,

Combiner Trouble Clearing and Module Replacement,

Amplifier 1600G Amplifier Alarm Clearing and Module

Alarm and alert severity

Fault Detection 323-1801-541 Rel 3 July 2000

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

System initiated conditions

Fault Detection 323-1801-541 Rel 3 July 2000

User initiated actions

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

Alarm cutoff (ACO) push button

Note: You can issue the ACO with the NE UI.

Fault Detection 323-1801-541 Rel 3 July 2000

Critical, Major, Minor LEDs

Circuit breaker trip LED

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

Bay lamps and contacts

SATT wire wrap

Fault Detection 323-1801-541 Rel 3 July 2000

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

Circuit pack LEDs

For a graphic representation on the LED locations of the various supported

Fault Detection 323-1801-541 Rel 3 July 2000

- Yellow (LOS Blue) MOR Plus

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

Uni-OSC Circuit Pack Booster +18/+21

Fault Detection 323-1801-541 Rel 3 July 2000

OPTera Long Haul 1600 323-1801-541 Rel 3 Standard July 2000

Network element user interface

You can access the NE UI by way of a VT-100 terminal connected to the

Fault Detection 323-1801-541 Rel 3 July 2000