LH 1600 Alarm Reference Guide

323-1801-542

Nortel Networks

OPTera Long Haul 1600 Optical Line System Alarm Reference Guide

Rel 3 Standard July 2000

What’s inside...

Alarm and trouble clearing guidelinesAlarm definitions

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

Alarm Reference Guide 323-1801-542 Rel 3 July 2000

iii

Contents 0About this document v

Alarm and trouble clearing guidelines 1-1Alarm Reporting 1-1Clearing alarms 1-2

Identifying the alarm 1-2Using the alarm-clearing procedures 1-3

Clearing multiple-alarm conditions 1-4Group alarms 1-5Event alerts 1-5OPC Alarms 1-5Supporting tools and indicators 1-6

Historical alarms 1-6The OPC surveillance environment 1-7Monitoring alarm status by the OPC 1-7

List of procedures1-1 Displaying the OPC status 1-111-2 Checking the network 1-141-3 Displaying detailed information about a shelf 1-171-4 Sorting the network element list 1-211-5 Customizing the network element alarm count list 1-251-6 Identifying a change in network status 1-281-7 Resetting the new and cleared alarm counts for selected network elements in

the span of control 1-321-8 Resetting the new and cleared alarm counts for all network elements in the

span of control 1-351-9 Displaying a detailed event report 1-381-10 Sorting the Events List 1-421-11 Updating the Events List manually 1-471-12 Enabling, disabling, or changing the auto-update feature for the Events

List 1-491-13 Filtering the Events List 1-551-14 Printing event details 1-631-15 Displaying the alarm details for a new alarm 1-681-16 Displaying an active alarm 1-721-17 Defining the user view and display options 1-751-18 Defining a filter 1-801-19 Changing the contents of the list of alarms 1-86

iv Contents

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

1-20 Sorting the list of alarms 1-891-21 Updating the list of alarms 1-921-22 Printing alarm details 1-951-23 Displaying active alarms 1-991-24 Displaying active alarms according to severity 1-1021-25 Displaying active alarms according to class 1-1051-26 Displaying alarm details 1-1081-27 Displaying historical alarms 1-1111-28 Displaying OPC alarms and the OPC pointer alarm status and severity 1-1141-29 Enabling and disabling OPC alarms 1-1161-30 Clearing OPC alarms 1-1211-31 Provisioning the network element to raise the pointer alarm 1-1241-32 Enabling and disabling the OPC pointer alarm 1-1281-33 Changing the severity of the OPC pointer alarm 1-133

Alarm definitions 2-1Equipment alarms 2-11

Generic equipment alarms 2-11Common equipment alarms 2-23External synchronization interface (ESI) equipment alarms 2-30OPC equipment alarms 2-32Shelf equipment alarms 2-36Orderwire equipment alarms 2-36

Facility alarms 2-38Generic facility alarms 2-38External synchronization interface (ESI) facility alarms 2-47Performance monitoring facility alarms 2-48OC-192 4-Fiber BLSR/STM-64 MS-SPRing facility alarms 2-51

Environmental alarms 2-52Common equipment environmental alarms 2-52Parallel telemetry environmental alarms 2-55

Alerts 2-56Generic alerts 2-56Performance monitoring alerts 2-58


v

About this document 0This document provides alarm and trouble clearing guidelines for the Nortel Networks OPTera Long Haul 1600 Optical Line System (formerly OPTera LH) Repeater and Combiner network elements. Topics covered include the following:

• guidelines for alarms and trouble clearing

• procedures to monitor alarm status using the Operations Controller (OPC) and Network Element User Interface NE UI)

• descriptions of all alarms

Note 1: For alarm definitions and clearing procedures on alarms associated with the MOR Plus fibre-optic link, refer to the MOR Plus Alarm Clearing and Module Replacement, 323-1801-545.

Note 2: For alarm definitions and clearing procedures on alarms associated with the 1600G Amplifier, refer to the 1600G Amplifier Alarm Clearing and Module Replacement, 323-1801-546.

AudienceThis document is for the following members of the operating company:

• planners

• provisioners

• network administrators

• transmission standards engineers

• maintenance personnel

vi About this document


ReferencesThis document refers to the following Nortel Networks technical publications (NTP) of the OPTera Long Haul 1600 Optical Line System Library:

• Network Element User Interface Description, 323-1801-195

• OPC User Interface Description, 323-1801-196

• Installation Procedures, 323-1801-201

• Powering Up and Commissioning Procedures, 323-1801-220

• Provisioning and Operations Procedures, 323-1801-310

• Performance Monitoring Procedures, 323-1801-520

• Fault Detection, 323-1801-541

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

• MOR Plus Alarm Clearing and Module Replacement, 323-1801-545

• 1600G Amplifier Alarm Clearing and Module Replacement, 323-1801-546

• Log Reference, 323-1801-840

• Preside Application Management User Guide, 450-3101-221

About this document vii


OPTera Long Haul 1600 Optical Line System NTP LibraryThe following figure shows the documentation structure of the OPTera Long Haul 1600 NTP Library.

Installation, Commissioning, and Testing

323-1801-201 Installation Procedures323-1801-220 Powering Up and Commissioning Procedures323-1801-221 Site Testing Procedures323-1801-222 System Commissioning and Testing Procedures323-1801-225 MOR Plus SLAT and Upgrade Procedures323-1801-226 1600G Amplifier SLAT and Upgrade Procedures

Operations, Administration, and Provisioning

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

Network ApplicationsSupported

Engineering and Planning

NTY311AX Repeater Network Application GuideNTY312AX Combiner Network Application GuideNTY314AX 1600G Amplifier Network Application GuideNTY312DX 100 GHz MOR Plus 2 to 32-λ Optical Layer Applications GuideNTY311DX 200 GHz MOR/MOR Plus 2 to 16-λ Optical Layer Applications GuideNTY313DX MOR Plus Optical Add/Drop Applications GuideNTY314DX MOR Plus Optical Layer OAM&P GuideNTY315DX 1600G Amplifier Optical Layer Applications GuideNTY317DX 1600G Amplifier Optical Layer OAM&P GuideNTCA66CA SONET Orderwire User GuideNTCA66DA SDH Orderwire User Guide323-1801-190 TL1 Interface Description323-1801-195 Network Element User Interface Description323-1801-196 OPC User Interface Description323-1801-197 1600G Amplifier Fiber Assist Tool Description

Library Introduction, List of Terms, and Master Topical Index

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

1600G Amplifier

Repeater

Combiner

MOR Plus

-continued-

viii About this document


Network ApplicationsSupported

Maintenance

323-1801-520 Performance Monitoring Procedures323-1801-541 Fault Detection323-1801-542 Alarm Reference Guide323-1801-543 Trouble Clearing and Module Replacement323-1801-545 MOR Plus Alarm Clearing and Module Replacement323-1801-546 1600G Amplifier Alarm Clearing and Module Replacement323-1801-840 Log Reference

1600G Amplifier

Repeater

Combiner

MOR Plus

323-1301-XXX OC-192 NTP Library323-1321-XXX TN-64X NTP Library323-1201-XXX OC-48 NTP Library323-1211-XXX TN-16X NTP Library450-3101-XXX Preside DocumentationNTR710AM Optical Networks Data Communications Planning GuideNTCA65DA 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 LibraryNTCA65KA OPTera Connect DX NTP Library (OPTera Connect DX SDH & TN-64X platforms)

Supporting Documentation to the OPTera Long Haul 1600 Library (not part of this library)

About this document ix


Alarm Reference Guide procedures SummaryMain tasks:

• Alarm and trouble clearing guidelines

• Monitor the OPTera Long Haul 1600 NE

— Use NE UI and surveillance from the OPC to identify the alarms.

— Use Trouble Clearing and Module Replacement, 323-1801-543 to clear the alarms.

• Display the OPC status

— Access the OPC UI (Procedure 1-1)

— Select the OPC status from the User Session Manager menu.

• Browsing the network

— Log into the OPC and open the network browser tool (Procedure 1-2).

— Check the status of the OPC and of all NE in the OPC span of control.

— Press Ctrl+L to display the List item menu.

— Display the shelf detail summary (Procedure 1-3).

— Press Ctrl+L, G from the network browser tool, to display the List menu.

— Choose sort to sort the NE list (Procedure 1-4).

• Monitoring network alarm status

— Log into the OPC and open the network Summary tool.

— Select the New since reset or Cleared since reset to customize the NE alarm count list (Procedure 1-5).

— Check the Network view banner to identify any change in the network status (Procedure 1-6).

— From the network summary tool display the new and cleared alarms on all NEs and OPCs.

— Select Reset Counts in the list item menu to reset the alarm counts for the NE or OPC. (Procedure 1-7).

— Select the Reset all counts to reset the alarm counts for all NEs and OPCs. (Procedure 1-8).

x About this document


• Viewing logs, alarms, and alerts at the OPC

— Select an event from the Event Browser Tool.

— Use show details to display detailed event report (Procedure 1-9).

— Select the sort item from the event list menu to sort the event list (Procedure 1-10).

— Select Update list item to update the event list manually (Procedure 1-11).

— Select Auto-Update from the menu. Turn it ON, OFF or make changes to the feature (Procedure 1-12).

— Select filter item from the Event List and select the events you need in the event list (Procedure 1-13).

— Display a detail summary of an event and select the print details to print details (Procedure 1-14).

— Open the Alarm Monitor tool and select Details new and active alarms (Procedure 1-15, Procedure 1-16).

— Select the Display Option item and modify it to define a user view of the network (Procedure 1-17).

— Defining a filter (Procedure 1-18).

— Select the Show All in the Option menu and change the contents of the list of alarms (Procedure 1-19).

— Sorting the list of alarms (Procedure 1-20).

— Select Update list item from the Alarm Monitor tool to update the list of alarms (Procedure 1-21).

— Printing alarm details (Procedure 1-22).

—continued—

About this document xi


• Displaying alarms at the network element

— Select the alarm menu from the main menu by entering alm (Procedure 1-23).

— Use the menu to display active alarms according to severity (Procedure 1-24).

— Use the menu to display active alarms according to class (Procedure 1-25).

— Use the menu to display active alarms according to details (Procedure 1-26.)

— Use the menu to display active alarms according to history (Procedure 1-27.)

• Provisioning OPC alarms

— Display alarms status and severity by opening the OPC Alarm Provisioning tool (Procedure 1-28).

— Enable or disable the alarms from the OPC Alarm Provisioning tool (Procedure 1-29).

— Select Manual Clear command to clear OPC alarms (Procedure 1-30).

— Select the SetNE and enter the NE number for the primary or backup OPC to provision the NE to raise the pointer alarm (Procedure 1-31).

— Enable or disable the OPC pointer alarm by choosing the change status from the List item menu (Procedure 1-32).

— Change the severity of the OPC pointer alarm by choosing the Change Severity from the List item menu (Procedure 1-33).

• Alarm definitions

— Read chapter 2 for definition of the alarms and alerts.

— Use Trouble Clearing and Module Replacement 323-1801-543 for troubleshooting on each alarm or alert.

xii About this document


High level procedure introductionThis document contains high level procedure introductions that provide information necessary for a qualified user to perform a procedure. You can find an overview of the requirements, the main procedure tasks, and the expected results on a single page. The step numbers in parentheses provide hypertext links to specific procedure steps in the complete procedure.

Some detailed procedures can include warning, caution, or danger messages included between detailed steps. You can find precautionary message icons included next to specific steps in the following high level introduction. To read the full precautionary message in the complete procedure look for the equivalent step as indicated in parentheses after the procedure task.

Example of a high level procedure introduction

Before you start

• Log on to the network element user interface.

Procedure tasks

• Access the main menu of the NEUI with admin or read/write privileges (step 1).

• Put the associated facility OOS if you are taking a CPG OOS (step 4).

• Put the corresponding output facility OOS if you are taking the protection ESI CPG OOS (step 10).

• Put the protection ESI CPG OOS (step 14).

• Put the output facility for the working ESI CPG OOS (step 18).

• Set the target filter mode to freerun if you are taking the working ESI CPG OOS (step 20).

Expected results

• The primary state of the CPG is changed.

• If the expected results do not occur:

— Perform the procedure again.

— Contact your next level of support.


1-1

Alarm and trouble clearing guidelines 1-This chapter describes the process used to clear alarms and other trouble conditions. For a description of the different indicators and support tools used to aid in troubleshooting, see Fault Detection, 323-1801-541.

Trouble conditions are visible through the following:

• light-emitting diodes (LEDs) on a circuit pack

• lamps and alarms on bays

• alarm indications by the operations controller (OPC)

• the network element user interface (NE UI)

Each procedure for an alarm provides instructions on how to clear trouble conditions. See Trouble Clearing and Module Replacement, 323-1801-543 for trouble clearing and equipment replacement procedures.

Note: For amplifier related alarms or alerts, refer to the NTP, 1600G Amplifier Alarm Clearing and Module Replacement, 323-1801-546. For alarms relating to the MOR Plus fiber-optic link, refer to the NTP, MOR Plus Alarm Clearing and Module Replacement, 323-1801-545

Alarm ReportingAlarm reporting is the monitoring of the OPTera Long Haul 1600 network element equipment, OPC, facilities, and software, for alarm (fault) and event (alert) conditions. Alarm reporting covers the generation of alarm and event reports for those conditions.

When an alarm condition occurs, the system sends an alarm report to the user interface. The following conditions can raise an alarm:

• One of the source faults is set and all of the masking faults are clear.

• The source equipment or facility is in-service and the hold-off period is over before the generation of an alarm.

• An active alarm status is alarmed and reported.

An alarm clears under the following conditions:

• All of the source faults clear or one of the masking faults occurs.

1-2 Alarm and trouble clearing guidelines


• The source equipment or facility is out of service, or the hold-off period before the generation of an alarm is over.

• You deprovision an active alarm.

Clearing alarmsThe OPTera Long Haul 1600 network element generates alarms when a fault occurs at known alarm points. To clear these alarms, use the alarm-clearing procedures provided in Trouble Clearing and Module Replacement, 323-1801-543 for the Repeater and Combiner network elements. For the 1600G Amplifier network element, use the alarm-clearing procedures provided in 1600G Amplifier Alarm Clearing and Module Replacement, 323-1801-546.

Identifying the alarmUse the NE UI and surveillance from the OPC to clear alarms. A single OPC can manage several OPTera Long Haul 1600 network elements. The network elements managed by the OPC are in the OPC span of control. The OPC groups the active alarms for a number of OPTera Long Haul 1600 network elements.

The OPC has a number of tools available to view alarm summaries or details. For a short introduction, see Fault Detection, 323-1801-541, or “The OPC surveillance environment” on page 1-7 of this document. Procedures that outline the functionality of the OPC tools start on page 1-14. Use Procedure 1-1, “Displaying the OPC status” for instructions on how to view the OPC system identification and status information.

The Alarm Monitor tool allows you to analyze all the active alarms within the OPC span of control. This tool provides access to the details of active alarms.

Note: An asterisk (*) in the Time column of this tool indicates the alarm occurred at least one day prior to the current date of the OPC.

The NE UI allows you to perform analysis and alarm monitoring functions.

Note: The user interface main menu for the Repeater, Combiner and 1600G Amplifier are slightly different from each other, as not all network elements offer the same functionality. For alarm monitoring however, only the menu item ‘ALarMs’ will be used. Sub-menu options from within this menu item are identical for all network elements.

Refer to Fault Detection, 323-1801-541 for more information on the NE UI.

Preside Network Management system monitors a number of OPCs and provides an additional level of alarm integration. Refer to Preside Application Management User Guide, 450-3101-221.

Alarm and trouble clearing guidelines 1-3


You can start correcting remote faults from the surveillance center if there is remote user interface access to the network element. In some events (such as to replace a failed circuit pack), you need to send a technician to the site. Other alarm indications, such as LEDs, lamps, and audible alarms, indicate the problem. A complete trouble-clearing analysis is based on alarms generated by the network element and maintenance and provisioning activities on the system.

Both the OPC and NE UI display the alarms by class, type, and label. There are three classes of alarms:

• equipment

• facility

• environmental

The equipment and facility classes are grouped according to the equipment or facility the alarm occurs on. The alarm label describes the problem.

When an exceeded threshold occurs, an alarm or alert generates. The provisioning of the threshold crossing report type determines which alarm or alert generates. See Performance Monitoring Procedures, 323-1801-520.

Using the alarm-clearing proceduresThe NTP, Trouble Clearing and Module Replacement, 323-1801-543, contains alarm-clearing and equipment replacement procedures.Alarms appear in alphabetical order by:

• class of alarm

• type of alarm

• label of the alarm (as identified in the alarm information displayed by the NE UI)

• circuit pack or facility type

Procedure formatEach alarm clearing procedure includes three standard sections. The sections are “Probable cause”, “Impact”, and “Action”.

The “Probable cause” section lists all expected causes of the alarm. This section also indicates how the network element software handles the alarm (alarm raised immediately or after a hold-off period). This section indicates the masking relationship of the alarm with other alarms.

The “Impact” section indicates the severity of the alarm under protected and not protected conditions. This section also indicates if the alarm is service affecting or not.



The “Action” section details the steps required, if any, to clear the alarm. Perform the steps in the order indicated. If possible, the most common solutions appear first. Non-service-affecting actions appear before any service affecting actions. If appropriate, there is a reference to other alarm clearing procedures.

Replacing circuit packs and other equipmentClearing certain alarms often requires the replacement of a circuit pack or other equipment. Follow the equipment replacement procedures in Trouble Clearing and Module Replacement, 323-1801-543. The module replacement procedures define the steps to take to protect traffic during the replacement procedures. After the replacement of a circuit pack, system diagnostics automatically re-evaluates the alarm status related to the circuit pack. If the circuit pack was responsible for a fault, the alarm clears. Make sure that the replacement circuit pack is operating correctly. The circuit pack must meet the baseline requirements for the current software release of the network element.

Completing the procedureThe alarm-clearing procedures provide actions for correcting all expected failure conditions. If the alarm clears after performing some of the actions in the procedure, there is no need to perform the remaining steps. The alarm-clearing procedure is complete when the alarm clears (exceptions occur in the event of false or repeated failures).

Perform a network element database backup, to make sure that the OPC has the latest shelf provisioning information.

Use the OPC Network Browser tool to view network status information including alarm, and performance data about all the network elements and the OPC. Procedures 1-2 to 1-4 show how to gather information about a distinct shelf or network element.

The OPC Event Browser tool allows the user to search the record of OPC log reports and OPC network element alarms and alerts. Refer to Procedures 1-9 to 1-14 in this chapter for event information.

Clearing multiple-alarm conditionsThe alarms generated by the OPTera Long Haul 1600 network element try to locate the source of the problem. Masking relationships exist between alarms on the same network element. Refer to the appropriate alarm-clearing procedure then follow the related procedure. The procedures identify alarms and the cause of the fault condition when possible.

Surveillance personnel often use the OPC or the Preside Network Management system to monitor the network. See Alarm Monitor Procedures 1-15 to 1-22 in this chapter. A number of alarms can refer to a common problem or to multiple problems in the network. Surveillance personnel must analyze the list of active



alarms to identify the source of a fault. The OPC Network Summary tool monitors any changes in alarms (see Procedures 1-5 to 1-8 in this chapter). Use the Network Summary tool to identify that an alarm exists.

When multiple alarms are present on a network element or in the network, clear the service affecting alarms with the highest severity first. For example, a “critical” alarm indicates traffic loss, while a “major” alarm for the same problem indicates that traffic is protected. The highest severity alarms can indicate the root cause of the problem. Secondary faults often become visible only after the correction of more severe problems. See Procedures 1-23 to 1-27 in this chapter to learn how to display active alarms on the NE UI.

Group alarmsA single group alarm is raised against a facility to indicate an alarm condition on one or more of the paths. The group alarm includes a large number of possible path alarms raised against an OPTera Long Haul 1600 network element.

Event alerts Event indications are events that normally do not require any direct maintenance action. The system sends event reports (alerts) as logs to the NE UI when an event condition occurs.

OPC AlarmsOPC alarms are different from alarms raised on the OPC circuit pack. OPC alarms refer to the tools and functions of the OPC, such as a network intrusion attempt on the OPC.

OPC alarms appear in the following tools, applications and interfaces:

• Alarm Monitor tool

• Event Browser tool

• Network Summary tool

• OPC Browser tool

• Preside Network Management application

• TL1 (Transaction Language 1) interface

• OSI (Open Systems Interconnect) interface

You can provision OPC alarms from the OPC Alarm Provisioning tool. See Procedures 1-28 to 1-33 for more information.



Supporting tools and indicatorsThe OPTera Long Haul 1600 network element allows efficient troubleshooting, both on-site and from remote locations. The following list provides additional troubleshooting aids:

• the OPC

• the NE UI

• logs

• performance monitoring

• LEDs

See Fault Detection, 323-1801-541 for more information.

Historical alarmsView historical alarms on the NE UI in a list format. The information in the list includes:

• AlmRpt: the alarm report number

• Unit: the alarmed unit

• Address: the name and address of the alarmed unit

• Shelf: the shelf housing the alarmed circuit pack

• Location: the frame number

• ShPos: the position of the shelf

• Reason: the type of alarm



The OPC surveillance environment To keep track of the status of the network, use the OPC tools listed under the Network Surveillance toolset in the User Session Manager window, as shown in the following graphic:

OTP0377.eps

The Network Surveillance toolset includes the following tools:

• Alarm Monitor—this tool allows you to view the alarm counts for all network elements in the OPC scope.

• Network Summary—this tool allows you to look for changes in alarms.

• Event Browser—this tool allows you to search the record of OPC log reports and network element alarms and alerts.

• Network Browser—this tool allows you to view network status information including alarm, and performance data about all the network elements.

Monitoring alarm status by the OPCThe Alarm Monitor tool provides the most detailed alarm status information. A summary appears at the bottom of the main window of all open tools, and at the bottom of the user session manager, as follows:

C0 M0 m1 w2 FailProt - Lckt 1 ActProt 1 PrfAlrt - 16:55

FW-20358

> User Session Manager : netsurv.

Available tools Open tools

ID234

State>.OK>.OK>.OK

ToolOPC Status:Primary/ActiveAlarm MonitorNE Login Manager

[ Logout ]

C 0 M 0 m 1 w 2 FailProt - Lckt 0 ActProt 0 PrfAlrt - 16:33

Toolset/ToolsNetwork Surv. Alarm Monitor Network Summary Event Browser Network BrowserUtilities NE Login Manager Password Update



The summary indicates the number of critical alarms, major alarms, minor alarms, and warning alarms, and the active protection switches and performance alerts. Any count that is greater than 999 appears in the status line as 999. The 999 code means the actual count is 999 or greater. Many of the tools have a banner line. Make sure you are looking at the correct banner line.

Refer to Table 1-1 for descriptions of the symbols that appear on the status line.

Table 1-1Descriptions of symbols from the OPC status line

Symbol Description

C The “C” symbol identifies the total number of Critical alarms. Critical alarms, are the most severe type of alarm and are normally service affecting. You must fix a critical alarm immediately.

M The “M” symbol identifies the total number of Major alarms. Major alarms are less severe than critical alarms but can be service affecting. Major alarms indicate problems that require an immediate response.

m The “m” symbol identifies the total number of minor alarms. Minor alarms are non-service-affecting and indicate protected circuit pack failures, common equipment failures, or performance monitoring threshold crossings.

w The “w” symbol identifies the total number of warnings. Warnings are conditions that are not as severe as those indicated by minor alarms. Check the cause of the warning alarm.

FailProt The ‘failProt’ symbol indicates the number of protection switch failures that are present on the OPC span of control

Note: This feature is not applicable to the OPTera Long Haul 1600 product line.

Lckt The “Lckt” symbol identifies the total number of lockouts performed. You can perform lockouts on separate channels in a network element. Neither a user or the system can switch traffic to or from a locked-out channel.

ActProt The “ActProt” symbol identifies the total number of active protection switches. A protection switch is active when the traffic on a working channel moves to a protection channel. The switch can be a manual switch or an automatic switch.

Note: This feature is not applicable to the OPTera Long Haul 1600 product line.

PrfAlrt The 'PrfAlrt' symbol identifies the number of performance monitoring alerts, or threshold crossing alerts that are present on the OPC span of control.



The summary count on the status line appears in reverse video when a new alarm appears. To remove the highlighting on the status line of the Network Summary tool and the Alarm Monitor tool, press Ctrl_X F.

In the event of a loss of communication with one of the network elements in the OPC span of control, a question mark (?) appears at the left of the alarm status line. Other problems can make the question mark appear.

Procedure listTable 1-2 lists the alarm procedures found in this chapter.

Table 1-2Alarms procedure list

Action Details

Displaying the OPC status Procedure 1-1

Browsing the network

Checking the network Procedure 1-2

Displaying detailed information about a shelf Procedure 1-3

Sorting the network element list Procedure 1-4

Monitoring network alarm status

Customizing the network element alarm count list Procedure 1-5

Identifying a change in network status Procedure 1-6

Resetting the new and cleared alarm counts for selected network elements in the span of control

Procedure 1-7

Resetting the new and cleared alarm counts for all network elements in the span of control

Procedure 1-8

Viewing logs, alarms, and alerts at the OPC

Displaying a detailed event report Procedure 1-9

Sorting the Events List Procedure 1-10

Updating the Events List manually Procedure 1-11

Enabling, disabling, or changing the auto-update feature for the Events List

Procedure 1-12

Filtering the Events List Procedure 1-13

Printing event details Procedure 1-14

Displaying the alarm details for a new alarm Procedure 1-15

—continued—



Displaying an active alarm Procedure 1-16

Defining the user view and display options Procedure 1-17

Defining a filter Procedure 1-18

Changing the contents of the list of alarms Procedure 1-19

Sorting the list of alarms Procedure 1-20

Updating the list of alarms Procedure 1-21

Printing alarm details Procedure 1-22

Displaying alarms at the network element

Displaying active alarms Procedure 1-23

Displaying active alarms according to severity Procedure 1-24

Displaying active alarms according to class Procedure 1-25

Displaying alarm details Procedure 1-26

Displaying historical alarms Procedure 1-27

Provisioning OPC alarms

Displaying OPC alarms and the OPC pointer alarm status and severity

Procedure 1-28

Enabling and disabling OPC alarms Procedure 1-29

Clearing OPC alarms Procedure 1-30

Provisioning the network element to raise the pointer alarm Procedure 1-31

Enabling and disabling the OPC pointer alarm Procedure 1-32

Changing the severity of the OPC pointer alarm Procedure 1-33

Table 1-2 (continued)Alarms procedure list

Action Details



Procedure 1-1Displaying the OPC status

Use the following procedure to view the operations controller (OPC) system identification and status information.

—continued—

Before you start

• Make sure you have a UserID and password that allow you to access the OPC.

• When you install software, commission network elements, or perform a database backup and restore operation, determine which OPC you are on.

• Understand how to use the OPC menus, see OPC User Interface Description, 323-1801-196.

Procedure tasks

• Log into the OPC (step 1).

• Select the OPC Status item (step 3).

• Return to the User Session Manager window (step 4).

Expected results

• The OPC status appears.


— Check that the OPC is on and is working.




Procedure 1-1 (continued)Displaying the OPC status

Action

Step Action

1 Log in to the OPC.

See the procedures in OPC User Interface Description, 323-1801-196, if you do not know how to log in to the OPC.

The User Session Manager appears. The OPC Status tool is at the top of the Open tools list.

OTP0377.eps

2 Tab to the Open tools list.

—continued—

FW-20358

> User Session Manager : netsurv.

Available tools Open tools

ID234

State>.OK>.OK>.OK

ToolOPC Status:Primary/ActiveAlarm MonitorNE Login Manager

[ Logout ]

C 0 M 0 m 1 w 2 FailProt - Lckt 0 ActProt 0 PrfAlrt - 16:33

Toolset/ToolsNetwork Surv. Alarm Monitor Network Summary Event Browser Network BrowserUtilities NE Login Manager Password Update



Procedure 1-1 (continued)Displaying the OPC status

Step Action

3 Use the arrow keys to move to the OPC Status entry in the list and press Ctrl_A (or Keypad 0) to select it.

The OPC Status window appears. OTP1096.eps

4 After you view the contents of the OPC Status window, press Ctrl_T 0 to return to the User Session Manager.

The User Session Manager appears. The OPC Status tool remains at the top of the Open tools list.

—end—

? C0 M0 m1 w2 FailProt - Lckt 0 ActProt 0 PrfAlrt - 11:38

>¥ OPC Status

OPC2139PPrimaryActive2139OPTera LH Rel 03.00Inactive

OPC Name:OPC Function:

OPC Status:Network Element:

SW Version:Backup OPC Status:



Procedure 1-2Checking the network

Use this procedure to check the status of the network using the Network Browser tool. The Network Element list provides a summary of all active alarms, protection-switch counts, and performance alerts for each network element in the OPC span of control. The Network Browser tool also displays OPC alarm counts.

—continued—

Before you start



Procedure tasks

• Open the Network Browser tool (step 1).

• Check the status of all network elements in the OPC span of control (step 4).

Expected results

• The status of all network elements in the OPC span of control appears.






Procedure 1-2 (continued)Checking the network

Action

Step Action



2 Within Network Surveillance tools, use the up/down arrow keys to position the cursor at the Network Browser option.

3 Press Ctrl_A (or Keypad 0) to open the Network Browser.

The Network Browser main window appears.OTP1093.eps

—continued—

FW 21125 (OPC20)

>• Network BrowserNetwork: CO13 System: CO13 Network Element Fac Eqp Env FailProt Lockout ActProt PrfAlrt O OPC2112P . 1m . - - - - 2112 3C+ 24m . - . - - 2113 2C+ 6m . - . - -

? C 5 M 1 m 93 w 5 FailProt - Lckt 0 ActProt 12 PrfAlrt - 16:00



Procedure 1-2 (continued)Checking the network

Step Action

4 Check the status of the OPC and of all network elements in the OPC span of control in the Network Element list.

The following table lists the symbols and their meanings found in the Network Element list:

Note: You can sort the list either by alarm severity or network element ID. See Procedure 1-4, Sorting the network element list, in this document.

5 To close the tool:

a. Press Ctrl_L W (or Keypad 6) to display the window menu.

The window menu appears.

b. Press the Space bar (or Keypad 0) to select Exit.

Both the main window and the tool close.

—end—

? the alarm counts can be wrong

C critical alarm

M major alarm

m minor alarm

w warning alarm

+ there are one or more additional alarms of lower severity, or alerts for facilities of lower bandwidth

- not available

. zero alarms or alerts



Procedure 1-3Displaying detailed information about a shelf

Use this procedure to locate more information about the shelf. This procedure allows you to:

• determine the type of service provided by the shelf

• display the shelf serial number

• display the booting and backup parameters

—continued—

Before you start



Procedure tasks


• Select the network element (step 4).

• Display the List item menu (step 5).

• Select the Shelf details item (step 6).

Expected results

• Detailed information about a shelf appears.






Procedure 1-3 (continued)Displaying detailed information about a shelf

Action

Step Action






Note: You can sort the list either by alarm severity or network element ID. See Procedure 1-4, “Sorting the network element list”, in this document.

4 Move to a network element that you need detailed information about and press Ctrl_A (or Keypad 0) to select it.

The selected item appears in reverse video.

If there are additional network elements that you need detailed information about, move to that network element and press Ctrl_Y (or Keypad .).

The selected network elements appear in reverse video.

Note: Do not select the line that displays the OPC alarm counts.

—continued—

FW-21125 (OPC20)






Step Action

5 Press Ctrl_L (or Keypad Enter) to display the List item menu.

The List item menu appears. OTP1092.eps

6 Use the arrow keys to move to the Shelf details command and press the Space bar (or Keypad 0) to select it.

The Shelf Details dialog appears.

Note 1: The Shelf details command becomes disabled when you select the OPC alarm counts line.

Note 2: If you select two or more network elements, press Ctrl_A (or Keypad 0) to display the Shelf Details dialog for each selected item.

OTP1097.eps

—continued—

>• Network BrowserNetwork: CO13 System: CO13

Network Element Fac Eqp Env FailProt Lockout ActProt PrfAlrt O OPC2112P . 1m . - - - - 2112 . . . - . . - 2113 2C+ 6m . - . 1OC192+ -


1 Shelf details D

2 Select3 Deselect

4 Help

>>>>

H

Shelf Details

Network Element: 2113

Type: OPTera LH Function: AMPLIFIER Booting Parameters Backup Parameters Profile: None File: Priority: 1 Limit: 2

[ Done Return ]




Step Action

7 Press Ctrl_A (or Keypad 0) to select the Done button to close the Shelf Details dialog.

The dialog closes.






—end—



Procedure 1-4 Sorting the network element list

Use this procedure to list network elements according to the severity of their alarms or according to their ID numbers.

—continued—

Before you start



Procedure tasks



• Select the Sort item (step 6).

• Select one of the sorting options (step 7).

Expected results

• The sorted detailed information about a shelf appears.






Procedure 1-4 (continued)Sorting the network element list

Action

Step Action






—continued—

FW 21125 (OPC20)






Step Action

4 Press Ctrl_L G (or Keypad 2) to display the list menu.

The List item menu and a submenu appear.OTP1095.eps

5 Use the Arrow keys to select the List command.

The List options appear. OTP1094.eps

—continued—




1 List item >>2 List3 background4 window

1 Shelf details •D

2 Select >>3 Deselect >>

4 Help •H




1 List item >>2 List3 backg4 wind

1 Sort >>

Help Hby alarm severityby network element

12




Step Action

6 Use the arrow keys to move to the Sort command, and press the right Arrow key to move to the submenu.

The first item in the submenu appears in reverse video.

7 Use the arrow keys to move to the option you need and press the Space bar (or Keypad 0) to select it.

The list sorts according to the option you select.






—end—

If you need to display network elements Then select

by alarm severity(critical alarms, major alarms, minor alarms)

by alarm severity

by ID numbers by network element



Procedure 1-5Customizing the network element alarm count list

Use this procedure to customize the network element alarm count list. When you first open the alarm count list, only the active alarms for each network element and each OPC shown appears. You can customize the list to also show new alarms, cleared alarms, or both.

—continued—

Before you start



Procedure tasks

• Open the Network Summary tool (step 1).

• Select the New since reset item to display new alarm counts (step 5).

• Select the Cleared since reset item to display cleared alarm counts (step 6).

Expected results

• The new or cleared alarm count list appears for the network element.






Procedure 1-5 (continued)Customizing the network element alarm count list

Action

Step Action



2 Within Network Surveillance tools, use the up/down arrow keys to position the cursor at the Network Summary option.

3 Press Ctrl_A (or Keypad 0) to open the Network Summary.

The Network Summary main window appears. F21554-192_R60

4 Select your next step:

5 To display new alarm counts, tab to the New since reset check box, and press Ctrl_A (or Keypad 0) to select it.

The new alarms occurring after the last reset time appear for all network elements and OPCs in the list.

—continued—

If you need to display Then

new alarm counts go to step 5

cleared alarm counts go to step 6

> Network Summary .Critical

.

C 0 M 0 m 9 w 0 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 15:58

Major.

minor9

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-Network View

Showing alarms: active and [ ] New since reset [ ] Cleared since reset

Network Element 0 OPC92115P + 9215+ 9216+ 9906

Reset14:4614:4614:4614:46

ActActActAct

Crit....

Major....

minor.54.

warn....

Fail----

Lock-...

ActP-...

Prf----

FW-21554 (OPC20)



Procedure 1-5 (continued)Customizing the network element alarm count list

Step Action

6 To display cleared alarm counts, tab to the New since reset check box. Press the right arrow key to move to the Cleared since reset check box, and press Ctrl_A (or Keypad 0) to select it.

The alarms cleared after the last reset time appear for all network elements and OPCs in the list.

F21551-192_R60






—end—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.


Showing alarms: active and [*] New since reset [*] Cleared since reset

Network Element 0 OPC92115P

+2 Montreal_108+ 9215215+++3 MONTPQ01D33+ 9216

+ 9906

Reset14:46

14:46

14:46

14:46

ActNewClrActNewClrActNewClrActNewClr

Crit............

Major............

minor............

warn............

Fail............

Lock...11.......

ActP......1.1...

Prf............

FW-21552 (OPC20)



Procedure 1-6Identifying a change in network status

Use this procedure to identify a change in network status. The Network View banner displays status information counts for all network elements in the OPC span of control. The Network Summary tool also displays the OPC alarm counts. A changed count is visible in two ways: the number increases or decreases, and the field appears in reverse video.

—continued—

Before you start



Procedure tasks


• Note any changes in the Network View banner (step 4).

• Locate the status icon which indicates a change in the counts for a network element or OPC (step 5).

• Display the new and cleared alarms on all network elements or OPCs in the list (step 6).

Expected results

• The network status of a shelf appears.






Procedure 1-6 (continued)Identifying a change in network status

Action

Step Action






4 Note any changes in the Network View banner.

The changed alarms appears in reverse video.

5 In the Alarm Count list, look for the status icon (+). The status icon indicates a change in the counts for that network element or OPC.

Locate the network element or OPC that has a new alarm or has a new cleared alarm.

6 Display the new and cleared alarms on all network elements and OPCs in the list.

See Procedure 1-5, “Customizing the network element alarm count list”, in this document.

The new and cleared alarms for each network element or OPC appear.

—continued—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.




Reset14:4614:4614:4614:46

ActActActAct

Crit....

Major....

minor.54.

warn....

Fail----

Lock-...

ActP-...

Prf----

FW-21554 (OPC20)




Step Action

7 Log in to the network element with the alarm and follow the instructions to clear this alarm. Refer to the appropriate NTP as listed below:

• Repeater, Combiner, Control Shelf related alarms

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

• MOR Plus related alarms

— Optical Alarm Clearing and Module Replacement, 323-1801-545.

• 1600G Amplifier related alarms

— 1600G Amplifier Alarm Clearing and Module Replacement, 323-1801-546

8 To reset the display of new alarms for all network elements, press Ctrl_X F.

All highlighting and plus (+) signs reset.

9 To reset the display of new alarms for selected network elements or OPCs:

a. Tab to the list of alarms.

The cursor appears in the list.

b. Use the arrow keys to move to the network element or OPC that raised the alarm and press Ctrl_Y (or Keypad .) to select the item.

c. Press Ctrl_L (or Keypad Enter) to display the List item menu.

The List item menu appears. F21552-192_R60

—continued—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.





+ 9906

Reset14:46

14:46

14:46

14:46


Crit............

Major............

minor............

warn............

Fail............

Lock...11.......

ActP......1.1...

Prf............

1

23

4

Reset Counts

SelectDeselect

Help

>>>>

H




Step Action

d. Use the arrow keys to move to the Reset Counts command and press the Space bar (or Keypad 0).

The reset time changes to the current time and the new alarm count and cleared alarm count reset to zero. A dot indicates a zero count.






—end—



Procedure 1-7Resetting the new and cleared alarm counts for selected network elements in the span of control

Use this procedure to set new and cleared alarm counts to zero for selected network elements and OPCs. Only the alarms received after the Reset time appear in the new alarm and cleared alarm fields.

—continued—

Before you start



Procedure tasks


• Display the new and cleared alarms on all network elements and OPCs in the list (step 5).

• Select each network element or OPC for which you need the count reset (step 6).


• Select the Reset Counts item (step 8).

Expected results

• The new and cleared alarm counts reset to zero for the selected network elements or OPC.






Procedure 1-7 (continued)Resetting the new and cleared alarm counts for selected network elements in the span of control

Action

Step Action






4 Tab to the list of alarms.


5 Display the new and cleared alarms on all network elements in the list.

See Procedure 1-5, “Customizing the network element alarm count list”, in this chapter if you need more information about this step.

The new and cleared alarms for each network element appear.

6 Move to each network element or OPC that you need the count reset. Press Ctrl_Y (or Keypad .) to select the network element or OPC.

The selected items appear in reverse video.

—continued—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.




Reset14:4614:4614:4614:46

ActActActAct

Crit....

Major....

minor.54.

warn....

Fail----

Lock-...

ActP-...

Prf----

FW-21554 (OPC20)



Procedure 1-7 (continued)Resetting the new and cleared alarm counts for selected network elements in the span of control

Step Action


The List item menu appears. F21552-192_R60

8 Use the arrow keys to move to the Reset Counts command, and press the Space bar (or Keypad 0) to select it.







—end—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.





+ 9906

Reset14:46

14:46

14:46

14:46


Crit............

Major............

minor............

warn............

Fail............

Lock...11.......

ActP......1.1...

Prf............

1

23

4

Reset Counts

SelectDeselect

Help

>>>>

H

FW-21552 (OPC20)



Procedure 1-8 Resetting the new and cleared alarm counts for all network elements in the span of control

Use this procedure reset the new and cleared alarm counts to zero for all network elements or OPCs in the Network Summary list. Only the alarms received after the Reset time appear in the new alarm and cleared alarm fields.

—continued—

Before you start



Procedure tasks


• Display the new and cleared alarms on all network elements or OPCs in the list (step 4).


• Select the Reset all counts item (step 7).

Expected results

• The new and cleared alarm counts reset to zero for all the network elements in the span of control.






Procedure 1-8 (continued)Resetting the new and cleared alarm counts for all network elements in the span of control

Action

Step Action

1 Log in to the OPC and open the Network Summary tool.





4 Display the new and cleared alarms on all network elements and OPCs in the list.

See Procedure 1-5, “Customizing the network element alarm count list”,in this chapter if you need more information about this step.

The new and cleared alarms for each network element and OPC appear.



—continued—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.




Reset14:4614:4614:4614:46

ActActActAct

Crit....

Major....

minor.54.

warn....

Fail----

Lock-...

ActP-...

Prf----

FW-21554 (OPC20)



Procedure 1-8 (continued)Resetting the new and cleared alarm counts for all network elements in the span of control

Step Action

6 Press Ctrl_L / (or Keypad 3) to display the list menu. F21553-192_R60

7 Use the arrow keys to move to the Reset all counts command and press the Space bar (or Keypad 0) to select it.







—end—


.


Major.

minor9

warning.

FailProt-

Lockout.

ActProt.




+2 Montreal_108+ 9215 14:46 Act

+ 9216

+ 9906

Reset14:46

14:46

14:46

14:46

ActNewClr

NewewClrlrlrClrActNewClrActNewClr

Crit......

.

.

.

.

.

Major............

minor......5.4...

warn............

Fail...---------

Lock............

ActP............

Prf------------

FW-21552 (OPC20)

1 Reset All Counts

2 Help

Ctrl+X F

H



Procedure 1-9Displaying a detailed event report

Use this procedure to display more information about an event that appears in the summary in the Events List.

—continued—

Before you start



Procedure tasks

• Open the Event Browser tool (step 1).

• Select one or more events from the list (step 4).


• Select the Details item (step 4).

• Display the Events List menu to select one event by event number (step 5).

• Select the Show details item (step 5).

• Type the name or number, or both, of the network element in the network element field (step 5).

• Type the Event number of the event you need to locate in the Event number field (step 5).

Expected results

• The detailed event report appears.






Procedure 1-9 (continued)Displaying a detailed event report

Action

Step Action



2 Within Network Surveillance tools, use the up/down arrow keys to position the cursor at the Event Browser option.

3 Press Ctrl_A (or Keypad 0) to open the Event Browser.

The Event Browser main window appears. The current item in the Events List highlights.

OTP1088.eps

Note 1: When the Events List contains more events than fit on one screen, you can scroll one line at a time. Press the up (or down) arrow key. For scrolling one screen at a time, press Keypad 5 followed by an arrow key. For more information about scrolling, see OPC User Interface Description, 323-1801-196.

Note 2: You can sort the list according to different options. See Procedure 1-10, “Sorting the Events List”, in this chapter.

—continued—

> Event Browser.

Auto-update: [ OFF ] Last update at: 14 Nov 04:31:0525 Events sorted by timeShowing: OPC logs,all NE logs, alarms, alerts, all sev, and all NEs


[ Update List ]

NE # NE Name

Cls Unit Date Time SvReasonEvt#

2112 446 Fac STM64 G17 1 MS Excessive BER 28 Jan 22:51:41 C2112 434 Fac STM16 G18 1 MS Rx SES threshol 28 Jan 22:44:32 A2112 432 Fac STM16 G18 1 MS Rx SES threshol 28 Jan 22:44:31 A2112 431 Fac STM16 G18 1 MS Rx ES threshold 28 Jan 22:44:31 A2112 418 Fac STM64 G17 1 MS Rx SES threshol 28 Jan 22:36:43 A2112 416 Fac STM64 G17 1 MS Rx SES threshol 28 Jan 22:36:42 A2113 145 Fac STM16 G18 1 MS Rx SES threshol 28 Jan 22:36:30 A2113 144 Fac STM16 G18 1 MS Rx SES threshol 28 Jan 22:36:29 A0 OPC2112P 1623 Cmpl log STBY612 Incrementa 28 Jan 20:01:36 w0 OPC2112P 1622 Prog log STBY702 Incrementa 28 Jan 20:00:02 w0 OPC2112P 1619 Cmpl log STBY612 Incrementa 28 Jan 14:01:08 w




Step Action

4 If you need to select one or more events from the list:

a. Use the arrow keys to move to the events you need detailed information about and press Ctrl_Y (or Keypad .) to select each event (maximum of five).


b. Press Ctrl_L (or Keypad Enter) to display the List item menu.


c. Use the arrow keys to move to the Details command and press the Space bar (or Keypad 0) to select it.

Alarm Details dialog(s) for the selected events appear. OTP0440.eps

—continued—

> Event Browser.

Auto-update: [ OFF ] Last update at: 14 Nov 04:31:0525 Events sorted by timeShowing: OPC logs, all NE logs, alarms, alerts, all sev, and all NEs


[ Update List ]

NE # NE Name



Details... D

Select >>Deselect >> Print Details

Help H

1

23

4

5

Alarm Details:

Alm# 446 Sev: CriticalUnit: STM64 G17 1 Imp: SA

Address: 2112 Shelf 3 Time: 22:51:41Location: ? Date: 28 Jan 2000

Reason: MS Excessive BER Cls: Facility FacilityID:

[ Done Return ] [ Print Details ]




Step Action

For information about how to respond to an event report, see Trouble Clearing and Module Replacement, 323-1801-543, and Log Reference, 323-1801-840.

Note: If you selected two or more events, press Ctrl_A (or Keypad 0) to display the Event Details dialog for each selected item.

5 If you need to select one event by the event number:

a. Press Ctrl_L / (or Keypad 3) to display the Events List menu.

The list menu appears.

b. Use the arrow keys to move to the Show details command and press the Space bar (or Keypad 0) to select it.

The Show Details dialog appears. F21020-192_R60

c. Tab to the network element field and type the name or number, or both, of the network element or OPC.

d. Tab to the Event # field and enter the number of the event you need to locate.

e. Tab to the OK button and press Ctrl_A (or Keypad 0) to select it.

The Show Details dialog closes. If the OPC finds the event, the event appears highlighted in the Events List and its Details dialog appears.

6 Use the arrow keys to move to the Done button and press Ctrl_A (or Keypad 0) to select it.

The dialog closes.






—end—

FW-21020

Show details

Network Element: > < Event #: > [ OK Return ] [ Cancel Del ]



Procedure 1-10Sorting the Events List

Use this procedure to sort the Events List by time, network element, reason, unit, class or severity. The current sort order appears above the list.

—continued—

Before you start



Procedure tasks


• Display the Events List menu (step 4).


• Select the sort order you need (step 6).

• If you need to replace the current sort order with the default sort order, select the Revert to last saved item (step 8).

• If you need to save the sort order as the default sort order, select the Save item (step 9).

• If you need to remove the dialog and not save the data, select the Cancel item (step 10).

• If you need to save the sort order as a temporary sort order for the current session, selectthe OK item (step 11).

Expected results

• The sorted Events List appears.






Procedure 1-10 (continued)Sorting the Events List

Action

Step Action





The Event Browser main window appears. OTP1088.eps

Note: When the Events List contains more events than fit on one screen, you can scroll one line at a time. Press the up (or down) arrow key. For scrolling one screen at a time, press Keypad 5 followed by the up (or down) arrow key. For more information about scrolling, see OPC User Interface Description, 323-1801-196.

—continued—

> Event Browser.



[ Update List ]

NE # NE Name






Step Action

4 Tab to the Events List and press Ctrl_L / (or Keypad 3) to display the Events List menu.

The Events List menu appears.OTP1089.eps

5 Use the arrow keys to move to the Sort command and press the Space bar (or Keypad 0) to select it.

The Event List Sorting dialog appears. F26470-OPC50

—continued—

> Event Browser.



[ Update List ]

NE # NE Name



1 Filter... F2 Sort... :3 Show details...4 Auto-update... W

5 Help H

Sort Item

Time:

Network Element:

Reason:

Unit:

Class:

Severity:

[Save S][OK Return]

[ Revert to last saved R][ Cancel Del]

Sort Order Specification

>1 < ( ) Ascending ( ) Descending

< ( ) Name ( ) Number (#)

<

<

<

<

Event List Sorting:




Step Action

6 Enter the sort order:

a. Tab to the sort item you require: time, network element, reason, unit, class, or severity.


b. Press Ctrl_L / (or Keypad 3) to display the priority list.

The priority list appears.

c. Select the priority (1 to 6) and press the Space bar (or Keypad 0) to select the value.

Note 1: Number 1 is the highest priority on the sort item list, and number 6 is the lowest priority on the sort item list.

Note 2: You can leave sort order fields empty.

Note 3: If you assign the same priority number to two or more items, the later selection overwrites the earlier selection.

d. For the time sort item, tab to the specification items to indicate the sort order: Ascending or Descending. Use the left or right arrow key to move to the option you need. Press Ctrl_A (or Keypad 0) to select it.

The mark next to the button appears or clears. A mark indicates the selection.

e. For the network element sort item, tab to the Specification section and select how to sort network elements (name or number). Use the left or right arrow key to move to the option you need. Press Ctrl_A (or Keypad 0) to select it.

The mark next to the button appears or clears. A mark indicates the selection.

7 The entry of the sort order data is now complete.

—continued—

If you need to Then go to

replace the current data with the default sort order step 8

save the data as the default sort order step 9

remove the dialog and not save the data step 10

save the data as temporary sort options for the current session

step 11




Step Action

8 Tab to the Revert to last saved button and press Ctrl_A (or Keypad 0) to select it.

The Event List Sorting dialog contains the default sort order. The sort order does not become active in the current session unless you select the OK button.

Go to step 11.

9 Tab to the Save button and press Ctrl_A (or Keypad 0) to select it.

The sort order defined has the default sort options for the Event Browser. The sort order does not become active in the current session unless you select the OK button.

Go to step 11.

10 Tab to the Cancel button and press Ctrl_A (or Keypad 0) to select it.

The Event List Sorting dialog closes, and the sort order does not change.

The procedure is complete.

Go to step 12.

11 Tab to the OK button and press Ctrl_A (or Keypad 0) to select it.

The list sorts according to the options you selected. The new sort order appears above the Events List.

Note 1: The Sort results reflect the filter you set up for the Events List. The sort results include only the event types you included in the filter.

Note 2: If you update the list, the new events appear in the list in their correct sort position.






—end—



Procedure 1-11Updating the Events List manually

Use this procedure to update the Events List with new events. The occurrence of a new event does not cause the Event list to update. The Events list only updates when a manual update or automatic update occurs. You must use the following procedure when you need to update the list manually.

The New Events icon (>>) next to the Update List button indicates the log of new events after the last update. If this icon is not visible, this procedure has no effect.

—continued—

Before you start



Procedure tasks


• Select the Update list item (step 4).

Expected results

• The updated Events List appears.






Procedure 1-11 (continued)Updating the Events List manually

Action

Step Action

1 Log in to the OPC and open the Event Browser tool.





Note: When the Events List contains more events than fit on one screen, you can scroll one line at a time. Press the up (or down) arrow key. For scrolling one screen at a time, press Keypad 5 followed by the up (or down) arrow key. For more information about scrolling, see OPC User Interface Description, 323-1801-196

4 Tab to the Update list button and press Ctrl_A (or Keypad 0) to select it.

The new events appear in the Events List according to the current settings in the filter. For more information about Events List filters, see Procedure 1-13 “Filtering the Events List”, in this chapter.

Note: An error message can appear when you update the Events List. This error message occurs if the OPC becomes inactive following the last use of the Update list check button

5 To close the tool press Esc ). —end—

> Event Browser.



[ Update List ]

NE # NE Name



>>



Procedure 1-12Enabling, disabling, or changing the auto-update feature for the Events List

Use this procedure to

• turn the automatic update feature ON and OFF

• set the update time period on the automatic update feature

• set the number of events to collect and add to the Events List at one time

The automatic update feature updates the Events List at a set time interval. The update period setting can be up to 24 hours greater than the minimum update interval. The minimum interval exists so that auto-updates do not occur so often that they effect OPC performance. The length of time the update takes depends on the number of new events. If you enter a value less than the minimum time interval, a message appears. The message asks you to enter a longer length of time or reduce the number of events to display.

The Update period field and the Number of events to display field are in the Event List Auto-update dialog. The Update period field has a Chooser menu. The first value in the Chooser menu is the minimum update period. The value of the minimum update period is based on the current value in the Number of events to display field. The minimum update periods are as follows:

The auto-update feature coordinates with the filter feature. When the Auto-update button is ON, the two fields below have the same value:

• Number of events field in the Events List Filter dialog

• Number of events to display field in the Events List Auto-update dialog

A change to one of these fields causes the other field to change automatically to the same value.

Auto-updates do not occur if there are no new events or if a manual update is in progress. The New Events icon (>>) next to the Update List button indicates the occurrence of new events after the last update.

You can disable the auto-update feature to view the Events List without updates.

—continued—

Number of events 0-25 26-100 101-200 201-300 301-400 401-500

Minimum update period (minutes)

5 6 7 8 9 10



Procedure 1-12 (continued)Enabling, disabling, or changing the auto-update feature for the Events List

—continued—

Before you start



Procedure tasks


• Turn the auto-update feature ON or OFF (step Note:).

• Set the number of events to collect and add to the Events List at one time (step 6).

• Set the update time period on the automatic update feature (step 7).

Expected results

• You set the auto-update feature in the Events List.







Action

Step Action






Note: When the Events List contains more events than fit on one screen, you can scroll one line at a time. Press the up (or down) arrow key. For scrolling one screen at a time, press Keypad 5 followed by the up (or down) arrow key. For more information about scrolling, see OPC User Interface Description, 323-1801-196

4 Tab to the Auto-update button and press Ctrl_A (or Keypad 0) to select it.

The button toggles between OFF (disable) and ON (enable) status. The auto-update feature is OFF by default. If the feature is OFF, selecting it turns the auto-update feature ON.

—continued—

> Event Browser.



[ Update List ]

NE # NE Name






Step Action


6 Complete step 6a to step 6f.

a. Tab to the Events List and press Ctrl_L / (or Keypad 3) to display the Events List menu.

The Events List menu appears.OTP1089.eps

b. Use the arrow keys to move to the Auto-Update command and press the Space bar (or Keypad 0) to select it.

The Event List Auto Update dialog appears.

c. Tab to the Number of events to display field and press Ctrl_L (or Keypad Enter) to display the List item menu.

A menu appears.

d. Press the Space bar (or Keypad 0) to select the Select All command.

The data in the field appears in reverse video.

e. Enter the number of events you need to display (from 1 to 500).

f. Continue with step 7c to change the update period or go to step 8.

—continued—

If Then go to

the Auto-update button is ON, and you need to change the number of events displayed when the event list automatically updates

step 6

the Auto-update button is ON, and you need to change the automatic update period

step 7

you need to change the Auto-update button to ON or OFF step 4

> Event Browser.



[ Update List ]

NE # NE Name




5 Help H




Step Action

7 The Update period field shows the existing time period between automatic updates. This period is the amount of time between the beginning of one automatic update and the beginning of the next auto-update. Complete step 7a to step 7e to set the Update period field.

a. Tab to the Events List and press Ctrl_L / (or Keypad 3) to display the Events List menu.

The Events List menu appears.

b. Use the arrow keys to move to the Auto-Update command and press the Space bar (or Keypad 0) to select it.

The Events List Auto Update dialog appears.

c. Tab to the Update Period field.

d. Press Ctrl_L / (or Keypad 3) to display the chooser menu.

The chooser menu of suggested update periods appears.

e. Use the arrow keys to move to a time period in the list. Press the Space bar (or Keypad 0) to select the time period.

Note: You can enter a time period different from the times available in the chooser list. Any number in the range from the minimum update period to 24 hours is acceptable.



The values in the fields in the Events List Auto-update dialog return to the last saved values. The Event Browser discards any information you entered.

Go to step 12.


The new values in the Number of events to display field and the Update period field become the default values for automatic updates. The new values take effect when you complete step 12. The dialog remains displayed.

Go to step 12.

—continued—


replace the current values in the Events List Auto-update dialog with the last saved information

step 9

save the information, and leave the Auto-update dialog open step 10

close the Auto-update dialog, and do not save the information

step 11

save the information, and close the Auto-update dialog step 12




Step Action


The Events List Auto-update dialog closes. The Event Browser discards any information you entered, and there is no change to the update period.

Go to step 13.


The Events List Auto-update dialog closes. The new values in the Number of events to display field and the Update period field become the default values for automatic updates. The update period appears above the Events List on the main window.

13 To close the tool press Esc ).—end—



Procedure 1-13Filtering the Events List

Use this procedure to set the filter attributes used to select the events you need to see in the Events List. You can select to display events by network element, by class of event, by severity, or by time range.

—continued—

Before you start



Procedure tasks


• Display the Events List menu (step 4).

• Select the Filter item (step 5).

• Limit the number of events displayed (step 6).

• Add or remove the selected network element from the events list (step 7).

• Add or remove the selected event types (step 8).

• Add or remove the selected event according to severity (step 9).

• Add or remove the selected alarm types (step 10).

• Add or remove the selected log class types (step 11).

• Add or remove the selected OPC log types (step 12).

• Filter on the basis of the number of occurrences for events (step 13).

• Filter events by unit identifiers (step 14).

• Display only instances of an alarm type (step 15).

• Change the year, month, date, or time to modify the time range (step 16).

Expected results

• The filtered Events List appears.






Procedure 1-13 (continued)Filtering the Events List

Action

Step Action





The Event Browser main window appears.OTP1088.eps

—continued—

> Event Browser.



[ Update List ]

NE # NE Name





Procedure 1-13 (continued) Filtering the Events List

Step Action

4 Tab to the Events List and press Ctrl_L / (or Keypad 3) to display the Events List menu.

The Events list menu appears.OTP1089.eps

5 Press the Space bar (or Keypad 0) to select the Filter command.

The Event List Filter dialog appears. OTP0531.eps

—continued—

> Event Browser.



[ Update List ]

NE # NE Name




5 Help H

Event List Filter:

Number of events: >10

Network Element 0 OPC2112P Include 2112 Include 2113 Include

Occurrences: < Unit: Reason:

Date and time, from: to: [Save ◊ S] [Revert to last saved ◊ R] [OK ◊ Return] [Cancel ◊ Del]

Severity Alarms Log Class OPC Logs[*] Critical Class: [*] Eqp [*] Trbl [*] COM[*] Major [*] Fac [*] Usage [*] SDA [*] minor [*] Env [*] State [*] STBY[*] warning [*] Sw [*] Cmpl [*] NAD[ ] Cleared [*] Prog [*] GEN

[*] Alarms [*] Alerts [*] OPC Logs

Event type:

<<

<




Step Action

6 The Number of events field allows you to limit the number of events displayed. Change the value of this field to view events not displayed. The maximum number of events to retrieve is 500.

If you need to limit the number of events displayed:

a. Tab to the Number of events field and press Ctrl_L (or Keypad Enter) to display the List item menu.

b. Press the Space bar (or Keypad 0) to select the Select All command.

The data in the field appears in reverse video.

c. Type the number of events that you need to displayed.

7 The Network Element list indicates the network element whose events appear in the Events List in the Event Browser main window. The word “Include” appears in front of Network elements which have their events displayed in the Network Element list.

If you need to modify the network element list:

a. Tab to the Network Element list.

The current list item is highlighted.

b. Use the arrow keys to move to the network element you need to add or remove. Press Ctrl_L (or Keypad Enter) to display the List item menu.

The List item menu appears. The first menu item (Add) is highlighted.

c. Select your next step:

d. Press the Space bar (or Keypad 0) to select the option.

To add the network element, select Add.

The word “Include” appears next to the network element in the Network Element list.

To remove the network element, select Removed.

The word “Exclude” appears next to the network element in the Network Element list.

—continued—

If you need to Then

add another network element to the list move to Add

remove a network element from the list move to Remove




Step Action

8 There are three Event type check buttons. These buttons allow you to determine if OPC logs, alarms, and or alerts appear in the Events List. The Alarm and Alert check buttons apply to both the OPC and network elements. When a mark appears in one of these buttons, events of that type appear in the Events List. You can select any number of event types.

If you need to modify the event types:

a. Tab to the Event type buttons.

The Alarms button is highlighted.

b. Use the arrow keys to move to the event type you need to add or remove, and press Ctrl_A (or Keypad 0) to select it.

The mark next to the button appears or clears. The appearance of a mark indicates a selection.

9 The Severity check buttons allow you to set what events appear in the Events List according to severity. When a mark appears in one of these buttons, events of that severity appear in the Events List. You can select more than one severity from this set of check buttons.

If you need to modify the event severity:

a. Tab to the Severity buttons.

The Critical button is highlighted.

b. Use the arrow keys to move to the severity you need to add or remove. Press Ctrl_A (or Keypad 0) to select it.


10 The Alarms check buttons allow you to set what class of alarms appear in the Events List. When a mark appears in one of these buttons, events of that alarm class appear in the Events List. You can select any number of alarm classes.

If you need to modify the alarm type:

a. Tab to the Alarms buttons.

The Eqp button is highlighted.

b. Use the arrow keys to move to the class of alarms you need to add or remove. Press Ctrl_A (or Keypad 0) to select it.


—continued—




Step Action

11 The Log Class check buttons allow you to determine what class of events appear in the Events List. When a mark appears in one of these buttons, events of that class appear in the Events List. You can select any number of log classes.

If you need to modify the log class type:

a. Tab to the Log Class buttons.

The Trbl button is highlighted.

b. Use the arrow keys to move to the class you need to add or remove. Press Ctrl_A (or Keypad 0) to select it.


12 The OPC Logs check buttons allow you to determine what class of OPC logs appear in the Events List. When a mark appears in one of these buttons, events of that class appear in the Events List. You can select any number of OPC log classes.

If you need to modify the OPC Logs type:

a. Tab to the OPC Logs buttons.

The COM button is highlighted.

b. Use the arrow keys to move to the class you need to add or remove. Press Ctrl_A (or Keypad 0) to select it.


13 If you need to filter on the basis of the number of occurrences for events:

a. Tab to the first input area for the Occurrences field and press Ctrl_L / (or Keypad 3) to display the list of operators.

The chooser menu appears.

b. Use the arrow keys to move to the operator you need and press the Space bar (or Keypad 0) to select it. You can select any of the following operators):

— less than (<)

— less than or equal to (<=)

— equal to (=)

— greater than or equal to (=>)

— greater than (>)

The operator appears in the field.

c. Tab to the second input area for the Occurrences field and enter a number in the range of 1 through 100.

—continued—




Step Action

14 If you need to filter events by unit identifiers:

Tab to the Unit field and enter a unit identifier or part of a unit identifier. Enter the value as it appears in the Events List. For example, enter g1 to list all alarms that effect the G1 circuit pack groups. To select on the basis of logs, enter logs.

15 To display one alarm type, tab to the Reason field. In the Reason field enter the alarm label as it appears in the Events List. The alarm label is identical to the reason text. You can enter any part of the reason text, as long as the characters are in sequence.

16 The Date and Time fields allow you to indicate a time range for events displayed in the Events List. To filter the list by date and time, set a time range.

If you need to modify the time range:

a. Tab to one of the fields.

b. To enter a different time range, use one of the following formats:

day/month/year hr:min:sec

Example: 9/11/1999 10:15:37

OR

day month year hr:min:sec

Example: 9 nov 1999 10:15:37

Note: If you do not select the year, or month, or complete date, the current year, month, or date are the default values. If you do not select the seconds, zero is the default value.

c. If you need to use a predefined time, press Ctrl_L / (or Keypad 3).

The chooser menu appears.

Use the arrow keys to move to the predefined time you need and press the Space bar (or Keypad 0) to select it.

The predefined time appears in the field.

Note: When you use a predefined time, the filtering is based on the time you saved the filter and not when you log in. For example, if the time filter is “1 day ago”, and you log in one day later, the events of the past 48 hours appear.

d. Repeat for the other Date and Time field if required.

—continued—




Step Action

17 The entry of filter data is now complete.


The Events List Filter dialog contains the default filter data. The filter does not become active in the current session unless you select the OK button.

Go to step 21.


The filter defined is the default filter for the Event Browser. The filter does not become active in the current session unless you select the OK button.

Go to step 21.


The Events List Filter dialog closes without any changes to the filtering data.

The procedure is complete.

Go to step 22.


The Events List Filter dialog closes. The filter attributes you defined for the current session, appear above the Events List in the main window.

The selected events add to the events now in the display up to a maximum of 500. After the 500 maximum, events drop from the display. Change the filter if you need to see these events.






—end—


replace the current data with the default filter step 18

save the data as the default filter step 19

remove the dialog and do not save the data step 20

save the data as a temporary filter for the current session step 21



Procedure 1-14Printing event details

Use this procedure to print event details of a single event, or up to five events.

—continued—

Before you start



• Make sure that the printer connected to the SERIAL port is working. For more information about how to connect an external device, refer to Installation Procedures, 323-1801-201.

Procedure tasks


• Print one event from the Details dialog (step 5).

• Print one to five events from the Details dialog (step 10).

Expected results

• You get a printout of one event or up to five events.






Procedure 1-14 (continued)Printing event details

Action

Step Action






4 You can select and print the details of up to five events at one time from the Events List. You can print the details of a separate event.

—continued—


print an event from the Event Details dialog step 5

print one to five events from the Events List step 10

> Event Browser.



[ Update List ]

NE # NE Name






Step Action

5 Tab to the Events List.

The current item in the Events List is highlighted.

6 Use the arrow keys to move to the event you need to print and press Ctrl_A (or Keypad 0) to select it.


The menu appears.

8 Use the arrow keys to move to the Details command and press the Space bar (or Keypad 0) to select it.

The Event Details dialog for the selected event appears.

Note: Depending on the event chosen, either the Alarm Details or the Log Details dialog window will appear as indicated below.

OTP0440.EPS

OTP0532.eps

—continued—

Alarm Details:





Log Details:

Log Number: 2448 Date: 06 Feb 2000Network element: 0 OPC2112P Imp: 00:25:42

Problem Number: 502Event type: State change

Severity: Major

Log text:

COM502 OPC to NE 2113 Sh 1 link lost.Request initiated by user: root





Step Action

9 Tab to the Print Details button and press Ctrl_A (or Keypad 0) to select it.

Go to step 12.

You get a printout of the selected event.

Note: The Print Details selection is not enabled if there is no printer connected the SERIAL port.

10 Move to an event you need to print. Press Ctrl_Y (or Keypad .) to select the event. Repeat this step to select a maximum of five events.


Note: You can select and print up to five events at one time. If you select more than five events, the Print Details command is inactive.Printing event details


The List menu appears.OTP1089.eps

12 Use the arrow keys to move to the Print Details command, and press the Space bar (or Keypad 0) to select it.

You get a printout of the selected events.

Note: The Print Details selection is not enabled if there is no printer connected to the SERIAL port.

—continued—

> Event Browser.



[ Update List ]

NE # NE Name




5 Help H




Step Action

13 You can print the details of more events or close the tool.






—end—


print more events step 4

close the tool step 14



Procedure 1-15Displaying the alarm details for a new alarm

Use this procedure to display a new alarm.

When a new alarm is raised, the count in the banner fields increases. There are two banner fields, the Network View and the User View. The user receives notification of the new incoming alarm by highlighting and/or beeping. The types of notification the system sends depends on your display options.

The list of alarms contains a one line summary for each active alarm in the OPC span of control. Details are available for each alarm in a separate dialog. Alarms that clear remain displayed until the list updates. The list of alarms does not contain logs, failed protection switches, lockouts, active protection switches, or performance monitoring data.

Note: An asterisk (*) in the Time column of this tool indicates the alarm occurred at least one day prior to the current date of the OPC.

—continued—

Before you start



Procedure tasks

• Open the Alarm Monitor tool (step 1).

• Note any fields in the banner that appear in reverse video. The reverse video indicates new alarms of the category occurring after the last use of the Clear Highlighting command (step 4).

• Select from one to five alarms you need more information about (step 7).



Expected results

• The alarm details for the new alarm appear.






Procedure 1-15 (continued) Displaying the alarm details for a new alarm

Action

Step Action



2 Within Network Surveillance tools, use the up/down arrow keys to position the cursor at the Alarm Monitor option.

3 Press Ctrl_A (or Keypad 0) to open the Alarm Monitor.

The Alarm Monitor main window appears. OTP1099.eps

4 Note any fields in the banner that are in reverse video. The reverse video indicates new alarms that occur after the last use of the ‘Clear Highlighting’ command.

5 In the left column of the list of alarms, look for one of the following symbols. The symbols indicate a new alarm, and the severity of the alarm.



—continued—

? the alarm is the result of a loss of communication or other conditions

+ there is a new alarm

* the alarm is active and highlighted on the screen

> Alarm Monitor Options.

Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2

Alarms sorted by severityShowing: All Severities, All NEs, OPC

[*] Auto Update List

NE# NE Name Alm# Cls Sh Unit Reason Time Sev2046 19 Fac 2 OC48 G9 1 Sect Rx loss of 14:44:13 C,SA2046 12 Fac 2 OC48 G8 1 Sect Rx loss of 20:01:17* C,SA2046 15 Fac 2 MOR G2 2 Blue loss of sig 14:43:10 M,SA

+ 2046 79 Fac 2 OC48 G8 1 PM 15min line/se 15:15:01 m,nsa+ 2046 77 Fac 3 OC192 G15 1 PM 15min line/se 15:15:01 m,nsa




Step Action

7 Move to an alarm you need more information about, and press Ctrl_A (or Keypad 0) to select it.


Move to other alarms you need more information about (maximum five) and press Ctrl_Y (or Keypad .).



The menu appears.


Alarm Details dialogs for the selected alarms appear.

Note: If you selected more than one alarm, continue to press Ctrl_A (or Keypad 0) to display the Alarm Details dialog for each item.

OTP0440.eps

10 Note important information, such as the type and location of the unit where the alarm is from, or its Facility ID.

11 Press Ctrl_A (or Keypad 0) to select the Done button to close the dialog.

The Alarm Details dialog closes.

—continued—

Alarm Details:








Step Action

12 Reset the count of new alarms. To do the reset, press Ctrl_L T to display the Options menu (or Keypad 2 and use the arrow keys to scroll to options menu).

The Options menu appears.OTP1100.eps

13 Press the Space bar (or Keypad 0) to select the Clear highlighting command.

The count of new alarms resets.






—end—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2





Clear highlightingShow allDisplay options...

Help

Ctrl+X F

>>

123

4



Procedure 1-16 Displaying an active alarm

Use this procedure to display any active alarm.

The list of alarms contains a one-line summary for each active alarm in the OPC span of control. Details are available for each alarm in a separate dialog. If you are updating the list of alarms manually, cleared alarms remain displayed until you update the list. The list of alarms does not contain logs, lockouts, or performance data.

—continued—

Before you start



Procedure tasks


• Select one to five alarms you need more information about (step 5).



Expected results

• The alarm details for the selected alarm appear.






Procedure 1-16 (continued)Displaying an active alarm

Action

Step Action








5 Move to an alarm you need more information about and press Ctrl_A (or Keypad 0) to select it.


Move to other alarms you need more information about (maximum of five), and press Ctrl_Y (or Keypad .).



The menu appears.

—continued—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2







Procedure 1-16 (continued) Displaying an active alarm

Step Action


The Alarm Details dialogs for the selected alarms appears.

Note: If you selected more than one alarm, continue to press Ctrl_A (or Keypad 0) to display the Alarm Details dialog for each item.

OTP0440.eps

8 Take note of important information, such as the type and location of the unit where the alarm came from, or facility ID.

9 Press Ctrl_A (or Keypad 0) to select the Done button to close the dialog.

The Alarm Details dialog closes.






—end—

Alarm Details:







Procedure 1-17Defining the user view and display options

Use this procedure to define a user view of the network. This procedure allows you to remove network elements from the user view.

Note: When you start the Alarm Monitor for the very first time, the complete network is in the user view.

You can change the display of new alarms in the user view section of the alarm banner. The user receives notification of the new incoming alarm by highlighting and/or beeping. The types of notification the system sends depends on your display options.

The user view banner line does not display if:

• there is no user view defined

• the user view is equivalent to the network view

—continued—

Before you start



Procedure tasks


• Display the Options menu (step 4).

• Select the Display Options item (step 5).

• Modify the options (step 6).

• Select OK to save the new display options (step 8).

Expected results

• The selected network elements appear in the user view and the selected alarm attributes are set (highlighting or beeping).






Procedure 1-17 (continued)Defining the user view and display options

Action

Step Action






4 Press Ctrl_L T to display the Options menu (or Keypad 2 and use arrow keys to scroll to options menu).

The Options menu appears.

—continued—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2







Procedure 1-17 (continued) Defining the user view and display options

Step Action

5 Use the arrow keys to move to the Display options command and press the Space bar (or Keypad 0) to select it.

The Alarm Monitor Display Options dialog appears. There are some default settings selected for you.

OTP0537.eps

The words “Included” or “Not included” appear next to Network elements and OPC in the list of Network elements in the user view.

There is a list of the alarm categories at the top of the dialog. Configure the Feedback separately for each category.

—continued—

Alarm Monitor Display Options

Feedback for new alarms: Beeps Beeps Critical > 4 Major > 2 minor > 0 warning > 0 Failed protection > Lockout > Active protection > Performance alert >

Network Elements in user view: Network Element 0 OPC2046P Included 2046 Included 2047 Included 2048 Included

[ OK Return ] [ Cancel Del ]




Step Action

6 If you need to modify the user view:

a. Tab to the Network Elements in the user view list. Use the arrow keys to select the network element or OPC that you need to include or not include in the user view.

b. Press Ctrl_L (or Keypad Enter) for the List item menu to appear.

The List item menu appears. The first menu item (Add) is highlighted. OTP0538.eps

c. To add a network element or OPC to the user view, press the Space bar (or Keypad 0) to select Add.

The network element is now in the user view.The word Included appears next to the network element in the list.

d. To remove a network element or OPC from the user view, use the arrow keys to move to the Remove command. Press the Space bar (or Keypad 0) to select it.

The network element in no longer in the user view. The words “Not Included” appear next to the network element in the list.

—continued—

Alarm Monitor Display Options

Feedback for new alarms: Beeps Beeps Critical > 4 Major > 2 minor > 0 warning > 0 Failed protection > Lockout > Active protection > Performance alert >

Network Elements in user view: Network Element 0 OPC2046P Included 2046 Included 2047 Included 2048 Included

[ OK Return ] [ Cancel Del ]

1 Add •+2 Remove


5 Help •H




Step Action

7 If you need to enable or disable the beep:

a. Tab to the Beeps field next to the alarm category you need to configure.

The field is highlighted.

b. Press Ctrl_A (or Keypad 0) to select the field.

c. Type the number of beeps you need (from 0 to 5).

Note: Some terminals cannot beep.

8 If you need to save the new display options, tab to the OK button and press Ctrl_A (or Keypad 0) to select it.

The Alarm Monitor Display Options dialog closes. The occurrence of the next alarm appears according to the set options.






—end—



Procedure 1-18Defining a filter

Use this procedure to indicate the subset of alarms you need to see in the list of alarms. You can display alarms by network element, by severity, or by time range.

—continued—

Before you start



Procedure tasks


• Display the list of alarms (step 5).

• Select the Filter item (step 6).

• Limit the number of alarms displayed (step 7).

• Add or remove the selected network elements from the list (step 8).

• Add or remove the selected alarm severity (step 9).

• Change the year, month, date, or time to modify the time range (step 10).

• If you need to replace the current data with the default filter, select the Revert to last saved item (step 12).

• If you need to save the data as the default filter, select the Save item (step 13).

• If you need to remove the dialog and not save the data, select the Cancel item (step 14).

• If you need to save the data as a temporary filter for the current session, select the OK item (step 15).

Expected results

• The alarms list appears according to the selected filter.






Procedure 1-18 (continued)Defining a filter

Action

Step Action








5 Press Ctrl_L / (or Keypad 3) to display the alarm list menu.

The List menu appears.

—continued—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2







Procedure 1-18 (continued) Defining a filter

Step Action

6 Use the arrow keys to move to the Filter command and press the Space bar (or Keypad 0) to select it.

The Alarm List Filter dialog appears. F21025-192_R60

7 If you need to change the maximum number of alarms displayed:

a. Tab to the Number of Alarms field and press Ctrl_L (or Keypad Enter) to display the List item menu.

The menu appears. F21031-192_R60

—continued—

[Save S] [Revert to last saved R] [OK Return] [Cancel Del]

0 OPC12345P Included

Alarm List Filter: Number of Alarms: >100 Network Element

9215 Included 9216 Included

Severity: [*] Critical [*] Major [*] minor [*] warning Date and time, from: _________________ < to: _________________ <






1 Select all A2 Deselect all

3 Cut X4 Copy C5 Paste V6 Delete

7 Help H

1




Step Action

b. Press the Space bar (or Keypad 0) to select the Select All command.

The data in the field is highlighted in reverse video.

c. Type the maximum number of alarms that you need displayed in the list of alarms. The maximum number is 500 alarms.

8 If you need to change the network elements included in the list of alarms (and whose alarms appear):

a. Tab to the Network Element list.

The current item in the list is highlighted.

b. Use the arrow keys to move to the network element you need to add or remove. Press Ctrl_L (or Keypad Enter) to display the List item menu.

The List item menu appears. The first menu item (Add) is highlighted. F21032-192_R60

c. To add a network element, press the Space bar (or Keypad 0) to select Add command.

The network element is now in the list. The word “Included” appears next to the network element in the list.

d. To remove a network element, Use the arrow keys to move to the Remove command. Press the Space bar (or Keypad 0) to select it.

The network element is no longer in the list. The words “Not included” appear next to the network element in the list.

—continued—




0 OPC12345P Included1 Add +2 Remove


5 Help H

1





Step Action

9 If you need to add or remove an alarm severity type:

a. Tab to the Severity buttons.

The first Severity button (Critical) is highlighted.

b. Use the arrow keys to move to the severity you need to add or remove. Press Ctrl_A (or Keypad 0) to select it.

The mark next to the button either appears or clears. If the mark is visible, alarms of that the severity appear in the Alarm Monitor tool.

10 If you need to indicate a time range:

a. Tab to the From and To fields.

The cursor appears in the field.

b. To enter another time, use one of the following formats:

day/month/year hr:min:sec

Example: 9/11/1999 10:15:37

OR

day month year hr:min:sec

Example: 9 nov 1999 10:15:37

Note: If you do not select the year, or month, or complete date, the default values are the current year, month, or date. If you do not select the seconds, the default value is zero.

c. To use a predefined offset time, press Ctrl_L / (or Keypad 3).

The chooser menu appears.F21033-192_R60

—continued—






1 Now2 10 min. ago3 30 min. ago4 1 Hour ago5 1 Day ago6 1 Week ago7 Ignore time

1




Step Action

d. Use the arrow keys to move to the predefined offset time you need. Press the Space bar (or Keypad 0) to select it.

The predefined offset time appears in the field.

e. Repeat for the other time range field if required.

11 The entry of filter data is now complete.


The Alarm List Filter dialog contains the default filter data. The filter does not become active in the current session unless you select the OK button.

Go to step 15.


The filter defined is the default filter for the Alarm Summary. The filter does not become active in the current session unless you select the OK button.

Go to step 15.

14 Tab to the Cancel button, and press Ctrl_A (or Keypad 0) to select it.

The Alarm List Filter dialog closes. The filtering data remains the same.

The procedure is complete. Go to step 16.


The Alarm List Filter dialog closes. The defined filter effect for the current session and appears above the list of alarms on the main window.

The selected alarms add to the alarms in the current list. The list can hold 500 alarms. After the 500 maximum, alarms drop from the display. Change the filter if you need to see these alarms.






—end—


replace the current data with the default filter step 12

save the data as the default filter step 13

remove the dialog and do not save the data step 14

save the data as a temporary filter for the current session step 15



Procedure 1-19Changing the contents of the list of alarms

Use this procedure to modify the list of alarms display so that it shows only new or active alarms.

—continued—

Before you start



Procedure tasks


• Display the Options menu (step 4).

• Select the Show all item (step 5).

• Select your next step (step 6).

Expected results

• The list of alarms display shows only new or active alarms.






Procedure 1-19 (continued)Changing the contents of the list of alarms

Action

Step Action






4 Press Ctrl_L T to display the Options menu (or Keypad 2 and use the arrow keys to scroll to options menu).

—continued—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2







Procedure 1-19 (continued)Changing the contents of the list of alarms

Step Action

OTP1100.eps

5 Use the arrow keys to move to the Show all command and then press the right arrow key to move to the submenu.

The menu appears.


7 Press the Space bar (or Keypad 0) to select the option.

The list of alarms updates to show only the alarms you selected.






—end—

If you need to view Then move to

alarms that have arrived since the last time you used the Clear highlighting command

new alarms

all alarms active alarms


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2





Clear highlightingShow allDisplay options...

Help

Ctrl+X F

>>

123

4



Procedure 1-20 Sorting the list of alarms

Use this procedure to sort the alarms. The current sort order appears above the Alarm list.

—continued—

Before you start



Procedure tasks




• Select your next step (step 6).

Expected results

• The list of alarms sorts according to the selected options.






Procedure 1-20 (continued)Sorting the list of alarms

Action

Step Action

1 Log in to the OPC and open the Alarm Monitor tool.





4 Tab to the list of alarms and press Ctrl_L / (or Keypad 3) to display the List item menu.

The list menu appears.

—continued—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2







Procedure 1-20 (continued) Sorting the list of alarms

Step Action

5 Use the arrow keys to move to the Sort command and press the right arrow key to move to the submenu.

The first item in the submenu is highlighted. OTP1102.eps

6 Use the arrow keys to move to the option in the submenu that you need:

7 Press the Space bar (or Keypad 0) to select the option menu.

The list of alarms updates to show the alarms in the sort order you selected. The new sort order appears above the list of alarms.






—end—

If you need to view alarms Then move to

by alarm severity (for example, critical alarms first, then major alarms, then minor alarms, then warning alarms)

by severity

by network element (the newest alarm of the network element appears first)

by network element

by time (the newest alarm appears at the top of the list)

by time


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2





1 Filter... •F2 Sort3 Update Lis >>

4 Help >>

1 by severity2 by network element3 by time



Procedure 1-21 Updating the list of alarms

Use this procedure to add incoming new alarms to the list. You can update the list automatically or manually. The data in the list of alarms updates automatically if Auto Update List is on. If you select Auto Update List, the Update list command is inactive because there is no need to manually update the list of alarms.

—continued—

Before you start



Procedure tasks


• If you need to turn automatic updates on or off, toggle the Auto Update List button on or off (step 4).

• If you need to update the list manually, select the List item menu and then select the Update List item (step 5).

Expected results

• The contents of the list of alarms updates automatically or manually.

• The updated list of alarms appears.






Procedure 1-21 (continued)Updating the list of alarms

Action

Step Action





The Alarm Monitor main window appears.OTP1099.eps

Note: Set the contents of the list of alarms to update automatically or manually. You can switch automatic updates on or off. A manual update is possible if automatic updates is off.

4 If you need to turn automatic updates on or off:

a. Tab to the Auto Update List button.

If a mark appears within the brackets next to the button, automatic updates are active.

b. Press Ctrl_A (or Keypad 0) to toggle the button on or off.

Automatic updates are enabled if the current status is not active, or disabled if the current status is active. The mark in the brackets next to the button indicates the new status.

—continued—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2







Procedure 1-21 (continued)Updating the list of alarms

Step Action

5 If you need to update the list manually (make sure the automatic update is off):

a. Tab to the list of alarms and press Ctrl_L / (or Keypad 3) to display the List item menu.

The List item menu appears.OTP1101.eps

b. Use the arrow keys to move to the Update List command and press the Space bar (or Keypad 0) to select it.

Note: Note the Update List command is disabled when the Auto Update List button is on.

All new alarms appear in the list, and cleared alarms no longer appear.






—end—


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2





F>>

H

Filter...SortUpdate List

Help

123

4



Procedure 1-22 Printing alarm details

Use this procedure to print the details of a single alarm or of up to five alarms.

—continued—

Before you start



• Make sure that the printer connected to the SERIAL port is working.

Procedure tasks


• Print one alarm from the Alarm Details dialog (step 5).

• Print up to five alarms from the Alarm Details dialog (step 10).

Expected results

• You get a printout of the details of one alarm or up to five alarms.






Procedure 1-22 (continued)Printing alarm details

Action

Step Action






4 You can select and print the details of one to five alarms at one time from the list of alarms.

—continued—


print an Alarm from the Alarm Details dialog step 5

print one to five alarms from the list of alarms step 10


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2








Step Action


The current item in the list of alarms is highlighted.

6 Use the arrow keys to move to the alarm you need to print and press Ctrl_A (or Keypad 0) to select it.



The menu appears.


The Alarm Details dialog for the selected alarm appears. OTP0440.eps

9 Tab to the Print Details button and press Ctrl_A (or Keypad 0) to select it.

You get an Alarm Details printout of the selected alarm.

Note: If a printer is not connected to the SERIAL port, the Print Details command is not enabled.

Go to step 14.

10 Use the arrow keys to move to the alarms you need to print and press Ctrl_Y (or Keypad .) to select each one.


—continued—

Alarm Details:








Step Action



Note: If you select more than five alarms, the Print Details command is inactive.

12 Tab to the Print Details command and press the Space bar (or Keypad 0) to select it.

You get a printout of the selected alarms.

Note: If a printer is not connected to port B, port 1, or port SERIAL, the Print Details command is not enabled.

13 You can print the details of more alarms or close the tool.






—end—


print more alarms step 4

close the tool step 14


Network View


Critical2

Major1

warning.

FailProt-

Lockout.

ActProt.

PrfAlrt-

minor2





Details... D

Select >>Deselect >>

Print Details

Help H

1

23

4

5



Procedure 1-23Displaying active alarms

Use this procedure to display a summary of active alarms for a network element.

—continued—

Before you start

• Log on to the network element user interface (NE UI).

User interface path

OTP0330.eps

Note: The above illustration is a sample of the NE UI main menu for a Combiner network element.

Procedure tasks

• Access the main menu of the NE UI and enter alm to select the ALarMs item (step 2).

• Enter al to list all the active alarms (step 3).

Expected results

• The list of all active alarms for the network element appears.


— Check that the shelf controller is in the shelf and is working.


ALarMs EQuipment FAcilityOptical FAcility ADministration

PerformanceMonitoring

PayLoad(Combiner

Only)

Main Menu

PRotection

list all activeALarms

list all activeALarms by

Severity


Class

ALarmDetails

LOGOUT

List allHistoricalalarms

Quit

Help



Procedure 1-23 (continued)Displaying active alarms

Action

Step Action

1 Log in to the Network Element User Interface (NE UI).

See the procedures in Network Element User Interface Description, 323-1801-195, if you do not know how to log in to the network element.

The NE UI main menu appears.OTP1039.eps

Note: The above NE UI main menu is from the 1600G Amplifier

2 Display the active alarms from the Main Menu NE UI by entering:

alm ↵

The Alarm menu appears.OTP1041.eps

—continued—

Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 11:45Main Menu--------- 1. ALarMs 2. PRotection 3. EQuipment 4. OTR FAcility 5. ADministration 6. LOGOUT 7. HELP

Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 11:45Alarm Menu----------0. Quit1. list all active ALarms2. list all active ALarms by Severity3. list all active ALarms by Class4. ALarm Details5. List all Historical alarmsNE 2128>



Procedure 1-23 (continued)Displaying active alarms

Step Action

3 Select the list all active ALarms, from the current menu by entering:

al ↵

The active alarms appear. The following figure is an example of active alarm output.

OTP1042.eps

—end—

Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 11:45Alarm Menu----------0. Quit1. list all active ALarms2. list all active ALarms by Severity3. list all active ALarms by Class4. ALarm Details5. List all Historical alarmsNE 2128> a1

Alm# Cls Sh Type Unit Reason Sev28 Eqp 1 OPC G1 OPC storage circuit pack missing m,nsa27 Eqp 1 OPC G1 OPC controller circuit pack missing m,nsa1 Env 1 CE High shelf temperature m,nsa

NE 2128>



Procedure 1-24Displaying active alarms according to severity

Use this procedure to display active alarms according to severity.

—continued—

Before you start


User interface path

OTP0331.eps


Procedure tasks


• Enter als to select the List active ALarms by Severity (step 3).

• Enter the alarm severity (step 4).

Expected results

• The list of all active alarms according to the severity selected for the network element appears.




ALarMs EQuipment FAcility ADministration PerformanceMonitoring

Main Menu

PRotection



Severity


Class

ALarmDetails

LOGOUT


Quit

Optical FAcility Help

PayLoad(Combiner

Only)



Procedure 1-24 (continued)Displaying active alarms according to severity

Action

Step Action




2 Select ALarMs from the Main Menu by entering:

alm ↵The Alarm menu appears.

OTP1041.eps

—continued—

Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 11:45Main Menu--------- 1. ALarMs 2. Performance Monitoring 3. PRotection 4. EQuipment 5. FAcility 6. Optical FAcility 7. PayLoad 8. ADministration 9. LOGOUT10. HELP




Procedure 1-24 (continued)Displaying active alarms according to severity

Step Action

3 Select the List active ALarms by Severity item from the current menu by entering:

als ↵

4 Select the alarm category by entering:

<alarm severity>↵

If there are no active alarms, a no active alarms message appears.

The active alarms of the selected severity are displayed. The following figure is an example of active critical alarm output.

F3200-192_R50

5 To display the alarms of another severity, press the Return key to go back to the Alarm Menu.

Continue with step 3.

—end—

where is

<alarm severity> C (critical alarm)MA (major alarm)MI (minor alarm)W (warning)

Alm # Cls Sh Type Unit Reason Sev 41 Eqp 2 QOC12 G3 Circuit pack fail C,SA 34 Eqp 2 OC48 G5 Circuit pack fail C,SA 33 Fac 2 OC48 G1 1 Sect Rx loss of signal C,SA 32 Fac 2 OC192 G1 1 Sect Rx loss of signal C,SA 31 Fac 2 OC12 G17 1 Line AIS C,SA NE 2>



Procedure 1-25Displaying active alarms according to class

Use this procedure to display active alarms according to class.

—continued—

Before you start


User interface path

OTP0332.eps


Procedure tasks


• Enter alc to select the List active ALarms by Class (step 3).

• Enter the alarm class (step 4).

Expected results

• The list of all active alarms according to the class selected for the network element appears.





Main Menu

PRotection



Severity


Class

ALarmDetails

LOGOUT


Quit


PayLoad(Combiner

Only)



Procedure 1-25 (continued)Displaying active alarms according to class

Action

Step Action




2 Select ALarMs, from the Main Menu by entering:


OTP1041.eps

—continued—





Procedure 1-25 (continued)Displaying active alarms according to class

Step Action

3 Select the List active ALarms by Class item by entering:

alc ↵

4 Select the alarm class by entering:

<alarm class>↵

If there are no active alarms, a no active alarms message appears.

The active alarms of the selected class appear. The following figure is an example of active facility alarm output.

F3201-192_R60

5 Display the alarms of other classes, press the Return key to go back to the Alarm Menu.


—end—

where is

<alarm class> env (environmental)eqp (equipment)fac (facility)

Alm # Cls Sh Type Unit Reason Sev 33 Fac 2 OC48 G1 1 Sect Rx loss of signal C,SA 32 Fac 2 OC192 G1 1 Sect Rx loss of signal C,SA 31 Fac 2 OC12 G17 1 Line AIS C,SA 2790 Fac 1 ESI BITS B Degraded clock carrier m,nsa 2532 Fac 1 COMM ENET 1 MI ethernet loss of signal m,nsa

NE 2>



Procedure 1-26Displaying alarm details

Use this procedure to display alarm details.

—continued—

Before you start


User interface path

OTP0333.eps


Procedure tasks


• Enter ald to select the Alarm Details item (step 3).

• Enter the alarm number (step 4).

Expected results

• The details of the selected alarm appear.





Main Menu

PRotection



Severity


Class

ALarmDetails

LOGOUT


Quit


PayLoad(Combiner

Only)



Procedure 1-26 (continued)Displaying alarm details

Action

Step Action






OTP1041.eps

—continued—





Procedure 1-26 (continued)Displaying alarm details

3 Select the ALarm Details item by entering:

ald ↵

4 Select the alarm number by entering:

<alarm number>↵

If there are no alarms active with that number, a no active alarms message appears.

The active alarm of the selected alarm number appears. The following figure is an example of alarm detail output.

OTP1043.eps

5 Display the alarm details of another alarm, press Return to go back to the Alarm Menu.


—end—

where

<alarm number> is value ranging from 1 to 9999

xterm

Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 12:02----------------Alarm Menu----------0. Quit1. list all active ALarms2. list all active ALarms by Severity3. list all active ALarms by Class4. ALarm Details5. list all Historical alarms

NE 2128> ALDEnter the alarm ID:[ 1-9999]? 27 Alm Rpt: 27 Minor Unit: OPC G1 nsa Address: 2048 Shelf: 1 10:48:36Location: Frame: - shPos: 1 Slot: 5 01-11-99 Reason: OPC controller circuit pack missing EQPEquip ID: PEC:NE 2128>



Procedure 1-27Displaying historical alarms

Use this procedure to display historical alarms. Only the last 50 alarms appear.

—continued—

Before you start


User interface path

OTP0334.eps


Procedure tasks


• Enter lh to select the List of all Historical alarms item (step 3).

Expected results

• The details of the selected alarm appear.


— Check the shelf controller is in the shelf and is working.



Main Menu

PRotection



Severity


Class

ALarmDetails

LOGOUT


Quit


PayLoad(Combiner

Only)



Procedure 1-27 (continued)Displaying historical alarms

Action

Step Action






OTP1041.eps

—continued—





Procedure 1-27 (continued)Displaying historical alarms

Step Action

3 Select the List all Historical alarms item by entering:

lh ↵

Historical alarms appear. The following figure is an example of a historical alarm output.

OTP1044.eps

—end—

xterm

Toronto C 000 M 001 m 036 w 000 LckOut 000 ActPt 000 12:04Alarm Menu----------0. Quit1. list all active ALarms2. list all active ALarms by Severity3. list all active ALarms by Class4. ALarm Details5. list all Historical alarmsNE 2128> LH

ALM300 MAY 10-2000 18:49:50 8692 Facility alarmInitiated by: SYSTEMAlmRpt: 14 ClearedUnit: OTR G0 2 nsaAddress: 2128 Shelf: 2 18:49:50Location: Frame: ShPos: 2 10-05-00Reason: OSC loss of signal FACFac ID:

ALM300 MAY 10-2000 00:34:00 8318 Facility alarmInitiated by: SYSTEMAlmRpt: 92 ClearedUnit: OTR G5 1 nsaAddress: 2128 Shelf: 2 00:34:00Location: Frame: ShPos: 2 10-05-00Reason: OSC DCC link fail FACFac ID:

- More ('ht' to halt; <CR> to print next screen; n <CR> to print next n lines)-



Procedure 1-28Displaying OPC alarms and the OPC pointer alarm status and severity

Use this procedure to display the OPC Alarm Provisioning tool. The main window of the OPC Alarm Provisioning tool has two sections. The top section displays the severity and status of the OPC pointer alarm. The bottom section displays the severity and status of all OPC alarms. The severity of the alarm can be Critical, Major, minor or warning. The status of the alarm can be ON or OFF.

Table 1-3 lists the operations you can perform from the OPC Alarm Provisioning tool.

—continued—

Table 1-3OPC Alarm Provisioning Operations

Enabling and disabling OPC alarms Procedure 1-29

Clearing OPC alarms Procedure 1-30

Provisioning the network element to raise the pointer alarm Procedure 1-31

Enabling and disabling the OPC pointer alarm Procedure 1-32

Changing the severity of the OPC pointer alarm Procedure 1-33

Before you start



Procedure tasks

• Open the OPC Alarm Provisioning tool (step 1).

Expected results

• The window that displays the severity and status of the OPC alarms and the OPC pointer alarm.






Procedure 1-28 (continued)Displaying OPC alarms and the OPC pointer alarm status and severity

Action

Step Action

1 Log in to the OPC and open the OPC Alarm Provisioning tool.

The OPC Alarm Provisioning window appears. F26425-192_R60

—end—

> OPC Alarm Provisioning

Showing: OPC pointer alarm

UUtUUilities

NE for Prim. OPC NE for Back. OPC Reason Severity Status 9215 9216 OPC alarm(s) active minor OFF

Showing: all OPC alarms

Reason Severity StatusLost peer OPC minor ONConfiguration audit fail minor ONConnection audit fail minor ONRemovable media backup/restore fail minor ONDatasync fail minor ONConnection services disabled warning ONPrimary: disk bad media detectedBackup: disk bad media detected


minor ON minor ON

>. OPC Alarm Provisoning Utilities



Procedure 1-29Enabling and disabling OPC alarms

Use this procedure to enable or disable OPC alarms. You can display active OPC alarms with the OPC Alarm Monitor tool. View active and historical OPC alarms with the Event Browser tool. To clear active OPC alarms, see Trouble Clearing and Module Replacement, 323-1801-543.

You can copy provisioning information from the primary OPC to the backup OPC during normal data synchronization. You cannot copy provisioning information from the backup OPC to the primary OPC. If you make OPC alarm provisioning changes on the backup OPC, you must complete the same provisioning on the primary OPC.

—continued—

Before you start



Procedure tasks


• Select the alarm to be enabled or disabled (step 2).

• Enable or disable the alarm (step 5).

• Transfer data to backup OPC (step 11).

Expected results

• The OPC alarms are enabled or disabled.






Procedure 1-29 (continued)Enabling and disabling OPC alarms

Action

Step Action


The OPC Alarm Provisioning window appears. OTP1134.eps

2 Tab to the list, Showing: all OPC alarms.

3 Use the arrow keys to move to the alarm you need to enable or disable.

—continued—



UUtUUilities



Reason Severity StatusLost peer OPC minor ONPrimary: disk 95% full minor ONBackup: disk 95% full minor ONRemovable media backup/restore fail minor ONDatasync fail minor ONHistorical log data lost warning ONPrimary: disk bad media detected minor ONBackup: disk bad media detected minor ON






Step Action

4 Press Ctrl_L (or keypad Enter) to display the List item menu.

The List item menu appears. The Change status command is highlighted and its submenu menu appears.

OTP1135.eps


6 Use the arrow keys to move to the Enable command. Press the Space bar (or Keypad 0) to select this command.

A confirmation dialog appears.F26442

7 Tab to the Yes button. Press Ctrl_A (or Keypad 0) to select this button.Go to step 10.

—continued—


enable the alarm step 6

disable the alarm step 8



UUtUUilities






1 Change state2 Manual clear

3 Select4 Deselect

5 help H

1 Inhibit (OFF)2 Enable (ON)

FW-

[No - ]

You are about to enable the OPC alarm.

Do you wish to continue?

[Yes Return ]




Step Action

8 Use the arrow keys to move to the Inhibit command. Press the Space bar (or Keypad 0) to select the command.


9 Tab to the Yes button. Press Ctrl_A (or Keypad 0) to select this button.

10 Select your next step:.

Note: If you change the provisioning data on the backup OPC, you cannot transfer the new alarm provisioning data to the primary OPC. Instead, you must provision the same data on the primary OPC. If you do not make the provisioning changes to the primary OPC, you lose the new data on the backup OPC during the next database backup.

11 In the OPC Alarm Provisioning tool, press Ctrl_L T to display the Utilities menu (or Keypad 2 and use the arrow keys to scroll to Utilities menu).

The Utilities menu appears.OTP1138.eps

—continued—

If you enabled or disabled an OPC alarm on the Then go to

primary OPC step 11

backup OPC step 16

[No - ]

You are about to inhibit the OPC alarm.


[Yes Return ]



UUtUUilities






1 Transfer data to backup OPC

2 Help




Step Action

12 Press the Space bar (or Keypad 0) to select the Transfer to backup OPC command.

The following confirmation dialog appears.F26449-192_R60

13 You can continue or stop the transfer.

14 Tab to the No button. Press Ctrl_A (or Keypad 0) to select this button.Go to step 16.


A message appears. The message indicates your request is in progress. For the results of the transfer, check the Event Browser.

16 Press Esc ) to close the tool.

Note: The system prompts you to perform a datasync if you have not done so and there is a change to the data.

—end—


stop the transfer step 14

continue the process step 15

[No - ]

Transferring data to the backup OPC will cause any existing data on the backup OPC to be overwritten.


[Yes Return ]



Procedure 1-30Clearing OPC alarms

Use this procedure to manually clear alarms generated by the OPC. Perform this procedure after you correct the problem on the OPC. The system clears OPC alarms one to two minutes after you correct the cause of the alarm. If you manually clear the alarm without correcting the cause, the alarm becomes active again after the hold-off period.

Display OPC alarms using the OPC Alarm Monitor tool or Event Browser tool.

—continued—

Before you start



Procedure tasks


• Select the alarm you need to manually clear (step 3).

• Select the Manual clear command (step 5).

Expected results

• The OPC alarm clears.






Procedure 1-30 (continued)Clearing OPC alarms

Action

Step Action



2 Tab to the section, Showing: all OPC alarms.

3 Use the arrow keys to move to the alarm you need to manually clear.

—continued—



UUtUUilities








Procedure 1-30 (continued)Clearing OPC alarms

Step Action



5 Use the arrow keys to move to the Manual clear command and press the Space bar (or Keypad 0) to select the command.




—end—



UUtUUilities






1 Change state2 Manual clear

3 Select4 Deselect

5 help H


FW-

[No - ]

You are about to manually clear the OPC alarm.


[Yes Return ]



Procedure 1-31Provisioning the network element to raise the pointer alarm

Use this procedure to select the network element where the OPC pointer alarm appears. When the pointer alarm is enabled, the selected network element provides notification of active OPC alarms.

This procedure is optional. Use the pointer alarm when you use only network element surveillance applications for surveillance.

You must specify the network element on which the pointer alarm will be raised before you can enable the pointer alarm. The pointer alarm is disabled by default. See Procedure 1-32 to enable the pointer alarm.

Provision a network element in the primary OPC span of control to raise the pointer alarm. Provision another network element to raise the pointer alarm if there is a backup OPC in the same span of control. It is recommended you select the network element where the OPC exists.

—continued—

Before you start



Procedure tasks


• Select the Set NE command (step 4).

• Enter the network element number for the primary OPC (step 6).

• Enter the network element number for the backup OPC if there is one (step 7).

Expected results

• A network element has the provisioning to raise the OPC pointer alarm.






Procedure 1-31 (continued)Provisioning the network element to raise the pointer alarm

Action

Step Action



2 Tab to the section, Showing: OPC pointer alarm.

—continued—



UUtUUilities









Step Action



4 Use the arrow keys to move to the Set NE command. Press the Space bar (or Keypad 0) to select this command.

The Set NE dialog appears. F26447

5 Make sure the cursor is in the Set NE for primary OPC field.

—continued—



UUtUUilities






1 Change status >>

2 Change severity

3 Set NE...

4 Select5 Deselect

6 Help H


FW-

[Cancel Del]

NE on which to raise the OPC pointer alarmNE on which to raise the OPC pointer alarmNE on which to raise the OPC pointer alar

[OK Return]

Set NE for primary OPC > Set NE for backup OPC > <

<




Step Action

6 Enter the network element number or use the chooser to indicate the network element where the pointer alarm for the primary OPC is raised.

Note: Press Ctrl_L / (or Keypad 3) to get the chooser menu. In the chooser menu use the arrow keys to move to the required network element number. Press the Space bar (or Keypad 0) to select the number.

The network element number appears in the field.

7 If there is a backup OPC in the span of control, tab to the Set NE for backup OPC field. If there is no backup OPC for the span of control go to step 9.

8 Enter the network element number or use the chooser to indicate the network element where the pointer alarm for the backup OPC is raised.

Note: Press Ctrl_L / (or Keypad 3) to get the chooser menu. In the chooser menu use the arrow keys to move to the required network element number. Press the Space bar (or Keypad 0) to select the number.

9 Tab to the OK button. Press Ctrl_A (or Keypad 0) to select this button.

The Set NE dialog closes and the network element(s) selected appear in the OPC Alarm Provisioning tool.


—end—



Procedure 1-32Enabling and disabling the OPC pointer alarm

Use this procedure to enable or disable the OPC pointer alarm. When the pointer alarm is enabled, the provisioned network element provides notification of active OPC alarms. Use this procedure when you use only network element surveillance applications.

Before you can enable the OPC pointer alarm, you must first select and provision the network element where the alarm is to be raised. See Procedure 1-31, “Provisioning the network element to raise the pointer alarm”.

You can copy new provisioning information from the primary OPC to the backup OPC during normal data synchronization. You cannot copy provisioning information from the backup OPC to the primary OPC. If you enable or disable the pointer alarm on the backup OPC, you must complete the same provisioning on the primary OPC.

—continued—

Before you start



• Provision a network element in the primary OPC span of control to raise the pointer alarm, seeProcedure 1-31.“Provisioning the network element to raise the pointer alarm”.

Procedure tasks


• Enable or disable the pointer alarm (step 3).

• Transfer the new data to the backup OPC (step 10).

Expected results

• The OPC pointer alarm is enabled or disabled.






Procedure 1-32 (continued)Enabling and disabling the OPC pointer alarm

Action

Step Action



2 Tab to the OPC pointer alarm section.

—continued—



UUtUUilities









Step Action




Note: Before you can enable the pointer alarm you must first provision the network elements to raise the pointer alarm. See Procedure 1-31, “Provisioning the network element to raise the pointer alarm”.

5 Use the arrow keys to move to the Enable command. Press the Space bar (or Keypad 0) to select this command.


6 Tab to the Yes button. Press Ctrl_A (or Keypad 0) to select this button.Go to step 10.

—continued—


enable the pointer alarm step 5

disable the pointer alarm step 7



UUtUUilities






1 Change status >>

2 Change severity

3 Set NE...

4 Select5 Deselect

6 Help H


FW-

[No - ]

You are about to enable the OPC pointer alarm.


[Yes Return ]




Step Action

7 Use the arrow keys to move to the Inhibit command. Press the Space bar (or Keypad 0) to select the command.

A confirmation dialog appears.F26444-192_R60



Note: If you changed the provisioning data on the backup OPC, you cannot transfer the new alarm provisioning data to the primary OPC. Instead, you must provision the same data on the primary OPC. If you do not make the provisioning changes to the primary OPC, you lose the new data on the backup OPC during the next database backup.



—continued—

If you enabled or disabled the OPC pointer alarm on the Then go to

primary OPC step 10

backup OPC step 15

[No - ]

You are about to inhibit the OPC ponter alarm.


[Yes Return ]



UUtUUilities







2 Help




Step Action


A confirmation dialog appears.F26449-192_R60






Note: If you close the tool after you make provisioning changes without saving these changes to the backup OPC, a prompt appears. Tab to the Yes button to transfer the changes and press Ctrl_A (or Keypad 0) to select this button.

—end—




[No - ]



[Yes Return ]



Procedure 1-33Changing the severity of the OPC pointer alarm

Use this procedure to provision the severity of the pointer alarm. You can provision the severity to be Critical, Major, minor or warning. The default severity is minor.

You can copy new provisioning information from the primary OPC to the backup OPC during normal data synchronization. You cannot copy provisioning information from the backup OPC to the primary OPC. If you change the severity of the pointer alarm on the backup OPC, you must complete the same provisioning on the primary OPC.

.

—continued—

Before you start



Procedure tasks


• Change the alarm severity (step 3).

• Transfer the new data to the backup OPC (step 8).

Expected results

• The OPC pointer alarm severity changes.






Procedure 1-33 (continued)Changing the severity of the OPC pointer alarm

Action

Step Action



2 Tab to the OPC pointer alarm section.


The List item menu appears.

—continued—



UUtUUilities









Step Action

4 Use the arrow keys to move to the Change severity command.

The Change severity submenu appears.OTP1136.eps

5 Use the arrow keys to move to the new severity. Press the Space bar (or Keypad 0) to select the severity.



—continued—



UUtUUilities






1 Change status >>

2 Change severity

3 Set NE...

4 Select5 Deselect

6 Help H

1 Critical2 Major3 minor4 warning

FW-

[No - ]

You are about to change the severity of theOPC pointer alarm to critical.


[Yes Return ]




Step Action


Note: If you changed the provisioning data on the backup OPC, you cannot transfer the new alarm provisioning data to the primary OPC. Instead, you must provision the same data on the primary OPC. If you do not make the provisioning changes to the primary OPC, you lose the new data on the backup OPC during the next database backup.



—continued—

If you changed the severity of the OPC pointer alarm on the Then go to

primary OPC step 8

backup OPC step 13



UUtUUilities







2 Help




Step Action


The following confirmation dialog appears.F26449-192_R60






Note: If you close the tool after you make provisioning changes without saving these changes to the backup OPC, a prompt appears. Tab to the Yes button to transfer the changes and press Ctrl_A (or Keypad 0) to select this button.

—end—




[No - ]



[Yes Return ]




2-1

Alarm definitions 2-This chapter provides you with, the definition of all alarms and alerts, and references to the correct procedure within the NTP, Trouble Clearing and Module Replacement, 323-1801-543, on troubleshooting alarms and if necessary, equipment replacement.

Note: For amplifier related alarms or alerts, refer to the NTP, 1600G Amplifier Alarm Clearing and Module Replacement, 323-1801-546. For alarms relating to the MOR Plus fiber-optic link, refer to the NTP, MOR Plus Alarm Clearing and Module Replacement, 323-1801-545

Procedures to perform troubleshooting on alarms can be found in the respective NTP as listed below:

Table 2-1 lists all the supported circuit packs for existing OPTera Long Haul 1600 network elements. The table includes the following information:

• the network element where the circuit pack is supported

• the shelf where the circuit pack is located

• the release version(s) in which the circuit pack is supported

Table 2-2 lists all the alarms in alphabetical order by alarm class and type. The table includes the following information:

• the severity for each alarm as critical, major, minor, indeterminate or warning according to whether any affected traffic is protected or unprotected

• a service code of service affecting (SA) or non-service-affecting (nsa) according to whether any affected traffic is protected or unprotected

• the default provisioning status as either enabled or disabled

2-2 Alarm definitions


Legend:

RPT — Repeater

CMB — Combiner

AMP — 1600G Amplifier

MN — Main shelf

EXT 1 — First extension shelf

Table 2-1Supported OPTera Long Haul 1600 circuit packs

Circuit Pack Network Element Shelf Release

OPC storage (POPS), OPC controller (POPC), and OPC interface (POPI)

CMB, RPT, AMP Control 1.5, 2, 3

shelf controller (SC) CMB, RPT, AMP Control 1.5, 2, 3

external synchronization interface (ESI) CMB Control 2

maintenance interface (MI) CMB, RPT, AMP Control 1.5, 2, 3

message exchange (MX) CMB, RPT, AMP Control 1.5, 2, 3

parallel telemetry (PT) CMB, RPT, AMP Control 1.5, 2, 3

orderwire (OW) CMB, RPT, AMP Control 1.5, 2, 3

multiwavelength optical repeater (MOR Plus) RPT, CMB MN 1.5, 2

2.5G WT RPT MN, EXT 1 1.5

10G WT RPT MN, EXT 1 2

OC-192/STM-64 XR RPT MN, EXT 1 1.5

OC-192/STM-64 T/R CMB MN, EXT 1 2

OC-48/STM-16 T/R CMB MN, EXT 1 2

timing distribution card (TDC) CMB MN 2

Uni-directional optical service channel (Uni-OSC) AMP MN, EXT 1 3

Bi-directional optical service channel (Bi-OSC) AMP MN, EXT 1 3

dual amplifier (DAMP) AMP MN, EXT 1 3

booster18 AMP MN, EXT 1 3

booster21 AMP MN, EXT 1 3

Alarm definitions 2-3


Table 2-2Network element and OPC alarms

Alarm label Severity Service code Default status

Equipment alarms

Generic equipment alarms

Circuit pack fail minor (protected)Critical (unprotected)

nsaSA

Enabled

Circuit pack mismatch minor (protected)Critical (unprotected)

nsaSA

Enabled

Circuit pack missing minor (protected)Critical (unprotected)

nsaSA

Enabled

Circuit pack overheated minor (protected)Critical (unprotected)

nsaSA

Enabled

Circuit pack provision mismatch minor (protected)Critical (unprotected)

nsaSA

Enabled

Circuit pack unseated minor (protected) nsansa

Enabled

Circuit pack vintage mismatch minor (protected)Critical (unprotected)

nsaSA

Enabled

Equipment forced switch request minor nsa Enabled

Equipment lockout request minor nsa Enabled

Equipment manual switch request minor nsa Enabled

Intercard fail minor (protected)Major (unprotected)

nsansa

Enabled

Loss of power feed A/B minor nsa Enabled

OH Bus multidrop link fail minor nsa Enabled

Software error minor nsa Enabled

Software trap minor nsa Enabled

Tx laser fail minor (protected)Critical (unprotected)

nsaSA

Enabled

—continued—



Common equipment alarms

Autoprovisioning mismatch minor nsa Enabled

Commissioning MI present Major nsa Enabled

Duplicate NE name warning nsa Enabled

Duplicate NE ID warning nsa Enabled

Entry to 20 ppm freerun minor nsa Enabled

Exerciser fail / MX Exerciser fail minor nsa Enabled

Filler card missing minor nsa Enabled

LCAP port intrusion attempt minor nsa Enabled

Manual area address dropped minor nsa Enabled

MI port intrusion attempt minor nsa Enabled

Mismatched switch type minor nsa Enabled

NE approval required minor nsa Enabled

Network port intrusion attempt minor nsa Enabled

Node in reconfiguration mode minor nsa Enabled

Node in site-test configuration minor nsa Enabled

Number of level 1 NEs exceeded minor nsa Enabled

Protection path fail minor nsa Enabled

Reconfiguration failed warning nsa Enabled

Serial number inconsistency Major nsa Enabled

Shelf autoprovisioning mismatch minor nsa Enabled

Software transfer fail Major nsa Enabled

Unknown software release Major nsa Enabled

—continued—

Table 2-2 (continued)Network element and OPC alarms




External synchronization interface equipment alarms

End VCO range warning nsa Enabled

Failure to lock minor (protected or SONET/SDH freerun)

Major (unprotected)

nsa

SA

Enabled

Timing generation entry to acquire minor nsa Enabled

Timing generation entry to freerun minor nsa Enabled

Timing generation entry to fast Minor nsa Enabled

Timing generation entry to holdover minor nsa Enabled

OPC equipment alarms

Backup/Primary: disk 95% full minor nsa Enabled

Backup/Primary: disk bad media detected minor nsa Enabled

Backup/Primary: network port intrusion minor nsa Enabled

Backup/Primary: serial port intrusion minor nsa Enabled

Backup/Primary: TCP/IP Access violation Major nsa Enabled

Datasync fail minor nsa Enabled

External Ethernet LOS minor nsa Enabled

Historical log data lost minor nsa Enabled

Internal Ethernet LOS minor nsa Enabled

Lost peer OPC minor nsa Enabled

Manual shutdown in progress minor nsa Enabled

OAM software fail minor nsa Enabled

OPC alarm(s) active minor nsa Disabled

Removable media backup/restore fail minor nsa Enabled

Upgrade in progress minor nsa Enabled

—continued—





Shelf equipment alarms

Shelf mismatch minor nsa Enabled

Shelf missing minor nsa Enabled

Orderwire equipment alarms

Auto orderwire seam active warning nsa Enabled

Manual orderwire seam active warning nsa Enabled

Facility Alarms

Generic facility alarms

Channel ID mismatch Major SA Enabled

Degraded clock carrier minor nsa Enabled

Far end protection line fail minor nsa Enabled

FEC provisioning mismatch minor nsa Enabled

Line AIS minor (protected)Critical (unprotected)minor (ESI)

nsaSAnsa

Enabled

Line RFI / MS RDI minor (protected)Critical (unprotected)

nsaSA

Enabled

Max. number of NE exceeded minor nsa Enabled

MI ethernet loss of signal minor nsa Enabled

Path AIS minor nsa Enabled

Payload fail minor nsa Enabled

Section Rx loss of frame / loss of frame (STMn facility)

minor (protected)Critical (unprotected)

nsaSA

Enabled

Section Rx loss of signal / loss of signal (STMn facility)

minor (protected)Critical (unprotected)

nsaSA

Enabled

Section trace mismatch minor nsa Enabled

Signal degrade / MS signal degrade minor (protected)Major (unprotected)minor (ESI)

nsaSAnsa

Enabled

—continued—





Signal fail / MS excessive BER minor (protected)Critical (unprotected)

nsaSA

Enabled

SONET SDCC/LDCC link fail / RS/ MS DCC fail

minor nsa Enabled

External synchronization interface facility alarms

Loss of frame / loss of frame (ESI facility) minor nsa Enabled

Loss of signal / loss of signal (ESI facility) minor nsa Enabled

Tx AIS minor nsa Enabled

Performance monitoring facility alarms

PM 1 minute line/section threshold / PM 1 minute MS/RS threshold

minor nsa Enabled


minor nsa Enabled

PM day line/section threshold / PM day MS/RS threshold

minor nsa Enabled

PM physical TCA minor nsa Enabled

OC-192 4-Fiber BLSR/STM-64 MS-SPRing facility alarms

Default K-bytes minor nsa Enabled

Invalid K-bytes minor nsa Enabled

Invalid neighbour detected minor nsa Enabled

Environmental alarms

Common equipment environmental alarms

Breaker filter A/B fail minor nsa Enabled

Breaker filter A/B missing minor nsa Enabled

Breaker filter A/B tripped / Breaker filter A/B trip

minor nsa Enabled

Cooling unit 1/2, fan 1/2/3 fail/missing minor (protected)Major (unprotected)

nsansa

Enabled

—continued—





Fan 1/2/3 fail minor (protected)Major (unprotected)

nsansa

Enabled

Fan 1/2/3 missing minor (protected)Major (unprotected)

nsansa

Enabled

High shelf temperature minor nsa Enabled

Low shelf voltage Major nsa Enabled

SATT fail minor nsa Enabled

48 V battery A B CE supply fail minor nsa Enabled

48 V battery A B CE supply low minor nsa Enabled

Parallel telemetry environmental alarms

Telemetry input (1 to 32) minor nsa Enabled

Telemetry output minor nsa Enabled

Alerts

Generic Alerts

Equipment protection switch complete minor (ESI)Indeterminate (message exchange)Indeterminate (TDC)

nsansansa

Enabled

Equipment protection switch fail minor (ESI)Indeterminate (message exchange)Indeterminate (TDC)

nsansansa

Enabled

Reference switch complete Indeterminate nsa Enabled

Reference switch fail Indeterminate nsa Enabled

Timing generation entry to normal / timing generation to normal

Indeterminate nsa Enabled

Performance monitoring alerts

LBC threshold 1/2 indeterminate nsa Enabled

Line/Section Rx CV threshold 1/2 / MS/RS Rx CV threshold 1/2


—continued—





Line/Section Rx ES threshold 1/2 / MS/RS Rx ES threshold 1/2


Line Rx FEC threshold 1/2 / MS Rx FEC threshold 1/2


Line/Section Rx SES threshold 1/2 / MS/RS Rx SES threshold 1/2


Line Rx UAS threshold 1/2 / MS Rx UAS threshold 1/2


Section Rx SEFS threshold 1/2 / RS Rx SEFS threshold 1/2






Use the following list to navigate through this chapter.

Alarm Class Alarm type Page

Equipment alarms Generic equipment alarms page 2-11

Common equipment alarms page 2-23

External synchronization interface (ESI) equipment alarms

page 2-30

OPC equipment alarms page 2-32

Shelf equipment alarms page 2-36

Orderwire equipment alarms page 2-36

Facility alarms Generic facility alarms page 2-38

External synchronization interface (ESI) facility alarms

page 2-47

Performance monitoring facility alarms page 2-48

OC-192 4-Fiber BLSR/STM-64 MS-SPRing facility alarms

page 2-51

Environmental alarms Common equipment environmental alarms page 2-52

Parallel telemetry environmental alarms page 2-55

Alerts Generic alerts page 2-56

Performance monitoring alerts page 2-58



Equipment alarms Equipment alarms relate to the actual circuit packs processing the signals. Alarms that are raised against several circuit packs appear under the generic equipment alarms category. Alarms that are specific to a circuit pack type follow.

Generic equipment alarms The following list contains equipment alarms raised against several circuit packs.

Generic equipment alarm Definition Troubleshooting Procedure 1

1. To troubleshoot these alarms, refer to Trouble Clearing and Module Replacement, 323-1801-543.

Circuit pack fail page 2-12 Procedure 2-1

Circuit pack mismatch page 2-14 Procedure 2-2

Circuit pack missing page 2-16 Procedure 2-3

Circuit pack overheated page 2-17 Procedure 2-4

Circuit pack provision mismatch page 2-17 Procedure 2-5

Circuit pack unseated page 2-18 Procedure 2-6

Circuit pack vintage mismatch page 2-18 Procedure 2-7

Equipment forced switch request page 2-19 Procedure 2-8

Equipment lockout request page 2-19 Procedure 2-9

Equipment manual switch request page 2-19 Procedure 2-10

Intercard fail page 2-19 Procedure 2-11

Loss of power feed A/B page 2-21 Procedure 2-12

OH Bus multidrop link fail page 2-21 Procedure 2-13

Software error page 2-21 Procedure 2-14

Software trap page 2-22 Procedure 2-15

Tx laser fail page 2-22 Procedure 2-16



Circuit pack failThis alarm applies to the following circuit packs:

• OPC storage (POPS), OPC controller (POPC), and OPC interface (POPI)

• shelf controller (SC)

• external synchronization interface (ESI)

• maintenance interface (MI)

• message exchange (MX)

• parallel telemetry (PT)

• orderwire (OW)

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R

• timing distribution card (TDC)

A circuit pack failure raises this alarm. The red light-emitting diode (LED) on the circuit pack is lit. The “Circuit pack mismatch” alarm masks the “Circuit pack fail” alarm.

Since the TDC is the only circuit pack which occupies a half-height slot and the OC-48/STM-16 T/R and OC-192/STM-64 T/R circuit packs occupy a full slot, the alarming strategy is as follows:

• A full-height circuit pack is provisioned in the slot and is in-service. If either a half-height slot or the full-height slot contains a failed circuit pack, the alarm is raised against the full-height slot.

• A half-height circuit pack is provisioned in the half-height slot and the half-height slot contains a failed circuit pack. The alarm is raised against the half-height slot.

If this alarm is raised against the maintenance interface, a transient fault also causes the alarm. The red fail LED on the maintenance interface circuit pack lights without actually raising the “Circuit pack fail” alarm. This alarm raised against the maintenance interface circuit pack masks the following environmental alarms:

• Fan 1/2/3 fail

• Cooling unit 1/2 Fan 1/2/3 fail/missing

• Breaker filter A or B fail

• Breaker filter A or B trip

• High shelf temperature



• Low shelf voltage

• SATT fail

If this alarm is raised against an OC-192/STM-64 T/R, the following situations can cause the alarm:

• The wavelength operation is not within the specific range.

• The power provisioning analog control loop is unable to lock onto the provisioned power setting.

Note 1: Upon removal or failure of the shelf controller, data communications channel (DCC) and operations, administration and maintenance (OAM) functions are unavailable. You cannot log in to the system.

Note 2: Upon removal or failure of the maintenance interface, parallel telemetry and user-interface access can be unavailable. Performance monitoring data for this network element can be inaccurate.

Note 3: Upon failure or removal of the message exchange circuit pack, there is no longer communication between the shelf controller, the maintenance interface and the port cards. The port cards include the 2.5G WT, 10G WT, OC-192/STM-64 XR, OC-48/STM-16 T/R, OC-192/STM-64 T/R, TDC, and the ESI circuit packs. A missing or failed message exchange circuit pack interrupts data communication functions. Fault reporting, performance monitoring, software upgrade, and circuit pack configuration are unavailable.

Note 4: Upon failure of the primary OPC, the backup OPC (if available) in the network becomes active. The backup OPC takes control of the network elements within its span of control. If the backup OPC is active for a significant period of time, execute the setserver command using the OSI address of the backup OPC. See the Procedure “Setting the server address on the network element” in System Commissioning and Testing Procedures, 323-1801-222.

Note 5: Upon failure or removal of the orderwire circuit pack, end-to-end orderwire communication in the network can be affected. Additionally, an audio feedback loop can be created diversely routed or ring networks if a manual seam was provisioned at this site. Refer to Provisioning and Operations Procedures, 323-1801-310 for more information.

Note 6: In the OPTera Long Haul 1600 Combiner Rel. 2 NE, since protection is not available for the OC-192/STM-64 T/R and OC-48/STM-16 T/R circuit packs, the severity of this alarm is Critical.



Circuit pack mismatchThis alarm applies to the following circuit packs:







• orderwire (OW)

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


This alarm is raised when a slot is provisioned for a specific circuit pack group, and you insert a different circuit pack into the slot. This alarm is raised when the condition occurs and clears when you install the correct circuit pack in the slot.




Note 1: The "Software transfer fail" alarm can mask the "Circuit pack mismatch" alarm.

Note 2: Upon removal or failure of the shelf controller, DCC and OAM functions are unavailable. No login to the system is possible.




Note 4: Upon failure or removal of the message exchange circuit pack, there is no longer communication between the shelf controller, the maintenance interface, and the port cards. The port cards include the 2.5G WT, 10G WT, OC-192/STM-64 XR, OC-48/STM-16 T/R, OC-192/STM-64 T/R, TDC, and the ESI circuit packs. A missing or failed message exchange circuit pack interrupts data communications functions. Fault reporting, performance monitoring, software upgrade, and circuit pack configuration are unavailable.

Note 5: Upon failure of the primary OPC, the backup OPC (if available) in the network becomes active. The backup OPC takes control of the network elements within its span of control.

Note 6: Upon failure or removal of the orderwire circuit pack, end-to-end orderwire communication in the network can be affected. Additionally, an audio feedback loop can be created in diversely routed or ring networks if a manual seam was provisioned at this site. Refer to Provisioning and Operations Procedures, 323-1801-310 for more information.




Circuit pack missingThis alarm applies to the following circuit packs:







• orderwire (OW)

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


This alarm is raised when a slot is provisioned for a specific circuit pack group that is not equipped in the shelf. This alarm is raised when the condition occurs and clears when you install a circuit pack in the slot.




This alarm raised against the maintenance interface circuit pack masks the following environmental alarms:

• Fan 1/2/3 fail

• Cooling unit 1/2 Fan 1/2/3 fail/missing

• Breaker filter A or B fail

• Breaker filter A or B trip

• High shelf temperature

• Low shelf voltage

• SATT fail



Note 1: Upon removal or failure of the shelf controller, DCC and OAM functions are unavailable. No login to the system is possible.


Note 3: Upon failure or removal of the message exchange circuit pack, there is no longer communication between the shelf controller, the maintenance interface, and the port cards. The port cards include the 2.5G WT, 10G WT, OC-192/STM-64 XR, OC-48/STM-16 T/R, OC-192/STM-64 T/R, TDC, and the ESI circuit packs. A missing or failed message exchange circuit pack interrupts data communication functions. Fault reporting, performance monitoring, software upgrade, and circuit pack configuration are unavailable.

Note 4: Upon failure of the primary OPC, the backup OPC (if available) in the network becomes active. The backup OPC takes control of the network elements within its span of control.

Note 5: Upon failure or removal of the orderwire circuit pack, end-to-end orderwire communication in the network can be affected. Additionally, an audio feedback loop can be created in diversely routed or ring networks if a manual seam was provisioned at this site. Refer to Provisioning and Operations Procedures, 323-1801-310, for more information.


Circuit pack overheatedThis alarm applies to the following circuit packs:

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


A circuit pack overheat raises this alarm. This alarm is raised when the condition occurs and clears when you replace the faulty circuit pack.

Circuit pack provision mismatchThis alarm is raised when the equipped 2.5G WT, 10G WT, OC-192/STM-64 XR, OC-192/STM-64 T/R, OC-48/STM-16 T/R circuit pack does not support the values that are currently provisioned. The alarm is raised when one of the following mismatch states is present:

• Optical power provisioning mismatch



10G WT, OC-192/STM-64 XR, OC-192/STM-64 T/R circuit packs support output optical power provisioning between -10.0 dBm and +1.50 dBm.

2.5G WT circuit pack supports output optical power provisioning between -11.0 dBm and +1.00 dBm.

OC-48/STM-16 T/R circuit pack, “Fixed” is the only valid value.

• Chirp provisioning mismatch

The chirp provisioning mismatch occurs when the slot is provisioned with a chirp value not supported by the equipped circuit pack.

• Wavelength provisioning mismatch

The wavelength provisioning mismatch occurs when the slot is provisioned with a wavelength value that is different from the wavelength of the equipped circuit pack. For example, the alarm is raised if an OC-192/STM-64 T/R 1557 nm circuit pack is equipped while the provisioned wavelength value is 1533 nm.

The “Circuit pack provision mismatch” alarms mask the “Circuit pack fail” alarm.

Circuit pack unseatedThis alarm applies to the following circuit packs:

• OPC storage (POPS), and OPC controller (POPC)

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


This alarm is raised when the latch or latches (as applicable) of a circuit pack are in a release state. This alarm is raised when the condition occurs. This alarm clears when you close the latch or latches (as applicable) on the circuit packs.

Circuit pack vintage mismatchThis alarm applies to the following circuit packs:








• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


This alarm is raised when the vintage of the circuit pack is outside the range of vintage baseline.

Equipment forced switch requestThis alarm applies to the following circuit packs:




A user request for a forced switch for the selected circuit pack raises this alarm. The alarm clears when the user releases the forced switch.

Equipment lockout requestThis alarm applies to the following circuit packs:




A user request for a lockout for the selected active circuit pack raises this alarm. The alarm clears when the user releases the lockout.

Equipment manual switch requestThis alarm applies to the following circuit packs:




A user request for a manual protection switch for the selected circuit pack raises this alarm. The alarm clears immediately after the manual switch is complete.

Intercard failThis alarm applies to the following circuit packs:

• OPC controller (POPC), and OPC interface (POPI)








• orderwire (OW)

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


Any intercard fault raises this alarm. An intercard fault is a failure between circuit packs in different circuit pack groups (G1 or G2). This alarm is raised against the possibly failed circuit pack. This alarm also contains the identity of the circuit pack that terminates the other end of the failed link.

If this alarm is raised against the OPC controller and interface circuit packs, the cause is a communication failure between the OPC controller and interface circuit packs. The failure is possibly due to the following reasons:

• a defective OPC controller or interface circuit pack

• an unseated OPC interface circuit pack

• an OPC is not powered and functional

Note: When the “Intercard fail” alarm is raised against the orderwire circuit pack, end-to-end orderwire communication in the network can be affected.



Loss of power feed A/BThis alarm applies to the following circuit packs:

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

The loss of one of the three 30A input feeds on the breaker filter module A or B raises this alarm. This alarm is raised when the failure occurs and clears when the failure clears. This situation is due to the following reasons:

• a blown fuse on the breaker filter module

• a problem with the power wiring

• an unseated breaker filter module

OH Bus multidrop link failThis alarm applies to the following circuit packs:

• 2.5G WT

• OC-48/STM-16 T/R

The Overhead (OH) bus is constructed by links between the transport circuit packs (OC-48/STM-16 T/R, 2.5 G WT, and DOSC) on the main shelf and the OH bus access circuit packs (orderwire and ESI) on the control shelf. One end of each OH bus link connects to a transport circuit pack. The other end connects to one or more OH bus access circuit packs.

This alarm is raised when the OH bus link fails between the 2.5G WT, OC-48/STM-16 T/R, or DOSC circuit packs and the OH bus access circuit packs on the control shelf.

Software errorThis alarm applies to the following circuit packs:



• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


The occurrence of software trap in the system raises this alarm. This alarm indicates that a software problem exists on the indicated network element. Refer to Nortel Networks technical assistance to clear this alarm using a resident tool.



Note: Upon removal or failure of the shelf controller, data communication channel and operations, administration and maintenance (OAM) functions are unavailable. No login to the system is possible.

Software trapThis alarm applies to the following circuit packs:



• orderwire (OW)

• 2.5G WT

• 10G WT

• OC-192/STM-64 XR

• OC-192/STM-64 T/R

• OC-48/STM-16 T/R


The occurrence of a software trap in the system raises this alarm. This alarm indicates that a software problem exists on the indicated network element. This alarm can be raised on some circuit packs after a brown-out condition. Refer to Nortel Networks technical assistance to capture the “trap” for analysis and clear this alarm using a resident tool.

Tx laser failThis alarm applies to the following circuit packs:

• 2.5G WT

• OC-48/STM-16 T/R

This alarm is raised when a circuit pack on the main shelf has a laser fail. This alarm is raised when the condition occurs and clears when you replace the faulty circuit pack.

Since the OC-48/STM-16 T/R circuit pack occupies a full slot, the alarm raising strategy is as follows:

• A full-height circuit pack is provisioned in the slot, is in service, and either a half-height slot or a full slot contains a wrong circuit pack. The alarm is raised against the full slot.

• A half-height circuit pack is provisioned in the half-height slot and the half-height slot contains a wrong circuit pack. The alarm is raised against the half-height slot.



Common equipment alarmsThe following list contains common equipment alarms.

Common equipment alarm Definition Troubleshooting Procedure 1

1. To troubleshoot this alarm, refer to Trouble Clearing and Module Replacement, 323-1801-543.

Autoprovisioning mismatch page 2-24 Procedure 2-17

Commissioning MI present page 2-24 Procedure 2-18

Duplicate NE name page 2-24 Procedure 2-19

Duplicate NE ID page 2-24 Procedure 2-20

Entry to 20 ppm freerun page 2-25 Procedure 2-21

Exerciser fail / MX Exerciser fail page 2-25 Procedure 2-22

Filler card missing page 2-26 Procedure 2-23

LCAP port intrusion attempt page 2-26 Procedure 2-24

Manual area address dropped page 2-26 Procedure 2-25

MI port intrusion attempt page 2-27 Procedure 2-26

Mismatched switch type page 2-27 Procedure 2-27

NE approval required page 2-27 Procedure 2-28

Network port intrusion attempt page 2-27 Procedure 2-29

Node in reconfiguration mode page 2-27 Procedure 2-30

Node in site-test configuration page 2-28 Procedure 2-31

Number of level 1 NEs exceeded page 2-28 Procedure 2-32

Protection path fail page 2-28 Procedure 2-33

Reconfiguration failed page 2-28 Procedure 2-34

Serial number inconsistency page 2-28 Procedure 2-35

Shelf autoprovisioning mismatch page 2-28 Procedure 2-36

Software transfer fail page 2-29 Procedure 2-37

Unknown software release page 2-29 Procedure 2-38



Autoprovisioning mismatchThe following situations raise this alarm:

• You insert a circuit pack of the wrong type in an unprovisioned shelf slot.

This alarm is raised against the second circuit pack in the above configurations.

This alarm is raised when the condition occurs and clears when you remove the circuit pack or you reprovision the slot.

The “Autoprovisioning mismatch” alarm is raised as follows:

Note: In the following cases listed, the sub-slots are not provisioned.

• The slot supports only full-height circuit packs and either the full slot or the sub-slot contains the wrong circuit pack. One alarm is raised against the full slot.

• The slot supports only half-height circuit packs and the sub-slot contains the wrong circuit pack. One alarm is raised against each sub-slot.

If only one sub-slot is not provisioned and it contains the wrong circuit pack, one alarm is raised against that sub-slot.

Commissioning MI present The shelf controller circuit pack raises this alarm when a commissioning maintenance interface circuit pack is present on a network element already commissioned.

Duplicate NE nameThis alarm is raised when you commission the network element with a mnemonic name that is not unique throughout the network. This problem makes the OPC command nelogin unpredictable, as it is possible that it cannot connect to the correct node.

This alarm is raised against all nodes that have the mnemonic name within the network.

Duplicate NE IDA network element with a non unique network element identification number (NE ID) raises this alarm. A non unique NE ID leads to an unstable association between this node and the OPC.

This alarm is raised against all nodes that have the mnemonic name within the network.



Entry to 20 ppm freerunThe shelf clock source that reverts to SONET/SDH freerun (+ 20 ppm) raises this alarm. If neither of the two ESI circuit packs are operational, then the current shelf clock source enters the freerun mode. The following situations causes this alarm:

• There are no ESI circuit packs inserted in the appropriate slots in the OPTera Long Haul 1600 shelf.

• Both ESI circuits packs fail at the same time.

• One ESI circuit pack failed, and the other ESI circuit pack is not present in the shelf.

Note: This alarm can occur for a time period of two to three minutes after a network element (NE) is powered up. When you power up a network element, it normally enters the freerun mode for the first two or three minutes to permit the ESI clock to stabilize in temperature before the NE starts using the ESI clock source.

Exerciser fail / MX Exerciser failThis alarm is raised when the protection switch exerciser failed while attempting to perform K-byte signaling. The alarm is raised for the following reasons:

• A higher priority switch request or an active loopback.

• An optical loopback on protection.

• Simultaneous running of the exerciser at LTEs at either end of the line.

• Failure of the protection on the receive side of the equipment or line.

• Failure of both the standby and active transmit side of the equipment or line.

If the alarm is raised against the MX circuit pack, this alarm is due to:

• Failure of the standby, active or both MX circuit packs

• Missing the standby (if dual MX is provisioned), active or both MX circuit packs.

If an “Exerciser fail” alarm results from an exerciser run, the alarm remains active until the exerciser runs successfully. In the case of the MX circuit pack, the exerciser is run internally once an hour. The exerciser is run when you insert a circuit pack to re-evaluate the situation.

If this alarm is raised against the MX circuit pack, protection switching can be unavailable. In the event of a failure affecting the working MX circuit pack, there is no communication between the shelf controller, the MI and the port cards. The port cards include tributary interfaces, transmit, receive and demultiplexer interfaces, and the ESI circuit pack. Fault reporting, performance monitoring, software upgrade and circuit pack configuration are unavailable.



Filler card missingThis alarm is raised when a slot on the main shelf is empty and no circuit pack group is created for that slot.

The “Filler card missing” alarm is raised as follows:

Note: In the following cases listed, no circuit pack is provisioned in either sub-slot.

• The slot supports only full-height circuit packs and both sub-slots are empty. The alarm is raised against the full slot.

• The slot supports only half-height circuit packs and both sub-slots are empty. One “Filler card missing” alarm is raised against each sub-slot.

If a full-height circuit pack is provisioned and out-of-service, one alarm is raised against each sub-slot. If a half-height circuit pack is provisioned and out-of-service, one alarm is raised against the sub-slot. All the other alarms are masked.

The ‘Filler card missing’ alarm can also be raised when a provisioned but OOS (FAC and EQP) circuit pack is removed (missing) from the Main Transport or Extension shelves.

The reason for this is as follows:

Provisioned but OOS EQP alarms are masked. In essence, an OOS circuit pack should create no alarms if it is failed, missing or mismatched. However, OC-192 requires proper cooling ventilation due to its high speed/ high density electronics. Fan forced air cooling is used for the Main Transport and Extension shelves.

To ensure the forced air cooling is properly circulating in the bay, OC-192 requires circuit packs (regular circuit packs and filler cards) to be equipped in all slots of the Main Transport and Extension shelves. When you remove an OOS circuit pack in the Main Transport or Extension shelf, the system raises a ‘filler card missing’ alarm to notify this condition which could affect proper cooling.

LCAP port intrusion attemptThis alarm is raised when the system detects an intrusion attempt on the local craft access panel (LCAP) port.

Manual area address droppedThis alarm is raised when a provisioned manual area address is dropped from the computed area address set of the network. Each network element supports a maximum of up to three manual area addresses at one time. All network elements in the network share this information. Each network element



independently calculates a set of computed area addresses from the union of all the manual area addresses provisioned on the network. The computed set is recalculated in the following situations:

• addition of a new network element to the network

• manual deletion or addition of an area address from any network element

• expiration of a local timer (maximum delay: every 10-15 minutes and minimum delay: every few seconds)

This alarm can indicate a network-wide error condition in the provisioning of data communication. If an area address is dropped on an network element, isolation of the network element and a loss of OAM&P capability on the network element can occur.

MI port intrusion attemptThis alarm is raised when the detection of an intrusion attempt on the maintenance interface port occurs.

Mismatched switch typeThis alarm is raised when two Message Exchange (MX) circuit packs present in the OPTera Long Haul 1600 shelf are not the same type. The MX circuit pack handles internal communications between the control circuit packs and the optical circuit packs, and DCC routing. The MX circuit pack also connects the shelf controller to all software-based circuit packs in the OPTera Long Haul 1600 bay through the star-based LAN.

You must install at least one MX circuit pack in the control shelf. It is recommended that you install two MX circuit packs: one to act as the working circuit pack, and the other to act as the protection circuit pack.

NE approval requiredThis alarm is raised when the database is lost and needs to be recreated, and at least one of the traffic carrying circuit packs is still provisioned for the old database.

Network port intrusion attemptThis alarm is raised when the user exceeds the number of allowed login attempts. A login attempt is not successful if either the user identifier or password is invalid.

Network port intrusions indicate unsuccessful login attempts over network connections to the OPC.

Node in reconfiguration modeThis alarm raised as part of system reconfiguration and is for information purposes only.



Node in site-test configurationThis alarm is raised when the user issues a command to put the network element into site-test configuration mode. This alarm indicates that a special configuration of connections is set up between tributary and line facilities in order to facilitate commissioning tests. The site-test verifies all the facilities on the network element before adding the network element to the ring. This alarm is not an alarm indication.

Note: Once you issue the command to put the network element into site-test configuration mode, and the “Node in site-test configuration” alarm is raised, do not perform a configuration audit from the OPC. If you perform a configuration audit, you will need to decommission the network element and then recommission it, in order clear this alarm. For more information to decommission and commission a network element, refer to Powering up and Commissioning Procedures, 323-1801-220.

Number of level 1 NEs exceededThis alarm is raised when the number of network elements supported in the DCC domain exceeds the maximum supported. The maximum number of network elements supported in a FiberWorld network is 150. A FiberWorld network is the collection of the following network elements that connect by way of DCC, Ethernet, or control network (CNet) links: OPC, OC-3, OC3-Express, AccessNode, Radio Node, OC-12, TN16X, OC-48, OC-192, and OPTera Long Haul 1600 network elements.

Protection path failThis alarm is raised when running the protection exerciser resulted in a K-byte failure. It occurs when one or more of the following conditions are present in the received K-bytes:

• Inconsistent K-bytes.

• An invalid, unused or inappropriate K-byte code.

• An invalid or unused channel number.

Reconfiguration failedThis alarm is raised during the system reconfiguration. For more information refer to the appropriate “OC-12/OC-48 Tributary to Quad OC-12 Conversion” change application notice (CAP).

Serial number inconsistencyThis alarm is raised when a hardware fault changed the shelf serial number.

Shelf autoprovisioning mismatchThis alarm is raised when the network element type created is unable to support the installed extension shelf. This alarm clears when the shelf is removed.



Software transfer failThis alarm is raised by the shelf controller circuit pack when software, configuration, upgrades and downloads (SCUD) needs to download a file from the OPC to the network element and is unable to. The problem is due to one or all of the following reasons:

• The file download was successful but the file integrity check fails.

• The requested file is missing on the OPC.

• The specified OPC open system interconnect (OSI) address or directory path is not correct.

• There is a loss of communication between the OPC and the network element.

• The maintenance interface circuit pack is not present or is defective.

Note 1: This alarm clears only when all causes of the alarm clear.

Note 2: The "Software transfer fail" alarm can mask the "Circuit pack mismatch" alarm and other alarms. Masking occurs because some alarms cannot be raised unless the correct software is running on certain circuit packs. It is possible that this can not be the case when the “Software transfer fail” alarm is active.

Unknown software releaseThis alarm is raised when provisioned data is unrecoverable from the shelf controller or maintenance interface circuit packs. This situation occurs if you replace both circuit packs simultaneously. It is possible that in this condition, commands sent by the network element user interface (NE UI) can not work. The system protects traffic by blocking commands from the NE UI when provisioning data is unrecoverable.



External synchronization interface (ESI) equipment alarms The following list contains equipment alarms raised against the ESI circuit pack.

End VCO range This alarm is raised when there is an indication that the timing generation hardware does not have enough room to track the active timing reference signal. The possible causes are the following:

• a degradation of the voltage-controlled oscillator (VCO)

• a degradation of the timing reference signal

• a combination of the causes stated above

This alarm is raised 2.5 seconds after the condition occurs and clears 10 seconds after the condition clears.

Note 1: This alarm is raised when the incoming reference signal is within Stratum 3 specifications. It is possible to disable the alarm when normal operation is from a source less than Stratum 1.

Note 2: If this alarm appears on both ESI circuit packs, the cause is probably an invalid source.

Failure to lockThis alarm is raised to indicate that the ESI circuit pack phase-locked loop (PLL) hardware fails to lock onto any available reference source. The PLL filter becomes stuck in acquire mode for more than 120 seconds, and a reference protection switch to an alternative source is not possible.

When two ESI circuit packs are present, the circuit pack that raises this alarm is probably failed. A faulty source is possible. When a single ESI circuit pack is present, and a single source is available, the cause is either a faulty circuit pack or a faulty source.

External synchronization interface (ESI) equipment alarm

Definition Troubleshooting Procedure 1


End VCO range page 2-30 Procedure 2-36

Failure to lock page 2-30 Procedure 2-37

Timing generation entry to acquire page 2-31 Procedure 2-38

Timing generation entry to freerun page 2-31 Procedure 2-39

Timing generation entry to fast page 2-31 Procedure 2-40

Timing generation entry to holdover page 2-31 Procedure 2-41



Note: This alarm is raised in connection with the ESI “Circuit pack fail” alarm.

Timing generation entry to acquireThe ESI is typically in acquire mode on power up or system reset, until synchronization with the external timing reference is complete. This alarm is raised when the ESI enters acquire mode and clears when the ESI enters fast-acquire mode.

Timing generation entry to freerunThis alarm is raised when the ESI is unable to lock on to an external timing reference. This alarm is also raised if the provisioning of the target filter mode is set to freerun. The voltage-controlled oscillator (VCO) on the circuit pack is set at the midpoint and is providing a Stratum 3 clock. The ESI is typically in freerun mode during installation. This alarm is raised when the condition occurs and clears when the ESI leaves freerun mode.

Timing generation entry to fastThe ESI is in fast-acquire mode. The ESI is attempting to reacquire synchronization and is adjusting to changes with the external timing reference. This alarm is raised when the ESI enters fast mode and clears when the ESI frequency adjusts to the reference input frequency.

Timing generation entry to holdoverThe ESI is in holdover mode as a result of a manual request or as the result of a loss of the reference signal. The holdover mode means that the ESI maintains its synchronization based on the last valid Stratum 3 or better reference signal for 24 hours. After the 24-hour period, the reference reverts to Stratum-3 quality (if the reference quality was better than Stratum 3). If the reference was already Stratum 3, the quality remains Stratum 3.

This alarm is raised when the ESI enters holdover mode and clears when either the primary or the secondary timing frequency problem clears. This alarm clears if you provision the ESI to another valid timing reference input.



OPC equipment alarmsThe following list contains OPC equipment alarms raised against the OPC controller, storage and interface packs.

Backup/Primary: disk 95% fullThis alarm is raised when at least 95% of the space on the Primary OPC hard disk is full or 95% of the space on the Backup OPC hard disk is full. The alarm becomes active when an hourly audit by the OPC detects the problem.

Note: Do not proceed with a software upgrade until you have cleared the alarm.

Backup/Primary: disk bad media detectedThere is a problem on the hard disk of the Primary OPC or Backup OPC. The alarm becomes active when the OPC detects the problem during the weekly audit.

OPC equipment alarm Definition Troubleshooting Procedure 1


Backup/Primary: disk 95% full page 2-32 Procedure 2-42

Backup/Primary: disk bad media detected page 2-32 Procedure 2-43

Backup/Primary: network port intrusion page 2-33 Procedure 2-44

Backup/Primary: serial port intrusion page 2-33 Procedure 2-45

Backup/Primary: TCP/IP Access violation page 2-33 Procedure 2-46

Datasync fail page 2-33 Procedure 2-47

External Ethernet LOS page 2-33 Procedure 2-48

Historical log data lost page 2-33 Procedure 2-49

Internal Ethernet LOS page 2-34 Procedure 2-50

Lost peer OPC page 2-34 Procedure 2-51

OAM software fail page 2-34 Procedure 2-52

OPC alarm(s) active page 2-34 Procedure 2-53

Removable media backup/restore fail page 2-34 Procedure 2-54

Upgrade in progress page 2-35 Procedure 2-55



Backup/Primary: network port intrusionThis alarm indicates that a network port intrusion attempt was detected on the Primary OPC or on the Backup OPC. This alarm is raised when the allowable number of unsuccessful login attempts is exceeded. A login attempt is unsuccessful if either the user identifier or password is invalid.

Network port intrusions indicate unsuccessful login attempts over network connections to the OPC.

Backup/Primary: serial port intrusionThis alarm indicates that a serial port intrusion attempt was detected on the Primary OPC or on the Backup OPC. This alarm is raised when the allowable number of unsuccessful login attempts is exceeded. A login attempt is unsuccessful if either the user identifier or password is invalid.

Serial port intrusions indicate unsuccessful local login attempts.

Backup/Primary: TCP/IP Access violationThe following situations cause this alarm:

• A user on the local host OPC has been denied access to the TCP/IP network by the access control software.

• A user on a remote host has been denied access to the local host OPC by the access control software.

Datasync failThis alarm indicates that an attempt to perform a database backup (datasync) from the primary OPC to the backup OPC failed. The database backup causing the alarm can be a manual backup or a scheduled backup. This alarm is not raised during database backups to SLAT OPCs or other OPCs.

External Ethernet LOSThis alarm is raised when the external Ethernet connection between the OPC and the operations system (OS) or the Network Manager (NM) fails. The possible causes are the following:

• The external cable is faulty.

• The Ethernet cable is disconnected.

• The OPC interface, storage or controller circuit pack failed.

Historical log data lostThis alarm indicates that historical event log data collected by the OPC is lost. The lost logs can include security event logs. It is possible that the log database was removed or tampered with. The OPC automatically creates a new log database.



Internal Ethernet LOSThis alarm is raised when the internal Ethernet connection between the OPC and the shelf controller fails. This situation occurs when there is no connection of the OPC circuit pack interface to the backplane.

Lost peer OPCThis alarm is raised when all the available communication paths between the Primary OPC and the Backup OPC are lost. With Partitioned OPC, there are two communication paths, one over fiber and the other over Ethernet.

Manual shutdown in progressThis alarm is raised when one or more of the following conditions are true:

• the Shutdown button is pressed

• the OPC card latches are open

• the OPC Shutdown tool is invoked

• a UNIX reboot command is invoked

OAM software failThis alarm is raised when the OPC Warm Standby (OWS) process fails on the OPC controller circuit pack.

OPC alarm(s) activeThis alarm indicates that the OPC associated with this pointer alarm has one or more active alarms. The OPC can be either the primary or backup OPC, as provisioned. This alarm becomes active at one designated network element.

The pointer alarm becomes active on the designated network element when an alarm becomes active on the OPC. The alarm clears automatically 30 seconds after all active alarms on the OPC are cleared or when there is an activity switch to the peer OPC.

If the OPC and the network element with the pointer alarm lose data communications association, the pointer alarm cannot become active or clear until you restore the association.

Removable media backup/restore failThe following list provides the problems that can occur when a user tries to backup data, restore data or display removable media contents:

• Problems common to save and restore procedures:

– The removable media drive is in use.

– There is no device file.

– The removable media is not inserted correctly.

– The data on the removable media is corrupted.



• Problems with archiving:

– The archiving operation exceeds the available free disk space.

– The current archiving operation failed because a file name contains an illegal character.

– The current archiving operation failed because some OPC data can not be accessed.

• Problems with restoring:

– The archive on the removable media was created from a software version that is different from the software version installed on this OPC.

– The data is not compatible between different versions of software.

– The OPC data backup on the removable media was created on an OPC that was installed as a different product.

• Data transfer operations:

– The data transfer exceeded its maximum allocated time to complete.

– The data transfer operation cannot be initiated.

– The data transfer operation has failed.

– A data transfer operation is in progress.

• Problems with OPC software:

– The version of OPC software that is running cannot be determined for verification of the removable media.

– The current archives operation failed because an OPC data file could not be accessed.

• Problems finding local OPC name/address:

– The tool is cannot find the name of the local OPC in the commissioning data.

– The local OPC address cannot be determined for verification of the removable media.

• The tool has failed and cannot continue because the contents of the removable media are not known.

• The removable media is damaged.

Upgrade in progressThis alarm is raised when a software upgrade is in progress. The alarm will clear when upgrade is completed.



Shelf equipment alarmsThe following list contains shelf equipment alarms raised against the shelf.

Shelf mismatchThis alarm is raised when the installed extension shelf does not match the extension shelf provisioned. Once the extension shelf provisioned matches the extension shelf installed or the extension shelf is removed, the alarm clears.

Shelf missingThis alarm is raised when the extension shelf is provisioned and then removed from the system without proper de-provisioning. This alarm is also raised when the extension shelf is provisioned but there is no extension shelf physically present.

Orderwire equipment alarmsThe following list contains orderwire equipment alarms.

Auto orderwire seam activeThis alarm is raised on a network element where an orderwire automatic seam is present. The automatic seam is present because an orderwire signalling network failure is detected on the local node. Even though the failure is detected on the local node, It is possible that the actual failure have occurred at the upstream node (usually the neighbour nodes).

This alarm can be raised when one of the following alarms is raised against an orderwire circuit pack at the local or upstream node:

• Circuit pack fail

• Circuit pack mismatch

Shelf equipment alarm Definition Troubleshooting Procedure 1


Shelf mismatch page 2-36 Procedure 2-56

Shelf missing page 2-36 Procedure 2-57

Orderwire equipment alarm Definition Troubleshooting Procedure 1


Auto orderwire seam active page 2-36 Procedure 2-58

Manual orderwire seam active page 2-37 Procedure 2-59



• Circuit pack missing

• Intercard fail

• Software trap

To clear these alarms, refer to the appropriate procedures in Trouble Clearing and Module Replacement, 323-1801-543.

This alarm can also be raised if the following occurs:

• an orderwire circuit pack is put out-of-service, or is deleted at the upstream node

• there are equipment or facility alarms related to MOR circuit packs.

Note: For DWDM system applications from 2 to 32 wavelengths, refer to the OC-192 Optical Layer Applications Implementation documentation suite (NTCA66BA). Until this documentation suite is available, refer to the Optical Networks Applications documentation suite, Issue 8.0 (NTCA66AE) for DWDM system applications that support from 2 to 16 wavelengths.

This alarm clears when the automatic orderwire seam condition clears.

Manual orderwire seam activeThis alarm is raised when the user issues a showmanseam command. The alarm is raised on all the network elements that have a manual orderwire seam enabled, and are part of the orderwire signalling network. For more information on orderwire seam provisioning, refer to Provisioning and Operations Procedures, 323-1801-310.

To mask the “Manual orderwire seam active” alarm, log into one of the network elements that is part of the orderwire signalling network, and issue the hidemanseam command. The alarm clears on all the network elements of the orderwire signalling network.

If a “Manual orderwire seam active” alarm does not clear on a network element when you issue the hidemanseam command, this can indicate segmentation of the orderwire signalling network. To clear the alarm, issue the hidemanseam command on at least one network element in each segment.

Clearing the “Manual orderwire seam active” alarm does not remove any manual orderwire seams provisioned on the network. To deprovision a manual orderwire seam, refer to Provisioning and Operations Procedures, 323-1801-310.



Facility alarmsFacility alarms that are raised against several facility types are grouped in the generic facility alarm category. Alarms that are raised against a specific facility type follow.

Generic facility alarmsThe following list contains facility alarms raised against several facility types.

Generic facility alarm Definition Troubleshooting Procedure 1


Channel ID mismatch page 2-39 Procedure 3-1

Degraded clock carrier page 2-39 Procedure 3-2

Far end protection line fail page 2-40 Procedure 3-3

FEC provisioning mismatch page 2-40 Procedure 3-4

Line AIS page 2-40 Procedure 3-5

Line RFI / MS RDI page 2-40 Procedure 3-6

Max. number of NE exceeded page 2-41 Procedure 3-7

MI ethernet loss of signal page 2-41 Procedure 3-8

Path AIS page 2-41 Procedure 3-9

Payload fail page 2-41 Procedure 3-10

Section Rx loss of frame / loss of frame (STMn facility)

page 2-42 Procedure 3-11

Section Rx loss of signal / loss of signal (STMn facility)


Section trace mismatch page 2-43 Procedure 3-13

Signal degrade / MS signal degrade page 2-43 Procedure 3-14

Signal fail / MS excessive BER page 2-44 Procedure 3-15

SONET SDCC/LDCC link fail / RS/ MS DCC fail page 2-45 Procedure 3-16



Channel ID mismatchThis alarm applies to the following facility types:

• OC-192/STM-64 facility


This alarm is raised when the channel identifier (ID) received over the working channel is different from the channel ID provided for the circuit pack. This occurs if you do not provision the circuit packs properly or the fiber connections have become crossed.

This alarm can also be raised if the OC-48/STM-16 T/R tributaries on an OPTera Long Haul 1600 Combiner shelf connect to OC-192/STM-64 T/R circuit packs not manufactured by Nortel Networks. The alarm is raised when the software in the vendor’s equipment is not compatible with Nortel Networks equipment.

The “Line RFI” alarm masks the “Channel ID mismatch” alarm when the OC-48/STM-16 T/R tributaries on a OPTera Long Haul 1600 Combiner shelf connect to OC-192/STM-64 T/R circuit packs not manufactured by Nortel Networks. This alarm is raised when the condition occurs and clears after the condition clears.

Degraded clock carrierThis alarm applies to the following facility types:



• external synchronization interface (ESI) facility

This alarm is raised when the ESI is unable to synchronize to the associated timing reference. This alarm indicates one of the following problems with the associated timing reference:

• The reference frequency is outside of the Stratum 3 range.

• There is excessive wander or jitter on the associated reference; the ESI PLL filters are stuck in acquire mode for more than 120 seconds.

Problems at an upstream node, including entry to SONET freerun cause this alarm.

This alarm is masked by the ESI “Loss of signal”, “Tx AIS”, “Loss of frame”, and “Signal degrade” alarms.



Far end protection line failThis alarm applies to the following facility types:



This alarm is raised to indicate that the K-bytes received a protection line signal failure.

FEC provisioning mismatchThis alarm applies to the OC-192/STM-64 facilities only.

This alarm is raised when the forward error correction (FEC) provisioning is enabled on the network element at one end of the section or line and disabled at the other end. This alarm is raised when the provisioning of FEC is enabled, but the supporting hardware does not have FEC capability.

Note: This alarm is raised at the receive end of the transmission, and only when the receive-end FEC provisioning is enabled.

Line AISThis alarm applies to the following facility types:




This alarm is raised by problems upstream of the network element resulting in this network element receiving a line alarm indication signal (AIS). The problems can be loss of signal (LOS) or loss of frame (LOF) at upstream equipment.

The Line AIS alarm can also be raised when a tributary facility of an upstream network element is put in the out of service state (OOS).

Line RFI / MS RDIThe Line remote failure indication (RFI) alarm is raised when the far end network element detects a problem on its receive optical signal.

The “Line RFI” alarm masks the “Channel ID mismatch” alarm when the OC-12, STS-48, or OC-48 tributaries on an OC-192 shelf connect to OC-12, STS-48, or OC-48 circuit packs not manufactured by Nortel Networks. This alarm is raised when the condition occurs and clears after the condition clears.



Max. number of NE exceededThis alarm applies to the external comms facility.

This alarm is raised when the maximum number of network elements supported in the DCC domain has been exceeded. The maximum number of network elements supported in a FiberWorld network is 150. A FiberWorld network is the collection of the following network elements that connect by way of DCC, Ethernet or CNet links: OPC, OC-3, OC3-Express, AccessNode, Radio Node, OC-12, TN16X, OC-48, OC-192, and OPTera Long Haul 1600 network elements.

Note: If you pull and re-insert the maintenance interface (MI) circuit pack, this alarm can be raised temporarily. Once the MI circuit pack is in running state, the “Max. number of NE exceeded” alarm clears.

MI ethernet loss of signalThis alarm applies to the remote layer management (RLM) facility.

This alarm is raised when the Ethernet connection between the OPTera Long Haul 1600 network element and other network elements fails. This problem is due to one of the following reasons:

• The Ethernet cable is faulty.

• The Ethernet cable is disconnected.

• The cable is connected to an Ethernet port that is out of service.

• The maintenance interface at the local or remote end failed.

Since the conditions causing the alarm are transient, allow one minute after the alarm is raised before replacing equipment.

Path AISThis alarm applies to OC-48/STM-16 facility

This alarm is raised when the payload is receiving Path AIS (alarm indication signal) due to path problems being experienced upstream of the NE. This alarm can also be caused by an active loopback at an upstream terminal.

Payload failThis alarm applies to the following facility types:



This alarm is raised to indicate a failure on the path on a single or multiple STS-1 within a facility.



Section Rx loss of frame / loss of frame (STMn facility)This alarm applies to the following facility types:



This alarm is raised when the OC-192/STM-64, or OC-48/STM-16 receive interface is unable to lock on the frame of the incoming (received) optical signal. This condition occurs for one of the following reasons:

• There is a defective upstream transmitter.

• The upstream transmitter or multiwavelength optical repeater (MOR Plus) circuit packs are incorrectly provisioned (if applicable).

• The MOR Plus configuration is incorrect at the tail end of the link (if applicable).

• The OC-192/STM-64 transmitter of the circuit pack is the wrong type (positive or negative chirp or incorrect wavelength).

• The receiver of the circuit pack is defective.

• There is degradation of a fiber connection.

• The optical patchcord suffered some damage.

• The received optical power is low.

• The optical fiber connector is dirty at the receiver of the circuit pack or at the launching transmitter.

• The miniature variable optical attenuator (mVOA) on the patchcord is malfunctioning.

This alarm is masked by the “Sect. Rx loss of signal” alarm. This alarm is raised 2.5 seconds after the condition occurs and clears 10 seconds after the condition clears.

Section Rx loss of signal / loss of signal (STMn facility)This alarm applies to the following facility types:



This alarm is raised when the OC-192/STM-64, OC-48/STM-16 receive interface is unable to lock on the frame of the incoming (received) optical signal. This condition occurs for one of the following reasons:












• The mVOA on the patchcord is malfunctioning.

This alarm masks the “Sect. Rx loss of frame” alarm. This alarm is raised 2.5 seconds after the condition occurs and clears 10 seconds after the condition clears.

Section trace mismatchThis alarm applies to the following facility types:



Section trace monitors STS-1 sections of traffic. This alarm is raised when the actual section trace value received by this facility is different from the provisioned expected value. This problem is due to the following reasons:

• an incorrectly provisioned expected section trace value

• an incorrectly connected fiber

• a defective transmitter or demultiplexerSignal degrade / MS signal degradeThis alarm applies to the following facility types:



• ESI

This alarm is raised when the number of errors (error rate) on the incoming receive line exceeds the user-provisioned signal degrade (SD) threshold.

If the faulty facility is the ESI, the identified timing reference input signal feeding the ESI has a line condition problem causing timing problems.



If this alarm is raised against the OC-192/STM-64, or OC-48/STM-16 facilities, the problem is due to one of the following reasons:











This alarm is masked by the “Loss of signal”, “Signal fail” and “Loss of frame” alarms. This alarm raises when the received bit error rate (BER) exceeds the user provisioned SD threshold. The alarm clears when the integration period for that specific SD-provisioned level clears after the condition is cleared. The integration period is dependent of the tributary rate as well as the signal degrade threshold, as described in Bellcore GR-253 standard.

Signal fail / MS excessive BERThis alarm applies to the following facility types:



This alarm is raised when the line BIP-8 errors (parity errors, Line CVs) on the incoming line exceed the Line BIP-8 signal fail threshold of 10E-4. This situation is due to one of the following:













This alarm is masked by the “Loss of signal”, “Loss of frame”, and “Tx AIS” alarms. This alarm is raised 2.5 seconds after the condition occurs and clears 10 seconds after the condition clears.

SONET SDCC/LDCC link fail / RS/ MS DCC failThe “SONET SDCC link fail” alarm applies to the following facility types:



The “SONET LDCC link fail” alarm applies to the following facility types:



This alarm is raised when the shelf controller is unable to communicate over the SONET section data communication channel (SDCC) or the line data communication channel (LDCC) link. This situation is the result of one or more of the following:

• a failed OC-48/STM-16 tributary circuit pack

• a crossed fiber between channels (single or double crossing)

• a remote system has the SDCC or LDCC disabled or not supported

• a remote system with SDCC out of service

• a failed transmitter of the circuit pack

• a failed receiver of the circuit pack

• a failed regenerator of the circuit pack (if applicable, for example, the OC-192/STM-64 XR)

• a failed or missing demultiplexer circuit pack

• a defective or missing far end shelf controller circuit pack or shelf processor



This alarm is raised when the data communications path fails and clears when the condition clears.

Note 1: A data communications failure in one direction can appear in the opposite direction at an OPTera Long Haul 1600 Repeater.

Note 2: The OC-48/TN-16X TransportNode supports SDCC only. Put the LDCC out of service on the tributary within the OPTera Long Haul 1600 Combiner network element if they interconnect to an OC-48/TN-16X network element. When you put the LDCC out of service on the tributary within the OPTera Long Haul 1600 Combiner network element, the LDCC link fail alarm is not raised on the tributary.

Note 3: This alarm can appear briefly when the data communication path is being established (for example, when SDCC is put into service), and should be considered normal operations.



External synchronization interface (ESI) facility alarmsThe following list contains alarms raised against the ESI facility.

Loss of frame / loss of frame (ESI facility)This alarm is raised when the frame is not detected on the timing reference coming into the equipment. This alarm is raised 2.5 seconds after the condition occurs and clears 10 seconds after the condition clears. This alarm is masked by the ESI “Loss of signal” and “Tx AIS” facility alarms and the ESI “Circuit pack fail” equipment alarm.

Loss of signal / loss of signal (ESI facility)This alarm is raised when a signal is not detected on the timing reference coming into the equipment. This alarm is raised 2.5 seconds after the condition occurs and clears ten seconds after the condition clears.

This alarm is masked by the ESI equipment “Circuit pack fail” alarm.

Tx AISThis alarm is raised when the combination of user requests and automatic switch requests does not allow selection of a reference for timing distribution. The transmitted alarm indication signal (AIS) indicates that no usable signal is available. This alarm is raised 2.5 seconds after the condition occurs and clears 10 seconds after the condition clears.

This alarm is masked by the ESI “Loss of signal” alarm.

External synchronization interface (ESI) facility alarm



Loss of frame / loss of frame (ESI facility) page 2-47 Procedure 3-17

Loss of signal / loss of signal (ESI facility) page 2-47 Procedure 3-18

Tx AIS page 2-47 Procedure 3-19



Performance monitoring facility alarmsThe following list contains performance monitoring (PM) facility alarms.

PM 1 minute line/section threshold / PM 1 minute MS/RS thresholdThis performance monitoring (PM) group alarm is raised to indicate the occurrence of a reported PM threshold crossing alert. This alarm is generated at the first occurrence of any line or section threshold crossing alert for the current one minute time period. The alarm is not generated more than once within a one minute time period. This alarm automatically clears at the expiration of the one minute time period. This alarm is due to the following:

• a defective upstream transmitter (2.5G WT, 10G WT, OC-48/STM-16 T/R, OC-192/STM-64 XR, OC-192/STM-64 T/R, MOR Plus circuit pack)

• incorrectly provisioned MOR Plus or transmitting circuit packs

• a wrong type (positive or negative chirp or incorrect wavelength) of OC-192/STM-64 transmitter of the circuit pack

• a defective receiver of the circuit pack

• an optical signal degradation

• a bent fiber

• a defective circuit pack

• a dirty optical connector

• an incorrectly set mVOA

• a wrong dispersion-compensating module (DCM) type for link engineering

• a DWDM coupler incorrectly configured at the receiving end

• a DWDM coupler damaged at the receiving or transmitting end

• an incorrect MOR Plus configuration at the tail end of the link

• exceeded system polarization mode dispersion (PMD) specifications

Performance monitoring facility alarm Definition Troubleshooting Procedure 1






PM day line/section threshold / PM day MS/RS threshold


PM physical TCA page 2-50 Procedure 3-23



• an out of service line with no optical/AIS signal

Note: The user can remove this alarm by changing the status from reported to not reported using the NE UI.

PM 15 minute line/section threshold / PM 15 minute MS/RS thresholdThis performance monitoring (PM) group alarm is raised to indicate the occurrence of a reported PM threshold crossing alert. This alarm is generated at the first occurrence of any line or section threshold crossing alert for the current 15 minute time period. The alarm is not generated more than once within a 15 minute time period. This alarm automatically clears at the expiration of the 15 minute time period. This alarm is due to the following reasons:


• incorrectly provisioned MOR Plus or transmitting circuit packs




• a bent fiber




• a wrong dispersion-compensating module (DCM) type for link engineering




• exceeded system polarization mode dispersion (PMD) specifications





PM day line/section threshold / PM day MS/RS thresholdThis performance monitoring (PM) group alarm is raised to indicate the occurrence of a reported PM threshold crossing alert. This alarm is generated at the first occurrence of any line or section threshold crossing alert for the current day time period. The alarm is not generated more than once within a day time period. This alarm automatically clears at the expiration of the day time period. This alarm is due to the following:


• incorrectly provisioned MOR Plus or transmitting circuit packs.




• a bent fiber




• a wrong DCM type for link engineering




• exceeded system PMD specifications



PM physical TCAThis performance monitoring group alarm is raised to indicate the occurrence of a reported PM threshold crossing alert. This alarm is generated at the first occurrence of any physical threshold crossing alert. The alarm will be active until all physical threshold crossing are cleared. The alarm will not be generated more than once regardless of the number of currently active physical threshold crossing.

The purpose of the alarm is to direct the users attention to the alert reporting mechanisms, the event browser on the OPC or the log system on the NE, to see what physical threshold crossing alerts have been generated and to take maintenance action to resolve the causes of the threshold crossings. This alarm will automatically clear when all existing physical threshold crossings clear.



OC-192 4-Fiber BLSR/STM-64 MS-SPRing facility alarmsThe following list contains OC-192 4-Fiber BLSR/STM-64 MS-SPRing facility alarms.

Default K-bytesThis alarm is raised to indicate that the neighboring node transmitted the default APS code. The default APS indicates the sourcing node is incapable of proper APS signalling. Protection switching in accordance with the present state of the ring is not possible.

This alarm is raised during the conversion from a linear terminal system to a 4-Fiber BLSR system in a SONET facility or a 4-Fiber MS-SPRing system in an SDH facility. On initiation, the set4Fring command performs validations and initiates a restart. After the recovery, the user can issue a query command to determine the outcome of the configuration. If the configuration was successful, the “Default K-bytes” and the “Node in reconfiguration mode” alarms are raised. This alarm clears when the node receives a node map from the OPC. The ring node map defines network element neighbor relationships. The ring node map provides a list of node (APS) IDs ordered according to the physical interconnections of the nodes in the 4-Fiber BLSR system in a SONET facility or a 4-Fiber MS-SPRing system in an SDH facility.

Invalid K-bytesThis alarm is raised to indicate that the received code in the APS channel is:

• an inconsistent APS code

• an improper APS codeInvalid neighbour detectedThis alarm is raised when the received K-bytes indicate a sourcing network element not corresponding to a neighboring node.

This alarm is a transitory alarm raised during the network element conversion from a linear terminal system to a 4-Fiber BLSR system in a SONET facility or a 4-Fiber MS-SPRing system in an SDH facility. On initiation, the set4Fring command performs validations and initiates a restart. After the recovery, the user can issue a query command to determine the outcome of the configuration. If the configuration was successful, an “Invalid neighbor

OC-192 4-Fiber BLSR/STM-64 MS SPRing facility alarm



Default K-bytes page 2-51 Procedure 3-24

Invalid K-bytes page 2-51 Procedure 3-25

Invalid neighbour detected page 2-51 Procedure 3-26



detected” alarm is raised on the first node to receive a node map. This alarm clears when the second node receives a node map. The ring node map defines network element neighbor relationships. The ring node map provides a list of node (APS) IDs ordered according to the physical interconnections of the nodes in the 4-Fiber BLSR system in a SONET facility, or a 4-Fiber MS-SPRing system in an SDH facility.

Environmental alarms Environmental alarms are used to monitor the environmental conditions of the network element, and external customer inputs. The environmental alarms are grouped in two categories: common equipment and parallel telemetry.

Common equipment environmental alarmsThe following environmental alarms are raised against the common equipment.

Breaker filter A/B failThis alarm is raised when the breaker filters A or B fail. This alarm can also be raised when a low shelf voltage is present.The alarm is raised when the condition occurs and clears when you replace the failed breaker.

This alarm is masked by the maintenance interface “Circuit pack fail” and “Circuit pack missing” alarms. This alarm is masked when the maintenance interface alarms are active, even if the user disabled the maintenance interface alarms.

Common equipment environmental alarm Definition Troubleshooting Procedure 1


Breaker filter A/B fail page 2-52 Procedure 4-1

Breaker filter A/B missing page 2-53 Procedure 4-2

Breaker filter A/B tripped / Breaker filter A/B trip page 2-53 Procedure 4-3

Cooling unit 1/2, fan 1/2/3 fail/missing page 2-53 Procedure 4-3

Fan 1/2/3 fail page 2-53 Procedure 4-5

Fan 1/2/3 missing page 2-54 Procedure 4-6

High shelf temperature page 2-54 Procedure 4-7

Low shelf voltage page 2-54 Procedure 4-8

SATT fail page 2-55 Procedure 4-9

48 V battery A B CE supply fail page 2-55 Procedure 4-10

48 V battery A B CE supply low page 2-55 Procedure 4-11



This alarm is also masked by the “48V battery A/B CE supply fail” and “48V battery A/B CE supply low” alarms.

Breaker filter A/B missingThis alarm is raised when either the breaker filter module A or B is not equipped in the control shelf. The alarm is raised when the condition occurs and clears when you insert the breaker filter module.


Breaker filter A/B tripped / Breaker filter A/B tripThis alarm is raised when either the breaker filter module A or B is not equipped in the control shelf. The alarm is raised when the condition occurs and clears when you replace the tripped breaker.


Cooling unit 1/2, fan 1/2/3 fail/missingThis alarm is raised when one of the three fan units on a shelf fails. This alarm is raised when the condition occurs, and clears when you replace the failed or missing fan.


Note: This alarm is raised only on OPTera Long Haul 1600 bays in the Combiner configuration.

Fan 1/2/3 failThis alarm is raised when one of the three fan units fails. This alarm is raised when the condition occurs and clears when you replace the failed fan.




Fan 1/2/3 missingThis alarm is raised when one of the three fan units on a shelf is missing or is removed from the shelf. This alarm is raised when the condition occurs and clears when you replace the missing fan.


High shelf temperatureThis alarm is raised when the shelf temperature detectors indicate an internal shelf temperature of over 70o C (158o F) for one of the following reasons:

• A fan module is defective.

• The central office temperature is too high.

• There is a problem with circuit packs in the shelf.

This alarm is raised when the condition occurs and clears when the temperature falls below 70o C (158o F) for one minute.


Low shelf voltageThis alarm is raised when the shelf controller detects that the voltage supply to all cards equipping the shelf is below the threshold level of -41.5 Vdc. The network element raises this alarm to inform the user of the dropping voltage, and to provide an early warning of potential system failure. This situation occurs in the following cases:

• There is degradation of the performance of both batteries A and B.

• There is degradation of the performance of one battery and the other is unused.

This alarm is raised when the condition occurs and clears when the voltage returns to the normal operating range.

This alarm is masked by the “Breaker filter A/B fail” and the maintenance interface “Circuit pack fail” and “Circuit pack missing” alarms. This alarm is masked when the maintenance interface alarms are active, even if the user disabled the maintenance interface alarms.



SATT failThis alarm is raised when the synchronization, alarms, and telemetry termination (SATT) module fails. The alarm is raised when the condition occurs and clears when the condition is not present.


48 V battery A B CE supply failThis alarm is raised when the -48 Vdc power supply source for the shelf (battery A or B) fails. This alarm is raised when the failure occurs and clears when the condition is not present.

48 V battery A B CE supply lowThis alarm is raised when the -48 Vdc power supply source for the shelf (battery A or B) is below the voltage threshold of -41.5 Vdc. If there is degradation of the performance of both 48V battery A and battery B, the “Low shelf voltage” alarm appears. This alarm is raised when the condition occurs and clears when the condition is not present.

Parallel telemetry environmental alarmsThe following list contains environmental alarms raised against the parallel telemetry circuit pack.

Telemetry input (1 to 32)This alarm is raised when one of the 32-input pins becomes grounded. An open door, power failure, fire, or other alarms can trigger this alarm.

This alarm is masked by the parallel telemetry “Circuit pack fail” alarm. The alarm clears when the latch returns to its normal state or upon removal of the parallel telemetry circuit pack or when the circuit pack group is out of service. Upon re-insertion of the parallel telemetry circuit pack or when the circuit pack group is back in service, the alarms are raised again if the latch is not in its normal state.

Parallel telemetry environmental alarm Definition Troubleshooting Procedure 1


Telemetry input (1 to 32) page 2-55 Procedure 4-12

Telemetry output page 2-56 Procedure 4-13



Telemetry outputThis alarm is raised when one of the 8-output latches becomes active to start operation of external equipment (for example, a fan or an audible alarm).

These alarms are masked by the parallel telemetry “Circuit pack mismatch” alarm. The alarms are raised when an output point is active and clear when the latch returns to its normal state. These alarms clear upon removal of the parallel telemetry circuit pack or when the circuit pack group is out of service. Upon reinsertion of the parallel telemetry circuit pack or when the circuit pack group is back in service, the alarms are raised again based on the current state of the latches.

Alerts Alerts are event reports usually not requiring any direct action from the craftsperson. Alerts that are raised against several circuit packs are grouped in the generic alert category. Alerts that are raised against a specific circuit pack type or facility follow.

Generic alertsThe following list contains alerts raised against several circuit pack types.

Equipment protection switch completeThis alert applies to the following circuit packs:

• ESI

• message exchange

• timing distribution card

This alert is raised when a switch from the active circuit pack to the standby circuit pack is successful. For automatic protection switches, the alert clears when the cause of the automatic protection switch clears. For forced switches

Generic alerts Definition Troubleshooting Procedure 1


Equipment protection switch complete page 2-56 Procedure 5-1

Equipment protection switch fail page 2-57 Procedure 5-2

Reference switch complete page 2-57 Procedure 5-3

Reference switch fail page 2-57 Procedure 5-4

Timing generation entry to normal / timing generation to normal




and lockouts, the alert clears when the forced switch or lockout is released. For manual switches, the alert clears immediately after the manual switch is complete.

Equipment protection switch failThis alert applies to the following circuit packs:

• ESI

• message exchange

• timing distribution card

This alert is raised when a protection switch from the active circuit pack to the standby circuit pack is unsuccessful. This alert is raised when a requested protection switch fails. This alert clears when you drop the protection request or when a successful protection switch is complete.

Reference switch completeThis alert applies to the timing generation (TG) protection group members.

This alert is generated when there is a protection switch from one synchronization timing reference source to another. The reference source indicated is the one the system switched to.

Reference switch failThis alert applies to the timing generation (TG) protection group members

This alert is generated when a requested protection switch from one synchronization reference to another fails.

Timing generation entry to normal / timing generation to normalThis alert is raised against the ESI. This alert is raised when the ESI unit is locking on the reference signal.



Performance monitoring alertsThe following list contains alerts raised by performance monitoring (PM).

LBC threshold 1/2This alert is raised when the Laser Bias Current value measured on the Transmit Circuit pack has crossed the TCA threshold.

Line/Section Rx CV threshold 1/2 / MS/RS Rx CV threshold 1/2This alert is raised when the number of line, section, or path receive code violations (CV) exceeds the limit set by either the threshold 1 or threshold 2 value.

Line/Section Rx ES threshold 1/2 / MS/RS Rx ES threshold 1/2This alert is raised when the number of line, section, or path termination errored seconds (ES) exceeds the limit set by either the threshold 1 or threshold 2 value.

Line Rx FEC threshold 1/2 / MS Rx FEC threshold 1/2This alert is raised when the number of line receive forward error correction (FEC) exceeds the limit set by either the threshold 1 or threshold 2 value.

Line/Section Rx SES threshold 1/2 / MS/RS Rx SES threshold 1/2This alert is raised when the number of line, section, or path termination severely errored seconds (SES) exceeds the limit set by either the threshold 1 or threshold 2 value.

Performance monitoring alerts Definition Troubleshooting Procedure 1


LBC threshold 1/2 page 2-58 Procedure 5-6

Line/Section Rx CV threshold 1/2 / MS/RS Rx CV threshold 1/2


Line/Section Rx ES threshold 1/2 / MS/RS Rx ES threshold 1/2


Line Rx FEC threshold 1/2 / MS Rx FEC threshold 1/2


Line/Section Rx SES threshold 1/2 / MS/RS Rx SES threshold 1/2


Line Rx UAS threshold 1/2 / MS Rx UAS threshold 1/2


Section Rx SEFS threshold 1/2 / RS Rx SEFS threshold 1/2




Line Rx UAS threshold 1/2 / MS Rx UAS threshold 1/2This alert is raised when the number of line or path receive unavailable seconds (UAS) exceeds the limit set by either the threshold 1 or threshold 2 value.

Section Rx SEFS threshold 1/2 / RS Rx SEFS threshold 1/2This alert is raised when the number of section receive severely errored frame seconds (SEFS) exceeds the limit set by either the threshold 1 or threshold 2 value.



Nortel Networks

OPTera Long Haul 1600 Optical Line System Alarm Reference Guide

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-542 Rel 3 Standard July 2000Printed in Canada and in the United Kingdom

Documents

LH 1600 Alarm Reference Guide