Alarm Handling Ma268 b1 PDF

Technical Documentation
Product family Tellabs® 6300 Managed

Transport System
Product name Tellabs® 6300 Network Manager
Title Working in Tellabs 6300 Manager Vol. 3:

Handling Alarms
Document User’s Manual

MA268 / Revision B1
Copyright © 2005 Tellabs. All rights reserved.

Tellabs® 6300 Network Manager Legal Notices
Working in Tellabs 6300 Manager Vol. 3: Handling
Alarms
Legal Notices
Copyright Statement This Tellabs manual is owned by Tellabs or its licensors and protected by U.S.
and international copyright laws, conventions, and treaties. Your right to use
this manual is subject to limitations and restrictions imposed by applicable li-
censes and copyright laws. Unauthorized reproduction, modification, distri-
bution, display or other use of this manual may result in criminal and civil
penalties.
Trademark Notice The following trademarks and service marks are owned by Tellabs Opera-
tions, Inc., or its affiliates in the United States and/or other countries: AUDIO
PLUS®, CABLESPAN®, CEC-128™, DYNAMIC SIGNAL TRANSFER™,
DXX®, DXX logo®, EC DUO®, ENHANCED AUDIO PLUS®, EX-
PRESS/PATH®, FOCUS™, MARTIS®, MARTISDXX®, MARTIS logo®, MAR-
TISDXX logo®, METROVANTAGE®, METROWATCH™, NETREACH®,
NETWISE®, SCULPTURED SOUND™, TELLABS®, TELLABS and T sym-
bol®, T symbol, TELLABS PROPARTNER™, TEL/MAP™, TEL/MOR®, THE
WORLD COMMUNICATES THROUGH TELLABS™, TITAN®, VERITY™,
YOUR NETWORKING PARTNER®.
Any other company or product names may be trademarks of their respective
companies.
2 MA268 • Rev. B1
Tellabs® 6300 Network Manager Revision Information
Alarms
Revision Information
Revision history This manual has changed as follows:
Rev. Date Description of Changes
A1 Oct. 15, 2002 First revision
B1 Dec. 19, 2005 The following changes have been made from A1:
• All information about handling alarms has been
updated to describe the TeMIP Client V5.1 for
Windows
• The list of alarms has been updated
MA268 • Rev. B1 3
Tellabs® 6300 Network Manager Revision Information
Alarms
4 MA268 • Rev. B1
Tellabs® 6300 Network Manager Contents
Alarms
Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Part I: Overview of Alarm Handling

1 Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 The Principles of Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Alarm Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Alarm Entities and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.1 Alarm Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.1 The Operation Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.2 The Alarm Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2 Attributes for Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2.1 The Event Time Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.2 The Main_Object Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.3 The Detailed_Object Attribute . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.4 The Alarm_Text Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.5 The Perceived Severity Attribute . . . . . . . . . . . . . . . . . . . . . . 25
2.2.6 The Probable Cause Attribute . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.7 The State Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.8 The Clearance Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.9 The Pseudo Alarm Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.10 The Correlated Notifications Attribute . . . . . . . . . . . . . . . . . . . 26
3 Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1 Alarms View Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Part II: Work Procedures

4 Defining the Alarm Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.1 Operation Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.1.1 Creating Operation Contexts in a Domain . . . . . . . . . . . . . . . 35
4.1.2 Managing Operation Contexts . . . . . . . . . . . . . . . . . . . . . . . . 36
4.1.3 Deleting Operation Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.1.4 Specifying Accumulation of Similar Alarms . . . . . . . . . . . . . . 42
5 Supervising Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1 Setting Up Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.1 Opening the Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.2 Specifying Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1.3 Setting Up Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2 Inspecting and Handling Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2.1 An Overview of the Process for Handling Alarms . . . . . . . . . . 51
5.2.2 Acknowledging Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.2.3 Locating the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.2.4 Attaching a Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.2.5 Terminating Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2.6 Automatic Clearance and Matching . . . . . . . . . . . . . . . . . . . . 55
5.3 Using the History View to View the Alarm Log . . . . . . . . . . . . . . . . . . . 56
5.3.1 Opening the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.3.2 Searching in the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3.3 Purging Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
MA268 • Rev. B1 5
Tellabs® 6300 Network Manager Contents
Alarms
Part III: Reference Information

6 Operation Context and Alarm Attributes . . . . . . . . . . . . . . . . . . . . . 65
6.1 Operation Context Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.1.1 Attributes for Registration of Operation Contexts . . . . . . . . . . 65
6.1.2 Identifiers Attributes for Operation Contexts . . . . . . . . . . . . . . 71
6.1.3 Characteristics Attributes for Operation Contexts . . . . . . . . . . 71
6.1.4 Status Attributes for Operation Contexts . . . . . . . . . . . . . . . . 75
6.1.5 Counters Attributes for Operation Contexts . . . . . . . . . . . . . . 80
6.1.6 Routing Attributes for Operation Contexts . . . . . . . . . . . . . . . 80
6.2 Alarm Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.2.1 Identifiers Attributes for Alarm Objects . . . . . . . . . . . . . . . . . . 81
6.2.2 Characteristics Attributes for Alarm Objects . . . . . . . . . . . . . . 81
6.2.3 Status Attributes for Alarm Objects . . . . . . . . . . . . . . . . . . . . . 86
6.2.4 Counters Attributes for Alarm Objects . . . . . . . . . . . . . . . . . . 88
7 Alarm Rule Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.1 Attributes for Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2 Identifiers Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.3 Characteristics Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.4 Status Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.5 Counters Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8 Alarm Rules for System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 103

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.2 Computer Hardware Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.2.1 Alarm Rules for SNMP Entities . . . . . . . . . . . . . . . . . . . . . . . 103
8.2.2 Alarm Rules for Bridge LAN Interfaces . . . . . . . . . . . . . . . . . 104
8.2.3 Alarm Rules for Bridge Leased Lines Interfaces . . . . . . . . . 104
8.2.4 Alarm Rules for Disk Storage . . . . . . . . . . . . . . . . . . . . . . . . 105
8.3 Computer Software Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.3.1 Alarm Rules for Alarm Logs . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.3.2 Alarm Rules for Alarm Escalation . . . . . . . . . . . . . . . . . . . . . 106
9 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
9.1 Special Operations for Operation Contexts . . . . . . . . . . . . . . . . . . . . 107
9.2 Special Operations for Alarm Rules . . . . . . . . . . . . . . . . . . . . . . . . . . 112
9.3 Special Operations for Alarm Objects . . . . . . . . . . . . . . . . . . . . . . . . 113
10 Alarm Text Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
11 Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
6 MA268 • Rev. B1
Tellabs® 6300 Network Manager Preface
Alarms
Preface
The purpose of this This documentation provides procedures that explain how to create alarm
documentation rules, filter alarms and interpret the alarm text for alarms triggered by the Tel-
labs 6300 network management system. Although the Tellabs 6300 network
management system activates the alarms, the user interface of the TeMIP Cli-
ent V5.1 for Windows displays the alarms.
For general information about using TeMIP Client V5.1 for Windows, use the
on-line help that is installed with the software. This on-line help is the com-
plete user documentation for the TeMIP Client V5.1 for Windows. Use it to
learn about the TeMIP Client, or to solve configuration or operation problems
while using the software.
Note: We assume that you are familiar with Microsoft Windows. For exam-
ple, you must know how to navigate in a tree structure and how to ac-
tivate pop-up menus.
Product version Use the Main Release Notes for the Tellabs 6300 network manager to make
sure that this documentation is the correct version for your current software
product.
The structure of this This documentation is structured as follows:

documentation
• Part I gives an introduction to alarm handling.
• Chapter 1 describes the principles in alarm handling and how alarms
are indicated in the Tellabs 6300 manager user interface.
• Chapter 2 introduces the entities connected to alarms and describes the
most important alarm attributes.
• Chapter 3 describes the filters that can be used to control the amount of
alarm information.
• Part II describes the common work procedures in handling alarms (that is,
how to define which alarms to collect, and how to inspect and handle the
displayed alarms).
• Part III is a reference section.
• Chapters 6 and 7 describe the attributes for the entities connected to
alarms.
• Chapter 8 describes the attribute values in connection with system
monitoring.
• Chapter 9 describes the special operations for the entities connected to
alarms.
• Chapter 10 lists and describes all the alarm texts possible from the net-
work management network elements
• Chapter 11 lists the names of the standardized probable causes.
• The last chapter is an index for the documentation.
MA268 • Rev. B1 7
Alarms
Style conventions The following style conventions are used in the text:
• Italic text
Italics text is used in the following situations:
• File, computer and directory names.
• Commands in normal text.
• Text that is to be replaced with a correct term or expression. This text is
normally enclosed in < >.
• Bold text
Bold text is used in the following situations:
• Names of windows displayed on screen
• Names of menu items accessed from the menu bar. (When these are
shown as a command, an arrow separates the menu items.)
• Names of push buttons displayed on screen
• Text typed as an answer to a question displayed on screen
• Monospaced text
Monospaced text is used in the following situations:
• Text to be typed as a command
• Computer dialog issued by software in a command line interface (no
graphical interface used)
• [Text] in square brackets
Text in square brackets is used in the following situations:
• [Monospaced] text in square brackets indicates optional items in
commands
• [Bold] text in square brackets indicates a function key on the keyboard
• {Text} in braces
Text in braces is used in the following situations:
• Choices in commands. These are normally separated by a vertical line
(|).
Abbreviations AIS Alarm Indication Signal

CCITT International Telegraph and Telephone Consultative Com-
mittee
ITU International Telecommunication Union
OSI Open Systems Interconnection
References [1] MA266, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-
work Manager, Working in Tellabs 6300 Manager, Vol.1: Principles of
Operation, User’s Manual
[2] MA267, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-
work Manager, Working in Tellabs 6300 Manager, Vol.2: Using the Net-
work Editor, User’s Manual
[3] MA269, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-
work Manager, Working in Tellabs 6300 Manager, Vol.4: Using the Entity
Browser, User’s Manual
8 MA268 • Rev. B1
Alarms
[4] TeMIP Client V5.1 for Windows, On-line help – Alarm Handling
[5] TeMIP Client V5.1 for Windows, On-line help – Alarm History
[6] TeMIP Client V5.1 for Windows, On-line help – TeMIP Desktop
[7] TeMIP Notification FM, Alarm Rules FM and Collection AM User’s
Guide
MA268 • Rev. B1 9
Alarms
10 MA268 • Rev. B1
Tellabs® 6300 Network Manager Part Overview of Alarm Handling
Alarms
Part I: Overview of Alarm Handling
• ‘1 Alarm Handling’ on page 13
• ‘2 Alarm Entities and Attributes’ on page 21
• ‘3 Alarm Filters’ on page 29
MA268 • Rev. B1 11
Tellabs® 6300 Network Manager Part Overview of Alarm Handling
Alarms
12 MA268 • Rev. B1
Tellabs® 6300 Network Manager 1 Alarm Handling
Alarms
1 Alarm Handling
Overview This chapter introduces the principles in alarm handling and describes how
alarms are indicated in the Tellabs 6300 manager user interface.
1.1 The Principles of Alarm Handling
Introduction Alarm handling is a function performed partly by Tellabs 6300 manager and
partly by the users of the system. Tellabs 6300 manager collects, presents and
logs alarms from the equipment of the managed network, while the users lo-
cate and analyze the problems (using the system’s functions) and initiate re-
pair actions.
Definition of alarms An alarm is a report on a detected fault or malfunction, either in the network
cables, in the equipment of the managed network, or in Tellabs 6300 manager
itself. For instance, a Tellabs 6340 switch node will send an alarm to Tellabs
6300 manager if it detects a loss of signal on the aggregate channel. Likewise,
Tellabs 6300 manager will generate an alarm if it detects a storage capacity
problem, or a problem in its own communication with the monitored equip-
ment.
Alarm reporting The figure outlines a typical fault example in which a cable rupture has caused
a loss of signal in the Tellabs 6340 switch nodes terminating the cable.
The Tellabs 6340 switch nodes in stations 1 and 2 detect a loss of signal due to
a cable rupture. They both send an alarm to Tellabs 6300 manager, which pre-
sents the alarms to the operator.
MA268 • Rev. B1 13
Alarms
Alarm information An alarm contains information on the detected fault. By default, the following
types of information are presented by the Real Time View window:
• Event Time
• Main Object
• Detailed Object
• Alarm Text
• Perceived Severity
• Probable Cause
• Specific Problems
• State
• Operator Note
• Domain
• Identifier
The information is supplied as attributes of the alarm objects, in formats rec-
ommended in OSI standards, and are shown in the alarm windows. The most
important attributes are described in ‘2.2 Attributes for Alarms’ on page 23
Alarm surveillance The alarm handling function, which allows the operator to supervise the
alarms received by Tellabs 6300 manager, can be run either as a stand-alone
system or as an integrated part of Tellabs 6300 manager.
Alarm presentation When an alarm is received by Tellabs 6300 manager, it is presented as one line
in the main alarm window. When no additional filters are used, this is called
the All Alarms - [n] - Real Time View window, where n is the number of active
alarms present.
The operator may also be notified in the map window or the Network Manage-
ment window, when an alarm is received, by a change of color of the icons rep-
resenting the faulty entities. The estimated severity determines the color. This
is called map notification.
Note: Map notification is only available when the alarm windows are open
(that is, when the alarm handling function is activated).
Alarm handling by the An alarm reflects an error condition somewhere in the managed network, or
user in Tellabs 6300 manager. Such a condition requires action by you, the user.
You must handle the alarm. To handle the alarm, select the alarm in the All
Alarms - [n] - Real Time View window and open the pop-up menu. The pop-up
menu makes the following options available:
• Acknowledge – when you select this option, the icon in the State column
changes to indicate that you have acknowledged the alarm.
• Acknowledge... – when you select this option, you are able to provide an
ID, which identifies who acknowledged the alarm.
• UnAcknowledge – this option enables you to return alarms that are already
acknowledged to their previous states.
• UnAcknowledge... – this option enables you to return alarms that are al-
ready acknowledged to their previous states and provide a user ID, which
enables you to identify who made the change.
14 MA268 • Rev. B1
Alarms
• Terminate – this option removes the alarm from the list of alarms. Once an
alarm is terminated, it cannot be returned to the list of alarms unless the
alarm is sent again.
• Terminate... – this option removes the alarm from the list of alarms and en-
ables you to provide an ID, which identifies who terminated the alarm.
• UndoTerminate – this option has no function.
• UndoTerminate... – this option has no function.
• Open in Current Management View... – this option opens a new window
that displays all the attributes for the selected type of alarm.
• Open in New Management View...
• Print Preview... – this option enables you to view on screen both the format
of the alarm and the alarm details before they are printed.
• Print – this produces a hard copy of the details for the selected alarm(s).
The details are presented in a table, which provides details about the fol-
lowing attributes:
• Alarm Origin
• State
• Problem Status
• Handled by
• Alarm Report Clearance Received
• Correlated Notifications
• Event Type
• Probable Cause
• Managed Object
• Target Entity
• Additional Text
• Event Time
• Domain
• Operator Note
• OC Name
• Identifier
• Original Severity
• Notification Identifier
• Similar Alarms
• Problem Occurrences
• Original Event Time
• User Text
• User Identifier
MA268 • Rev. B1 15
Alarms
Note: If no information is available for one or more of these attributes, then

there are blank cells in the table.
• Set Operator Note... – this option enables you to attach notes to the indi-
vidual alarms.
• Show Comments – this option enables you to view any comments, which
have been added as additional text. This is useful when trying to trouble-
shoot a system for alarms of the same type.
• Copy to Clipboard – this copies the whole alarm record to the clip board.
• Create Statistics on Managed Object – this option provides a new window
which displays alarm severity statistics for the selected managed object.
These statistics are displayed in a graphic format.
Note: The statistics displayed with this option are not affected by the use
of filters in the Real Time View window
• Create Statistics on Operation Context – this option provides a new win-
dow which displays alarm severity statistics for the operation context.
These statistics are displayed in a graphic format.
Note: The statistics displayed with this option are not affected by the use
of filters in the Real Time View window
The course of an alarm, including the actions to be performed, from the time
it appears initially until the alarm is finally archived, is described in
‘5.2 Inspecting and Handling Alarms’ on page 51
Alarm logging When an alarm is received, it is immediately registered in an alarm log. An

alarm remains here until it is transferred to the archives of the network man-
agement center.
Alarm responsibility Responsibility for alarm handling can be divided into fields of responsibility,
areas, and shared between several operators of a network management center.
The division of responsibility between operators can be adjusted as required.
Note: An operator assigned to a specific area will normally not receive alarms
from other areas. Only alarms from his own area will normally be visi-
ble.
Note: In Tellabs 6300 manager, the fields of responsibility or areas in connec-
tion with alarms are called operation contexts. An operation context
collects the alarms from a specific domain. See ‘2.1.1 The Operation
Context’ on page 21 for more information about operation contexts.
Alarm rules Figure ‘Alarm reporting’ on page 13 illustrates a situation where the managed
equipment itself can detect and report errors. Some kinds of equipment, how-
ever, do not have this ability, although they have the ability to respond to que-
ries on current status and characteristics.
To monitor such equipment (in the framework of Tellabs 6300 manager, typi-
cally computer hardware and software), special alarm rules are set up. These
rules recurrently ask the equipment for key values. If these key values are
found to be unacceptable compared to predefined standards, an alarm is gen-
erated. See ‘2.1.2 The Alarm Rule’ on page 22 for information about the differ-
ent types of alarm rules.
Alarm clearance Modern transmission equipment has been designed to detect and report both
appearance and disappearance of transmission problems. This means that,
when a problem is encountered, an alarm is sent. And when the problem is
16 MA268 • Rev. B1
Alarms
perceived to have disappeared — for example, due to a repair — a new

“alarm” is sent to clear the first one. This second alarm is called a clearance
alarm and has the severity Clear. One clearance alarm can clear several genu-
ine alarms, if the problem originally caused many alarms to be generated.
When a clearance alarm is received and is matched to a genuine alarm, the
genuine alarm is normally automatically terminated and removed from the
Real Time View window. So, to notify you about the clearance and termination,
a line of text with information about the clearance is displayed in the message
column of the RealTime AH tab in the Message Console window.
This line of text is called a pseudo-alarm because, on the one hand, it is not a
real alarm (icons in the map window will not be colored to indicate it), but on
the other hand it appears as an alarm.
In the Real Time View window, the clearance alarm is represented by an alarm
object with the perceived severity Clear if a clearance alarm cannot be matched
with an existing alarm. This may be occur if the alarm has already been termi-
nated by an operator.
1.2 Alarm Indication
How alarms are When an alarm is generated in an entity, the existence of the alarm is indicated
indicated in the various Tellabs 6300 manager windows where the entity itself or entities
containing that entity are represented. In general, the alarm is indicated by a
display of the color matching the alarm’s severity (see ‘Icon colors’ on page 18
for a description of the alarm colors). When the alarm has been cleared or ter-
minated, the color display disappears. The alarm is indicated in the different
types of windows in the following way:
• In the Real Time View window and History View window, the complete
alarm information line is colored in a color that shows the severity of the
alarm.
• In the Map View window, the border around the relevant icons and/or
boxes blink in the alarm color.
• In the Trail View window the alarm indication field at the bottom of the
window is colored in the same color as the severity of the alarm.
Note: The alarm indication field is not updated dynamically. If an alarm is
cleared while the window is open, it is necessary to refresh the win-
dow manually before the color is removed.
• In the Find Trail window, the trail name is highlighted in the alarm color.
You can locate where the alarm is coming from by double-clicking on an alarm
information line. This opens the attributes window for the operation context
of the selected alarm. Alternatively, you can double- click on an icon indicat-
ing an alarm and thereby display its child entities.
Note: When several alarms exist for the same entity, the color from the alarm
of the highest severity is used.
MA268 • Rev. B1 17
Alarms
Icon colors The color of the alarms in the Real Time View window are determined by the
most severe not-handled alarm within the entities the icon represents. The ta-
ble shows the default colors for the different severities.
Severity Color
Critical Red
Major Orange
Minor Yellow
Warning Green
Indeterminate Blue violet
Clear Blue
If you wish to use different colors for the different alarms, then you can
change them in the TeMIP Client window. Select Tools →Options... →General
tab. In the Set Severity Color group box, use the Windows color palette to
change the color settings.
Note: This method does not change the colors of the alarms in the Trail View
and Find Trail windows. Although the alarm colors in these windows
can be changed, we recommend that you use the default color settings.
18 MA268 • Rev. B1
Alarms
Examples of alarm The figure shows how the same alarm is indicated in different ways in differ-
indication ent types of windows.
MA268 • Rev. B1 19
Alarms
20 MA268 • Rev. B1
Tellabs® 6300 Network Manager 2 Alarm Entities and Attributes
Alarms
2 Alarm Entities and Attributes
Overview This section introduces the entities connected to alarm handling (the opera-
tion context and the alarm rule) and describes the most important attributes
for an alarm.
Although the operation contexts and alarm rules are defined using the
T6300NM Entity Browser, and not the TeMIP Client, it is important that you
know how these entities are connected with the alarm handling.
2.1 Alarm Entities
Overview The following entities must be set up to enable the reception and handling of
alarms:
• ‘2.1.1 The Operation Context’ on page 21
• ‘2.1.2 The Alarm Rule’ on page 22.
2.1.1 The Operation Context
Definition An operation context is the supervisor and collector of alarms from the entities
(the physical objects, for example network elements) within a specific domain.
The managed network and the Tellabs 6300 manager representation are divid-
ed into a number of domains that together form a hierarchy, where the top do-
main is at the highest level. The alarm handling function, which receives, han-
dles and logs alarms, is organized in a similar way. Each major domain is as-
signed an operation context, in which all alarms that originate from that do-
main are received, handled and stored.
Note: The assignment of an operation context to a domain is fixed and cannot
easily be changed.
MA268 • Rev. B1 21
Alarms
An example The figure shows an example of an alarm handling organization, where the
alarm handling function is divided into two distinct operation contexts.
Alarms from domain A are received in the operation context for domain A,
while alarms from domains b1, b2, and b3 are received in the operation con-
text for domain B.
Note: Domains b1, b2, and b3 share a single operation context, for instance be-
cause each of them is too small to comprise a field of responsibility of
appropriate size.
Fields of responsibility An operation context represents a field of responsibility with respect to alarm
handling. Typically, one operator will get the responsibility for one operation
context, while another operator will get the responsibility for another opera-
tion context. The division of the alarm handling function into a number of op-
eration contexts, therefore, reflects the (potential) division of responsibility be-
tween operators of a network management center. The actual division of re-
sponsibility at your management site will determine which operation context
you are responsible for and when.
Note: It is possible for individual operators to adopt responsibility for several
operation contexts. This is, for instance, useful when a reduced number
of operators are working on the night shift at a management center.
Alarm log An alarm log is attached to each operation context. This logs all the alarms re-
ceived in the operation context. The contents of the alarm log can be dis-
played, and you can search for specific groups of alarms.
2.1.2 The Alarm Rule
Definition An alarm rule is used to generate alarms for equipment that cannot generate
alarms by itself.
At regular intervals, an alarm rule checks the value of a specified attribute of,
for instance, a terminal server. If the value is not acceptable, the alarm rule
fires (generates an alarm). Alarm rules can also be used to monitor equipment
22 MA268 • Rev. B1
Alarms
that is not part of the managed network, such as a thermometer measuring the
temperature in the computer room.
Types of alarm rules The table shows the five types of alarm rules.
Type of alarm rule Description
change of rule Monitor the value of an attribute and generate an

alarm if the value changes from one specified val-
ue to another. You may use wildcards if you want
any change of the value to generate an alarm.
comparison rule Compare the value of an attribute for, for in-

stance, an NE to a specified constant value by us-
ing a relational operator, for example > (greater
than). When you apply a comparison rule, the
system will check the value of the attribute at reg-
ular time intervals and compare it to the constant.
If the specified relation is satisfied, an alarm is
generated. The comparison rule can be used, for
instance, to monitor the temperature at a station
and generate an alarm if the temperature exceeds
a certain limit. The alarm is removed again auto-
matically, if the temperature falls below the limit.
expression rule Specify any of the other four alarm rule types in
one expression. To use the expression rule, you
must be thoroughly familiar with the syntax of an
alarm rule expression.
occurs rule Generate an alarm if a specified event occurs.
occurs n time rule Generate an alarm if a specified event occurs a

specified number of times over a specified period
of time.
2.2 Attributes for Alarms
Information from The information contained in the alarm attributes is normally sufficiently de-
attributes tailed for the operator to take appropriate action. However, it is often the com-
bination of information given, more than a single attribute for an alarm, that
gives a hint to what may have caused the problem. Furthermore, it is often the
combination of alarms received, and not the single alarm in itself, that helps
to identify the specific fault. For example, if you receive a LossOfSignal alarm
from both ends of a cable, a cable rupture would seem the most obvious ex-
planation.
The attributes for an alarm provide information about such things as, for ex-
ample, the severity of the alarm, the probable cause of the alarm, and from
which entity in the managed network the alarm has been sent. The values of
the attributes are shown in the alarm windows; but they can also be inspected
for each alarm using Open in Current Management View... option in the pop-up
menu.
This section describes a few of the most important attributes. See ‘6.2 Alarm
Object Attributes’ on page 80 for a description of all alarm attributes. You can
change the number and type of attributes shown, see ‘To change the alarm at-
tributes shown in the Real Time View window’ on page 24.
MA268 • Rev. B1 23
Alarms
To change the alarm It is possible to change the number and type of attributes shown in the Real
attributes shown in the Time View window and the History View window. To do this:
Real Time View window
Note: To simplify this procedure, only the Real Time View is referred to.
Step Action
1 Open the pop-up menu at the top of the table in the Real Time View or
History View window.
2 Select Customize....
The RT Alarms window or History Alarms window appears.
3 Use the buttons in the window to move the relevant field names and
set the order in which they appear.
4 Click OK to make the changes and close the window.
For a full description of how to customize the attributes shown, see [4].
2.2.1 The Event Time Attribute
Description The Event Time attribute gives the date and time when the alarm was generat-
ed. This information is a time stamp which is supplied by, for instance, the NE
that sent the alarm. It appears in the alarm windows in the Event Time column.
A number of other attributes (see Section 6.2) hold different time stamps at-
tached to the alarm.
2.2.2 The Main_Object Attribute
Description The Main_Object attribute is a user-friendly attribute. The information here is

extracted from the Managed Object attribute. It shows the type and name of the
NE or Tellabs 6300 manager component to which the detected fault applies.
For example, T6350_20.int indicates the type of the network element and its
working name.
2.2.3 The Detailed_Object Attribute
Description The Detailed_Object attribute is a user-friendly attribute. The information here

is extracted from the Managed Object attribute. It shows where the fault occurs
in the equipment. For example, PH_TTP "1-1-1-1" indicates that the fault oc-
curs on the trail termination point in rack 1, subrack 1, slot 1, port 1.
2.2.4 The Alarm_Text Attribute
Description The Alarm_Text attribute is a user-friendly attribute. It describes what fault

may be causing the alarm.
24 MA268 • Rev. B1
Alarms
2.2.5 The Perceived Severity Attribute
Description The Perceived Severity attribute indicates the severity level of the alarm. In the
alarm windows, the value of the attribute is shown in the Perceived Severity
column.
The severity levels Tellabs 6300 manager as well as the management equipment distinguish be-
tween different levels of severity. Some errors are estimated to be severe, be-
cause they normally affect the telecommunications traffic seriously, when
they occur. Other errors are perceived to be less severe, because they only
have minor or no direct influence on the traffic. In accordance with interna-
tional standards, six levels of severity exist. The table shows them in increas-
ing order of severity.
Severity level Explanation
Clear A clearance alarm.
Warning A problem that may become worse if not han-

dled, for instance that the alarm log is 40% full.
Minor A minor problem, sometimes a consequence of a

problem of greater severity. For instance, tribu-
taries will normally send Minor alarms when re-
ceiving alarm indication signals (AIS).
Major A severe problem that requires action very soon.
Critical A severe problem that requires immediate action.
Indeterminate The severity level could not be determined. It is

only rarely used in Tellabs 6300 manager.
2.2.6 The Probable Cause Attribute
Description The Probable Cause attribute describes the error in a standardized form.
Note: Do not try to interpret this in isolation, but combine it with the other at-
tributes, for example Alarm_Text, to get an idea of the problem causing
the alarm.
2.2.7 The State Attribute
Description The State attribute describes the stages that the alarm goes through from it
first appears until it is terminated. The alarm state is shown as icons in the Real
Time View window and the History View window.
The state icons The table shows the available alarm state icons.
Icon Name Description of State
Outstanding The alarm has not yet been acknowledged.
MA268 • Rev. B1 25
Alarms
Icon Name Description of State
Acknowledged The alarm has been acknowledged but not

yet terminated.
Terminated The alarm has been terminated but not yet

archived.
Note: The last icon does not appear in the Real Time View window. The com-
plete line is just removed.
2.2.8 The Clearance Attribute
Description The Clearance attribute indicates that the alarm has been cleared because a
matching clearance alarm has been received. The clearance icon is only shown
in the History View window when a clearance has been sent by the equipment
and then received and matched to the alarm. If the alarm cannot be correlated,
or the pseudo alarm function is not selected, then the clearance alarm remains
in the list of alarms.
The clearance report flag The table shows the clearance report flag icon.
icon
Icon Name Description
True The alarm has been cleared.
2.2.9 The Pseudo Alarm Attribute
Description The Pseudo Alarm attribute indicates that the alarm has been cleared and cor-
related. The pseudo alarm icon is only shown in the History View window
when a clearance alarm, that is sent by the equipment, is correlated and the
Pseudo Alarms option is selected in the Options Dialog window. By default, the
pseudo alarm option is selected.
Note: For details about how to change this setting, see [4].
The clearance report flag The table shows the clearance report flag icon.
icon
True The alarm has been cleared and correlat-

ed.
2.2.10 The Correlated Notifications Attribute
Description The Correlated Notifications attribute applies to the automatic clearance of

alarms. The attribute contains information about the alarms matched (corre-
lated) with the current alarm. The correlated notifications icon is only shown
in the Real Time View window and the History View window when correlated
notification information is available.
26 MA268 • Rev. B1
Alarms
Note: The Correlated Notifications attribute is not present in the default list of
attributes in the Real Time View window. For details about how to in-
clude it in the list, see [4].
The correlated notif info The table shows the correlated notif info icon.
icon
True Correlated notification information is

available.
MA268 • Rev. B1 27
Alarms
28 MA268 • Rev. B1
Tellabs® 6300 Network Manager 3 Alarm Filters
Alarms
3 Alarm Filters
Overview This section describes the filters that you can be use to control the amount of
alarm information displayed in the Real Time View and History View windows.
For a full description about creating and using the alarm filters, see [4] and [5].
3.1 Alarms View Filters
Description You can control the amount of alarm information displayed by setting up the
alarm filters. When you apply a filter to the alarm list in the Real Time View or
History View window, only those alarms that fulfil the requirements of the fil-
ter are displayed.
Note: Alarm filters are a display function only. The collection of alarms is not
affected by the use of alarm filters.
You can save each filter with a unique name. The filter names appear below
the User folder, which is visible in the Filter View. The Filter View is a tree
structure positioned on the left-hand side of the Real Time View and History
View windows. It is from within the Filter View that you control which filters,
if any, are active.
The Filter View From the Filter View, you decide which filter patterns are active or inactive
and you can open the Filter Editor window.
To use the filter patterns, you must select the check-box that is next to the filter
name. It is possible to use one or more filters at the same time.
Note: It depends on what the filter patterns specify that determines how well
the multiple filter patterns work together.
The Filter Editor window The figure shows the Alarm Handling Filter Editor window. You use this win-
dow to set up alarm filtering requirements and create alarm filters. To open
MA268 • Rev. B1 29
Alarms
the window, select View →Filter Patterns... while the Real Time View window
is selected.
Note: The filters for the History View window are set in the History Alarms Fil-
ter Editor window. You open this in the same way as described above.
The window is divided into 2 halves, a top half and a bottom half. These have
the following functions:
• Top half of the window: this shows you the names, the operator settings
and the filter patterns for any filters that are already present. If no filters
are present, it is here that you can create new filters. To create filter pat-
terns, see ‘5.1.3 Setting Up Alarm Filters’ on page 49.
• Bottom half of the window: this area enables you to define the patterns for
the filters. It is only possible to use this part of the window after you have
created a new filter in the top part of the window, or added a new item or
sub-filter to an existing filter. Patterns are created by selecting criteria
from the attributes list.
• Buttons: Use the Valid button once you have defined the filter rule to make
sure that the pattern you have defined is allowed. The Apply button is
only available after you have created, or edited, a valid filter pattern. Af-
ter you use this button, all the changes you have made in the Alarms Filter
Editor window are made available in the Real Time View or History View
windows.
Filtering criteria The filter patterns are set up by specifying values for some of the alarm at-
tributes. The following attributes are available:
• Acknowledge User Identifier
• Additional Text
• Alarm Origin
• Alarm Report Clearance Received
• Alarm Type
• Alarm Text
• Correlated Notifications
• Detailed_Object
• Domain
• Escalated Alarm
• Event Time
• Handled By Ticket
30 MA268 • Rev. B1
Alarms
• Identifier
• Main_Object
• Managed Object
• Notification Identifier
• OC Name
• Operator Note
• Original Event Time
• Original Severity
• Outage Flag
• Probable Cause
• Problem Occurrences
• Problem Status
• Security Problem Cause
• Similar Alarms
• State
• Target Entity
• Termination User Identifier
• User Identifier
• User Text
For a description of the individual alarm attributes and their possible values,
see ‘6.2 Alarm Object Attributes’ on page 80.
Example of a filter Filter patterns are often used to reduce the number of alarms displayed when
pattern you want to search for an individual alarm or type of alarm. In this example,
the filter pattern is used so that only alarms with a severity of critical are dis-
played. The figure shows how the pattern is defined, how it is displayed in the
MA268 • Rev. B1 31
Alarms
Filter View and the effect it has on the alarms displayed in the Real Time View
window
32 MA268 • Rev. B1
Tellabs® 6300 Network Manager Part Work Procedures
Alarms
Part II: Work Procedures
• ‘4 Defining the Alarm Collection’ on page 35
• ‘5 Supervising Alarms’ on page 43
MA268 • Rev. B1 33
Tellabs® 6300 Network Manager Part Work Procedures
Alarms
34 MA268 • Rev. B1
Tellabs® 6300 Network Manager 4 Defining the Alarm Collection
Alarms
4 Defining the Alarm Collection
Overview The first step in alarm handling is setting up the entities that allow alarm gen-
eration and collection. This section describes how to set up and manage the
operation contexts in order to collect alarms.
4.1 Operation Contexts
Overview This section contains the following information:

• ‘4.1.1 Creating Operation Contexts in a Domain’ on page 35
• ‘4.1.2 Managing Operation Contexts’ on page 36
• ‘4.1.3 Deleting Operation Contexts’ on page 40
• ‘4.1.4 Specifying Accumulation of Similar Alarms’ on page 42.
4.1.1 Creating Operation Contexts in a Domain
Introduction As mentioned in ‘2.1.1 The Operation Context’ on page 21, the total alarm col-
lection for a network can be divided among a number of operation contexts.
Each operation context is assigned to a domain and collects the alarms from
this domain and all its subdomains. Usually, all alarms from these domains
are collected, but the operation context can be defined to collect only alarms
of certain severities.
When you organize the management of a network, different users can be
made responsible for different operation contexts. For instance, different op-
erators may handle alarms in different geographical areas, while the system
manager only handles alarms from the man_env domain.
Operation contexts should be defined so that each domain is covered in one
and only one operation context. This means that special operation contexts
should not be defined for subdomains if the parent domain is already covered
by an operation context.
The existing operation contexts are represented by icons in the man_env do-
main. This is the domain where you create and delete operation contexts.
To create an operation This procedure describes how you define an operation context for a specific
context in a domain domain and register it in the TeMIP database.
Step Action
1 Start the T6300 network management system and log on to the cor-
rect server.
2 In the network manager window, select Operations →Entity Brows-

er.
The Entity View window appears.
3 In the Global Classes list, open the pop-up menu for

OPERATION_CONTEXT and select Directive View.
The Directive View - OPERATION_CONTEXT window appears.
MA268 • Rev. B1 35
Alarms
Step Action
4 To create the operation context:

a) In the Entity field, delete the * and type in the name for the new
operation context.
b) In the Directive field, select CREATE in the drop-down list.
c) Select Associated Domain and type in a name for the domain that
is supervised by the operation context.
d) Make sure that Automatic Terminate On Alarm Clearance is set to
true.
e) Select Operations →Start.
5 To register the operation context you just created:

a) In the Directive field, select Register in the drop-down list.
b) Make sure that the Operation field is set to Register.
c) Select Operations →Start.
6 Keep the Directive View window open as you need to copy the text in
the Entity field later on in this procedure.
7 In the network manager window, select Operations →Network Edi-

tor.
The Network Editor window appears.
8 To insert the operation context that you created:

a) In the domains view of the Network Editor, open the pop-up
menu for the domain name you defined in Step 4 and select Open
domain. A map view for the domain opens.
b) In the map view for the domain, open the pop-up menu and se-
lect Insert TeMIP object. The Insert TeMIP Object window appears.
c) In the Insert TeMIP Object window, select the Name field and paste
the text from the Entity field in the Directive View window.
d) Click OK.
e) Select File →Commit to implement the changes. The Commit win-
dow appears.
f) Click Start in the Commit window.
4.1.2 Managing Operation Contexts
Two entry points to There are 2 main entry points to manage operation contexts. The entry point
manage operation that you use depends on which task you are actually doing at the time. But re-
contexts gardless of the entry point, they both take you to similar user-interfaces. The
entry points are from:
• The T6300 network manager. This entry point takes you to the Directive
View - OPERATION_CONTEXT <oc name> window. This entry point is
commonly used when creating operation contexts for a domain.
• The TeMIP Client. This entry point takes you to the
OPERATION_CONTEXT <oc name> window. This entry point is commonly
36 MA268 • Rev. B1
Alarms
used while monitoring alarms. It provides an easy method to customize

the attributes for the operation context that you are monitoring.
To open the directive This procedure describes how to open the directive view for an operation con-
view from T6300 network text when you open it from the T6300 network manager.
manager
Step Action
1 Start the T6300 network management system and log on to the cor-
rect server.
2 In the network manager window, select Operations →Entity Brows-

er.
The Entity View window appears.
3 In the Global Classes list, select OPERATION_CONTEXT.

The Entity View - OPERATION_CONTEXT window appears. This win-
dow contains a complete list of all the operation contexts.
MA268 • Rev. B1 37
Alarms
Step Action
4 In the Entity View - OPERATION_CONTEXT window, open the pop-up

window for the correct operation context and select Directive View.
The Directive View - OPERATION_CONTEXT <oc_name> window ap-
pears.
To simplify the instructions in the procedures in this documentation,

this window is called the directive view window.
To open the directive This procedure describes how to open the directive view for an operation con-
view from the TeMIP text when you open it from the TeMIP Client.
Client
Step Action
1 Select Start →Tellabs 6300 Network Manager →TeMIP Client.

The TeMIP Client window appears.
Note: This is an example of how the TeMIP Client can appear. How it
appears on your system depends on how you saved the workspace.
38 MA268 • Rev. B1
Alarms
Step Action
2 If the Operation Context View window is not open in your TeMIP Cli-
ent window, select Window →OC View.
If the OC View window already contains the desired operation con-
text in the list of operation contexts, go to Step 7.
3 If the desired operation context is not shown in the list in the OC View
window, open the pop-up menu in the OC View window and select
OC List....
The Operation Context List window appears.
4 Make sure that there is a * in the OC Name field, and then click Find.
A list of all the operation contexts for the domain appears in the
Available Operation Contexts field.
5 Select the desired operation context(s) and click Add to add it to the
Alarm Handling Operation Context List field.
6 Click OK. The operations contexts present in the Alarm Handling Op-
eration Context List appear in the OC View window.
7 In the OC View window, open the pop-up window for the desired op-
eration context and select Open in New Management View....
The OPERATION_CONTEXT <oc name> window appears.
To simplify the instructions in the procedures in this documentation,

this window is called the directive view window.
MA268 • Rev. B1 39
Alarms
To perform an operation This procedure describes how you perform an operation on an operation con-
on an operation context text in the directive view.
Step Action
1 Open the directive view for the desired operation context. If you do
not know how to do this use one of the methods below:
• ‘To open the directive view from T6300 network manager’ on
page 37
• ‘To open the directive view from the TeMIP Client’ on page 38
2 Select the desired operation from the drop-down list.
Note: If you want to delete an operation context (oc), see ‘To delete an
operation context’ on page 40.
3 Depending on the directive view you are using, do one of the follow-
ing:
• Select Operations →Start, or
• Click the Execute directive button (green arrow).
Operations The specific operations for operations contexts are described in ‘9.1 Special
Operations for Operation Contexts’ on page 107.
4.1.3 Deleting Operation Contexts
To delete an operation This procedure describes how you remove an operation context from the
context man_env domain.
Step Action
1 Select all the alarms for the desired operation context and terminate
them all (see ‘To terminate an alarm’ on page 55).
40 MA268 • Rev. B1
Alarms
Step Action
page 37
3 Select SUSPEND in the operation drop-down list.
ing:
5 Select PURGE_ALARMS in the operation drop-down list.
ing:
7 Select DELETE in the operation drop-down list.
ing:
9 Select Deregister in the operation drop-down list.
MA268 • Rev. B1 41
Alarms
Step Action
ing:
The selected operation context is now removed from operation con-
text list.
4.1.4 Specifying Accumulation of Similar Alarms
To accumulate similar This procedure describes how to change the settings for an operation context
alarms so that similar alarms are shown once only.
Step Action
page 37.
• ‘To open the directive view from the TeMIP Client’ on page 38.
2 Select SET in the operation drop-down list.
3 Set the operation context’s Reduction Mode attribute to Automatic.

See ‘Reduction Mode’ on page 73.
4 Set the operation context’s Similarity Mode attribute to SameProblem-

Type or SameProblemTypeAndSeverity, depending on the required
similarity criterion.
See ‘Similarity Mode’ on page 74.
5 If required, change the operation context’s Severity Propagation Mode

attribute.
See ‘Severity Propagation Mode’ on page 74.
ing:
The changes are now active in Real Time View window in the TeMIP
Client.
42 MA268 • Rev. B1
Tellabs® 6300 Network Manager 5 Supervising Alarms
Alarms
5 Supervising Alarms
Overview This section contains the work procedures for starting alarm collection and for
inspecting and handling the received alarms. This is described in the follow-
ing sections:
Note: If you require full details about the TeMIP Client window, and/or the as-
sociated windows it contains, see [4].
• ‘5.1 Setting Up Alarm Handling’ on page 43
• ‘5.2 Inspecting and Handling Alarms’ on page 51
• ‘5.3 Using the History View to View the Alarm Log’ on page 56
5.1 Setting Up Alarm Handling
Overview This section describes how to prepare for alarm surveillance and inspection.
5.1.1 Opening the Window
The TeMIP Client The main window for the alarm handling function of Tellabs 6300 manager is
window the TeMIP Client window. It is from this window that you manage alarms and
get access to other windows for administration of the operation contexts (for
example, the OPERATION_CONTEXT <oc object name> window. This is also
known as the directive view, see page 45). You are also able to retrieve alarm
information from the alarm log (the History View window, see page 56). The
figure shows the contents of the Real Time View window.
The window contains the following areas:

• The menu bar, from which you can, for example, acknowledge and termi-
nate alarms and open the Real Time View and History View windows.
MA268 • Rev. B1 43
Alarms
• The operation context view (OC View). This shows a list of operation con-
texts. These can be either enabled or disabled.You enable and disable OCs
with the pop-up menu of each OC. Only when an OC is enabled can the
alarms appear in the Real Time View window.
• The filter area contains information about the currently used filters and
buttons for creating and selecting filters. Below the alarm information list
there are 2 alarm counters. These counters change when the filter settings
made in the filter area are enabled.
• The Console view provides you with information about what is happen-
ing in the windows open in the TeMIP Client.
• The alarm information list contains information about the alarms that are
not yet terminated. The information is organized in columns, where each
column represents either an alarm attribute or a user-defined field. The
number of columns, their contents and sequence are determined by you.
Below the list of alarms are 2 alarm counters and an alarm counter reset
button. The counter on the left shows the total number of alarms currently
displayed in the alarm information area. The counter on the right shows
the number of new alarms added to the window since you used the alarm
counter reset button. A pop-up menu is available for each alarm in the
alarm information list. This pop-up menu gives you access to the a direc-
tive view, which shows all the values for the attributes associated with the
selected alarm.
To open the Real Time This procedure describes how you open the Real Time View window, which
View window gives you a list of active alarms.
Step Action
1 If the TeMIP Client window is not already open, do it now. Select

Start →Tellabs 6300 Network Manager →TeMIP Client.
Note: How the TeMIP Client window looks when you open it de-
pends on what was open when the closed the window. When you
have a TeMIP Client configuration that suits you, you can save this as
a customized workspace.
The TeMIP Client window appears.
2 Select File →Open →Real Time View.

The Real Time View window appears.
Note: The very first time the Real Time View window appears, no
alarms are present. When this is the case, it is necessary to select an
operation context from the OC View and open a Real Time View win-
dow.
44 MA268 • Rev. B1
Alarms
5.1.2 Specifying Alarm Surveillance
Introduction Setting up alarm surveillance means including the relevant operation contexts
in the Operation Context View window. To include or remove operation con-
texts from the Operation Context View window, it is necessary to use the Oper-
ation Context List window.
The Operation Context The figure shows an example of the Operation Context View window. Within
View window this window, you are able to enable or disable the operation contexts. Only
when an operation context is enabled are you able to view the associated
alarms in the Real Time View window.
Icons in the Operation The OC View contains a number of symbols, or icons. Some of the more com-
Context View window mon ones are described below. For a complete list of symbols and explana-
tions see [4].
Column Icon Description
Administrative State Locked
Unlocked
Shutting Down
Unknown
Operational State Unknown
Off
On
MA268 • Rev. B1 45
Alarms
Column Icon Description
Monitored Enabled – the alarms for the opera-

tion context are shown.
Disabled – the alarms for the opera-

tional context are not shown.
Degraded
To open the Operation This procedure describes how you open the Operation Context List window.
Context List window
Step Action
1 In the OC View window, open the pop-up menu and select OC List....
Note: If you have not used the OC list window, then the fields in the
window are empty.
2 To show all the operation contexts available for the domain, make
sure that there is a * in the OC Name field, and then click Find.
A list of all the operation contexts for the domain appears in the
Available Operation Contexts field.
3 To use the contents of the OC List, use one of these procedures:

• ‘To add an operation context to the list in the OC View’ on page
46
• ‘To remove an operation context from the list in the OC View’ on
page 47
To add an operation This procedure describes how you include an operation context in the list in
context to the list in the the Operation Context View window.
OC View
Step Action
Note: If no operation contexts appear, see ‘To open the Operation
Context List window’ on page 46 and display all the operation con-
texts.
46 MA268 • Rev. B1
Alarms
Step Action
2 Select the desired operation context(s) in the Available Operation Con-

text field and click Add.
The selected operation context(s) is added to the list in the Alarm
Handling Operation Context List field.
3 Click OK.
The OC List window closes and the operations contexts present in the
Alarm Handling Operation Context List appear in the OC View win-
dow.
Note: The operation contexts are disabled. While they have this state,
no alarms appear in the Real Time View window.
To remove an operation This procedure describes how you remove an operation context from the list
context from the list in in the Operation Context View window.
the OC View
Step Action
Note: If no operation contexts appear, see ‘To open the Operation
Context List window’ on page 46 and display all the operation con-
texts.
2 Select the desired operation context(s) in the Alarm Handling Opera-

tion Context List field and click Remove.
The selected operation context(s) is added to the list in the Available
Operation Contexts field.
MA268 • Rev. B1 47
Alarms
Step Action
3 Click OK.
The OC List window closes and the operations contexts removed
from the Alarm Handling Operation Context List do not appear in the
OC View window.
To enable alarm display This procedure describes how you enable the display of alarms from a specific
operation context.
Step Action
1 If the operation context has not already been included in the alarm
handling, follow the procedure described in ‘To add an operation
context to the list in the OC View’ on page 46.
2 In the Operation Context View window, open the pop-up menu for
the desired operation context and select Enable.
All the alarms for the operation context appear in the Real Time View
window.
To disable alarm display This procedure describes how you disable the display of alarms from a specif-
ic operation context.
Step Action
1 If the operation context has not already been included in the alarm
handling, follow the procedure described in ‘To add an operation
context to the list in the OC View’ on page 46.
2 In the Operation Context View window, open the pop-up menu for
the desired operation context and select Disable.
All the alarms for the operation context in the Real Time View win-
dow are removed.
48 MA268 • Rev. B1
Alarms
5.1.3 Setting Up Alarm Filters
To define and apply a This procedure describes briefly how you define a pattern for an alarm filter.
filter pattern Alarm filters are a display function only. They determine what is shown in the
alarm view windows, but they do not affect the collection of alarms. For a full
description of how to create, edit and enable alarm filters, see [4].
Note: Some of the criterion fields support regular expressions (string or entity
data types).
Step Action
1 In the alarm filter area of the Real Time View window or History View
window, open the pop-up menu and select New Pattern.
The Filter Editor window appears.
2 In the Filter Editor window, provide a name for the filter. (If the edi-
tor is not active, open the pop-up menu for the filter name and select
rename.)
Note: It is recommended that the name provides an indication to the
function of the filter.
3 When you have given a new name, click outside of the editor field to
keep the name.
4 Open the pop-up menu for the filter name you just gave and select
Add Item.
A list of possible attributes appears in the Attributes field.
5 Scroll through the list of attributes and select the correct attribute.
When an attribute is selected, one of the following appears:
• A list of possible operators appears in the Operator(s) field. If this
is the case, go to Step 6.
• A text field appears. If this is the case, go to Step 7.
6 Select one or more of the possible values from the list.

Go to Step 8.
MA268 • Rev. B1 49
Alarms
Step Action
7 Use the following procedure to provide user-defined text:.

a) Click the New (Insert) button in the Value(s) field. A new text field
appears.
b) Type in the value that you wish to use.
c) Click . This saves the text.

d) Go to Step 8
8 Click Validate to keep the filter pattern you just created.

When a valid filter pattern is created, then the Apply button becomes
active.
9 Click Apply to implement the changes.

The filter pattern you created is now available in the alarm filter area
in the Real Time View and History View windows.
To inspect a filter pattern This procedure describes how you inspect the criteria of an existing filter pat-
tern.
Step Action
1 In the Real Time View window or the History View window, expand
the tree structure in the alarm filter area.
2 Select the desired filter from the list and expand the tree structure for
this filter.
The filter pattern’s criteria are displayed.
Note: If a pattern has more than one value, then the values are listed
below each other and separated with an OR.
To delete a filter This procedure describes how you delete an existing filter.
Step Action
the tree structure in the alarm filter area.
2 Open the pop-up menu for the desired filter and select Delete Pattern.
The filter name is removed from the list.
To select the use of a This procedure describes how you select a filter pattern that you want to use.
filter
Step Action
the tree structure for the user-defined filter patterns in the alarm fil-
ter area.
50 MA268 • Rev. B1
Alarms
Step Action
2 Select the check-box for the desired filter.

The filter is now active. Only those alarms that meet the filter pattern
are shown in the Real Time View window or the History View win-
dow.
To deselect the use of a This procedure describes how you clear the use of any filter whatsoever. That
filter is, how you display all not-closed alarms again.
Step Action
the tree structure for the user-defined filter patterns in the alarm fil-
ter area.
2 Remove the mark in the check-box for the desired filter.

The filter is no longer active. All alarms that were removed when the
filter was selected appear in the Real Time View window or the Histo-
ry View window.
5.2 Inspecting and Handling Alarms
Introduction From the time an alarm is initially introduced in Tellabs 6300 manager until it
is placed in the archives of the network management center, it passes through
a number of stages. This section describes these stages and the procedures at-
tached to them.
5.2.1 An Overview of the Process for Handling Alarms
The course of an alarm The table describes the stages that an alarm passes through from it is received
till it is archived.
Stage Description
1 The first appearance of the alarm.
When an alarm appears for the first time in the Alarm Handling win-
dow, its state will be Outstanding and its problem status will be Not-
Handled (that is, nobody has yet recognized or acted upon the
alarm). The alarm will remain Outstanding until it is acknowledged,
and it will remain Not-Handled.
2 The alarm is acknowledged.
When you acknowledge an alarm, you indicate to Tellabs 6300

manager that you will take action to get the underlying problem
solved. Conversely, if you — as the responsible operator — do not
acknowledge an alarm within a certain time, the alarm will normal-
ly be forwarded to a management headquarter, to ensure that
someone else handles the problem. See Section 5.2.2 for a descrip-
tion of the procedure.
MA268 • Rev. B1 51
Alarms
Stage Description
3 The problem is located.
An operator will often be able to recognize the problem causing an

alarm at the very moment the alarm appears. However, some
alarms require a more careful analysis, before action can be taken to
solve the problem.
The following hints may ease the process of locating and handling
the problem (see Section 5.2.3 for a description of the procedures):
• You can use a filter to limit the number of alarms currently
shown.
• You can look at all the attributes that have been set for the alarm.
• Tellabs 6300 manager can automatically find the entity causing
the alarm in the map window.
• You can look at the attributes of the equipment causing the
alarm.
4 A note is attached to the alarm.
When you have acknowledged an alarm and located the problem

causing the alarm, it is a good idea to attach a short note to the
alarm. It allows both you and others to see what action was actually
taken. See Section 5.2.4 for a description of the procedure.
5 The alarm is terminated.
When the problem of the alarm has been solved, the alarm must be
terminated. Normally, alarms are terminated automatically by the
system. But in some cases — for instance, if the problem causing an
alarm is a lasting one — it may be a good idea or even necessary to
terminate an alarm manually. See Section 5.2.5 for a description of
the procedure.
Note: When an alarm is terminated, it will be removed from the Real
Time View window. However, the alarm is not removed from Tellabs
6300 manager. It remains in the alarm log. From here it can be re-
trieved and inspected later (see ‘5.3 Using the History View to View
the Alarm Log’ on page 56).
6 The alarm is cleared and matched automatically.
Tellabs 6300 manager has mechanisms for matching a genuine

alarm with a clearance alarm. Such a matching causes the genuine
alarm to be automatically terminated (and removed from the Real
Time View window) and the clearance alarm to be converted to a
pseudo-alarm. However, if the clearance alarm cannot be matched
with an existing alarm — the genuine alarm may, for instance, have
been terminated by the operator — it will be displayed as a genuine
alarm (with severity Clear). See Section 5.2.6 for a description of the
changes in alarm attributes at alarm clearance.
52 MA268 • Rev. B1
Alarms
Stage Description
7 The alarm is archived.
From the alarm log, alarms can be retrieved for inspection days or
weeks after their occurrence. However, as new alarms are continu-
ously added to the alarm log, it is necessary once in a while to trans-
fer old alarms to other archives, to keep the size of the alarm log
manageable.
5.2.2 Acknowledging Alarms
To acknowledge an This procedure describes how you acknowledge an alarm, to indicate that you
alarm will take action to get the underlying problem solved.
Step Action
1 In the Real Time View window, open the pop-up menu for the desired
alarm, or alarms, and select Acknowledge.
The state changes from outstanding to acknowledged.
For details about the state attributes and icons, see ‘2.2.7 The State Attribute’
on page 25.
5.2.3 Locating the Problem
To limit the number of This procedure describes how you concentrate on only some alarms. For in-
alarms currently shown stance, alarms from one operation context or one NE and/or alarms with a
minimum level of severity.
Step Action
1 Create and use filters in the Real Time View window. See
‘5.1.3 Setting Up Alarm Filters’ on page 49.
To display all attributes This procedure describes how you show all attributes that have been set for a
for an alarm specific alarm.
MA268 • Rev. B1 53
Alarms
Note: The alarm information list in the Real Time View window only shows a
limited number of attributes of an alarm.
Step Action
alarm, or alarms, and select Open in New Management View....
The OPERATION_CONTEXT <oc name alarm_object n> window ap-
pears.
Note: There are multiple tabs available in this window. For full de-
tails about this window and the tabs in this window, see [6].
To manage the entity This procedure describes how you perform management operations directly
that caused the alarm on the entity causing a specific alarm.
Step Action
alarm, or alarms, and select Directives →Show.
A directive window specifically for the selected alarms appears.
5.2.4 Attaching a Note
To create an operator This procedure describes how you attach an operator note to an alarm.
note
Step Action
alarm, or alarms, and select Set Operator Note.
The Set Operator Note window appears.
2 Type in the text you want to attach to the alarm and click OK.
The text is added to the Alarm Object Operator Node attribute for the
alarm. You can view this in the alarm directive view window, see
‘To display all attributes for an alarm’ on page 53.
54 MA268 • Rev. B1
Alarms
5.2.5 Terminating Alarms
To terminate an alarm This procedure describes how you terminate an alarm manually to indicate
that the problem has been solved.
Step Action
1 In the Real Time View window or the History View window, open the
pop-up menu for the desired alarm, or alarms, and select Terminate.
Note: Both Acknowledged alarms and Outstanding alarms can be ter-
minated.
In the Real Time View window, the alarm is removed from the list of
alarms. In the History View window the attribute icons change, see
‘Attribute icon changes’ on page 55.
Attribute icon changes When an alarm is terminated in the History View window, the attribute icons
change. This is illustrated in the diagram below.
5.2.6 Automatic Clearance and Matching
Attribute icon changes When an alarm is matched to an alarm clearance, the alarm’s Acknowledged
state changes to Terminated, and the Clearance Report Flag is set.
Note: When the alarm is terminated, it is removed from the alarm list in the
Real Time View window.
Pseudo-alarm When an alarm clearance has been matched to an existing alarm and has ter-
minated it, a pseudo-alarm with information about the clearance is displayed
MA268 • Rev. B1 55
Alarms
in the Real Time View window. The pseudo-alarm is indicated by the icon
shown in the figure.
Note: If the alarm clearance is not matched to an existing alarm, it is displayed

as an ordinary alarm with severity Clear.
5.3 Using the History View to View the Alarm Log
The History View window An alarm is stored in an alarm log at the very moment it is received by Tellabs
6300 manager. There is one alarm log for each operation context, and the
alarm log is always accessed via its operation context.
You can inspect and handle the contents of an alarm log in the History View
window, which can be opened in the TeMIP Client window. The figure shows
an example of the History View window, which is used for displaying informa-
tion on the alarms of an operation context present in the alarm log.
The History View window provides a static display, representing a “snapshot”

of the alarm log at the time you opened the window or made the last search in
the log. That is, the alarm information list in this window will not be updated
automatically (as in the Real Time View window) if a new alarm is received, or
if the status of an existing alarm changes.
Note: When you open a new History View window, no alarm information ap-
pears. You must use the Start alarm display button to display the alarm
information for the selected operation context.
56 MA268 • Rev. B1
Alarms
5.3.1 Opening the Alarm Log
To open the History View This procedure describes how you open the alarm log in the TeMIP Client win-
window dow.
Step Action
1 Select File →Open →History View.

An All Alarms – History View window appears.
Note: The alarm information list is empty.
2 If this is the first time that you open the History View window, or you
have not selected an operation context previously, you must select
one now. Use these steps to do this:
a) In the TeMIP Client window, select File →OC List →OC List (His-
tory).... The Operation Context List window appears.
b) Click Find to display all the operation contexts for the domain.
c) Select the desired operation contexts in the Available Operation
Contexts field and click Add.
d) Click OK. The OC List window closes and the selected operation
contexts appear in the On Operation Contexts field at the bottom
of the History View window.
3 Click the Start alarm display button. The alarm information list fills
with all the alarms present in the alarm log for the selected operation
contexts.
MA268 • Rev. B1 57
Alarms
5.3.2 Searching in the Alarm Log
Introduction You retrieve alarms from the alarm log in the History View window. To make
it easier to find individual alarms, you are able to create the search patterns
that enable you to reduce the number of alarms in the list and find the alarm
you are interested in. For instance, you can set up a filter pattern to retrieve all
alarms originating from a specific NE and with a specific probable cause and
a specific alarm type.
For full details about using the search function in the History View window,
see [5].
To define a search This procedure describes how you define a search pattern.
pattern
Step Action
1 In the History View window, open the pop-up menu in the Search
Pattern tab and select New Pattern.
The Create a New Search Filter window appears.
2 Type in a name for the new filter pattern.

Note: We recommend that you give a descriptive name that indicates
which attributes the search pattern uses. The name cannot be modi-
fied once you have moved to the next window.
3 Click OK.
The History Alarm Handling Search Pattern window appears.
4 Click Insert Row.

A new line appears under the Attribute Name, Condition and Values
fields.
5 Select the correct values in the Attribute Name, Condition and Values
fields.
58 MA268 • Rev. B1
Alarms
Step Action
6 If you want to apply additional attributes to the search pattern, re-

peat Step 4 and Step 5.
7 When all the required attributes are defined in the Filter group box,
click OK.
The History Alarm Handling Search Pattern window closes and search
pattern name appears in the Search Pattern tab. These search pat-
terns are now available in all History View windows.
To change a search This procedure describes how you change the attributes of a search pattern.
pattern
Note: The search pattern name remains the same.
Step Action
1 In the Search Pattern tab of the History View window, open the pop-
up menu for the search pattern you want to change and select Prop-
erties.
The History Alarm Handling Search Pattern window appears.
2 Select the row of attributes you wish to change or click Insert Row if
you want additional attributes included.
3 When all the required attributes are defined in the Filter group box,
click OK.
The History Alarm Handling Search Pattern window closes. The
changed search pattern is now available in all History View windows.
MA268 • Rev. B1 59
Alarms
To apply a new search This procedure describes how you apply a new search pattern.
pattern
Step Action
up menu for the search pattern you want to use and select Apply Pat-
tern.
The search pattern attributes are applied. This is shown by a change

in the alarm list.
To apply a new search This procedure describes how you apply a search pattern to a list of alarms in
pattern in a new window a new window. This enables you to keep the original list alarms open in an-
other History View window.
Step Action
up menu for the search pattern you want to use and select Apply Pat-
tern In New.
A new History View window appears. The selected search pattern at-
tributes are already applied to the list of alarms that appears.
To delete a search This procedure describes how you delete an existing search pattern.
pattern
Step Action
up menu for the search pattern you want to delete and select Delete
Pattern.
The search pattern name is removed from the Search Pattern tab.
5.3.3 Purging Alarms
Introduction When alarms are not purged automatically from the alarm log during the ar-
chiving process (see the Purge parameter in the operation ‘Archive’ on page
110), they can be purged with a specific operation.
60 MA268 • Rev. B1
Alarms
Note: Only archived alarms can be safely purged.

Note: By default, Tellabs 6300 manager is set up to automatically purge all ter-
minated alarms older than 60 days once a day.
To purge alarms This procedure describes how you purge alarms.
Step Action
page 37
2 Select SUSPEND in the operation drop-down list.
ing:
4 Select PURGE_ALARMS in the operation drop-down list.
ing:
All the alarms for this OC are purged.
6 Select RESUME in the operation drop-down list.
MA268 • Rev. B1 61
Alarms
Step Action
ing:
See the description of the operation and its parameters in
‘Purge_alarms’ on page 108.
62 MA268 • Rev. B1
Tellabs® 6300 Network Manager Part Reference Information
Alarms
Part III: Reference Information
• ‘6 Operation Context and Alarm Attributes’ on page 65
• ‘7 Alarm Rule Attributes’ on page 91
• ‘8 Alarm Rules for System Monitoring’ on page 103
• ‘9 Operations’ on page 107
• ‘10 Alarm Text Descriptions’ on page 115
• ‘11 Probable Causes’ on page 139
MA268 • Rev. B1 63
Tellabs® 6300 Network Manager Part Reference Information
Alarms
64 MA268 • Rev. B1
Tellabs® 6300 Network Manager 6 Operation Context and Alarm Attributes
Alarms
6 Operation Context and Alarm Attributes
Overview This chapter describes the attributes for the operation context entity and its
child entities (alarm objects and similar alarms). The operation context entity
is used to collect alarms within a specific domain, as described in ‘2.1.1 The
Operation Context’ on page 21.
6.1 Operation Context Attributes
Introduction The following attribute types are available for operation contexts:
• ‘6.1.1 Attributes for Registration of Operation Contexts’ on page 65
• ‘6.1.2 Identifiers Attributes for Operation Contexts’ on page 71
• ‘6.1.3 Characteristics Attributes for Operation Contexts’ on page 71
• ‘6.1.4 Status Attributes for Operation Contexts’ on page 75
• ‘6.1.5 Counters Attributes for Operation Contexts’ on page 80
• ‘6.1.6 Routing Attributes for Operation Contexts’ on page 80
6.1.1 Attributes for Registration of Operation Contexts
OPERATION_CONTEXT
Allows you to enter a name for the operation context. This attribute is manda-
tory.
Rules for entity names The following rules apply to entity names:
• The name must be unique among all global entities.
• The maximum length of an entity name is 511 characters.
• The following characters are allowed:
• !$-_0123456789
• abcdefghijklmnopqrstuvwxyz
• ABCDEFGHIJKLMNOPQRSTUVWXYZ
• If Tellabs 6300 manager is configured to support special national charac-
ters, an extended set of characters can be used, for instance special Scandi-
navian characters such as æ, ø and å.
• If the entity name is enclosed in quotation marks (“ “), an extended set of
characters can be used, for instance spaces, if you want to break the name
into multiple words. The following characters can be used:
• #%&’()*+,./:;<=>?@[\]^{|}~
Associated Domain
Determines which management domain is to be associated with the operation
context. Specify the full name. This attribute is mandatory.
MA268 • Rev. B1 65
Alarms
Automatic Acknowledge
Determines the severity level of the alarms that are created as acknowledged
instead of as outstanding. Alarms with severity levels less than or equal to this
value are automatically created as acknowledged.
Value Description
Indeterminate All alarms are automatically acknowledged.

Critical All alarms except indeterminate ones are auto-
matically acknowledged.
Major All alarms except indeterminate and critical ones
are automatically acknowledged.
Minor All alarms except indeterminate, critical and ma-
jor ones are automatically acknowledged.
Warning All warning alarms and clearance alarms are au-
tomatically acknowledged.
Clear Clearance alarms are automatically acknowl-
edged.
not-automatic No alarms are automatically acknowledged.
Automatic Escalation Critical Delta Time

Determines the maximum time an alarm of severity Critical may remain unac-
knowledged before it escalates. Enter a relative time using the format dd-
hh:mm:ss. Enter 0 to avoid automatic alarm escalation. This is the default set-
ting.
Automatic Escalation Major Delta Time

Determines the maximum time an alarm of severity Major may remain unac-
ting.
Automatic Escalation Minor Delta Time

Determines the maximum time an alarm of severity Minor may remain unac-
ting.
Automatic Escalation Warning Delta Time

Determines the maximum time an alarm of severity Warning may remain un-
acknowledged before it escalates. Enter a relative time using the format dd-
ting.
66 MA268 • Rev. B1
Alarms
Automatic Terminate On Alarm Clearance

Determines whether an alarm received in the operation context is terminated
automatically, when it is correlated with an incoming alarm of severity Clear.
Value Description
False Alarms are not automatically terminated. When

this value is set, ‘Termination Policy’ on page 70
is set to None automatically.
True Alarms are automatically terminated.
Note: In all predefined operation contexts this attribute was set to True. For
trail alarms, this attribute must be set to True.
Automatic Terminate On Alarm Close

Defines the severity level for automatic termination of alarms whose Problem
Status attribute changes to Closed. Alarms with severity less than or equal to
the specified level are automatically terminated when closed.
Value Description

matically terminated when closed.
Indeterminate All alarms are automatically terminated when
closed.
are automatically terminated when closed.
jor ones are automatically terminated when
closed.
Warning Warning alarms and clearance alarms are auto-
Clear Clearance alarms are automatically terminated
when closed.
not-automatic No alarms are automatically terminated when
closed.
Capacity Alarm Threshold

Specifies at which capacity threshold a ProcessingErrorAlarm should be gen-
erated to indicate that the alarm log is nearly full. Each threshold is specified
as an integral percentage of full capacity. Up to three thresholds can be speci-
fied separated by commas. Alternatively, you can enter the thresholds in sep-
arate fields. Place the cursor over the field name and select Create member in
the pop-up menu. The default setting will generate alarms when the alarm log
is 80, 90 and 100 percent full.
Examples:
50, 60, 70
40, 60
40
MA268 • Rev. B1 67
Alarms
The severity of the generated alarms is determined by the value of the corre-
sponding thresholds as follows:
Value Description
0 - 40% Severity: Warning

41 - 60% Severity: Minor
61 - 80% Severity: Major
81 - 100% Severity: Critical
Discriminator Construct
Defines an alarm filter. Refer to [8] for further information.
Implementation Desc
Allows you to specify an implementation description.
Initial Administrative State

Determines whether alarm collection is suspended from the creation of the
operation context. Later you can suspend and resume alarm collection using
the Suspend and Resume operations (see ‘9.1 Special Operations for Opera-
tion Contexts’ on page 107).
Value Description
Locked Alarm collection is suspended until a Resume op-

eration is carried out.
Unlocked Alarm collection is not suspended.
Note: Alarms cannot be collected when Operational State is set to Disabled

(see ‘Operational State’ on page 78).
Location
Allows you to specify the address of the center responsible for the operation
context.
MAIL Account
Allows you to specify the mail address for the responsible person or center.
Managing Director
Specifies the director in charge of the operation context entity. This attribute
is mandatory.
Name
Allows you to specify a descriptive name for the operation context icon.
A nick name can be defined during registration of an entity. If you define a
nick name, this name appears below the entity icon in the map window in-
stead of the entity name. This is useful if your network plan uses abbreviated
names and you want to show more descriptive names in the map window. For
example, if the entity name is defined as oc_sys_man, you may want to show
System Management instead.
68 MA268 • Rev. B1
Alarms
Note: The nick name is not an attribute. It is associated with the entity icon in
the map window in which the entity was created. If the entity is regis-
tered in two domains, it may have different nick names in the two map
windows. Therefore, you cannot show or set the nick name using the
Show and Set operations. If you need to change the nick name after reg-
istration, use the Change Entity Attributes... item in the pop-up menu.
Operation Context Description

Allows you to attach a note to the operation context to describe it.
Phone Number
Allows you to specify the telephone number of the responsible person or cen-
ter.
Reduction Mode
Defines whether incoming alarms concerning the same problem are accumu-
lated as similar alarms or not.
Value Description
NonAutomatic The alarms are not accumulated as similar

alarms.
Automatic Similar alarms are accumulated according to the
criterion defined by the Similarity Mode attribute
(see ‘Similarity Mode’ on page 70).
Reference Operation_Context Name

Allows you to copy the values from an existing operation context into the one
you are about to define. Enter the Tellabs 6300 manager name of the operation
context from which you want to copy.
Example: oc_sys_man
Note: If you enter values for attributes other than Reference
Operation_Context Name and Associated Domain, these values will
overwrite the values copied from the reference operation context.
Remarks
Allows you to enter a note (maximum 80 characters) to describe the operation
context.
Repository Location
Specifies the directory pathname of the alarm log. The default value is /var/
kits/temip.
Note: Do not change this attribute from its default setting. If you do, no back-
up will be performed.
Responsible Person
Allows you to specify the name of the person responsible for the operation
context. This person should be contacted before changes relating to the oper-
ation context are made.
MA268 • Rev. B1 69
Alarms
Scheduling Package
Defines specific periods of alarm collection activity. Refer to [8] for further in-
formation.
Severity Propagation Mode

Defines how the value of the alarm object’s Perceived Severity attribute is de-
termined, according to the severities of the accumulated similar alarms.
Value Description
Highest The highest severity among the incoming similar

alarms in the accumulation is used. This is the de-
fault value.
First The severity of the first alarm (the Original Alarm
Object) is used.
Latest The severity of the latest similar alarm in the ac-
cumulation is used (excluding clearance alarms).
Similarity Mode
Defines the criterion that is used during automatic alarm accumulation to de-
cide whether alarms are similar (see ‘Reduction Mode’ on page 69).
Value Description
NotApplicable No accumulation of similar alarms.

SameProblemType Alarms are similar if they have the same problem
for the same managed object. This is the default
value.
SameProblemTypeAnd- Alarms are similar if they have the same problem
Severity and severity for the same managed object.
Termination Policy
Determines how alarms are terminated automatically.
Value Description
None Alarm objects can be terminated using the Termi-

nate directive.
AckandCleared Automatic termination is possible when this val-
ue is selected and the state of the alarm object is
Acknowledged or Cleared.
Cleared Automatic termination is possible when this val-
ue is selected and the state of the alarm object is
Cleared.
Text File
Allows you to specify the full path of a text file with additional information.
Example: /usr/6300/op_con2/description
70 MA268 • Rev. B1
Alarms
6.1.2 Identifiers Attributes for Operation Contexts
Name
Shows the name of the operation context assigned at registration. You cannot
set this attribute.
6.1.3 Characteristics Attributes for Operation Contexts
Additional Text Propagation Mode

Specifies if the similar alarm’s Additional Text value needs to be propagated
to the Parent Alarm Object.
Value Description
NoUpdate The Additional Text value of a similar alarm is

not propagated to the parent alarm object.
Replace The Additional Text of a similar alarm replaces
the Additional Text of the parent alarm object.
Associated Domain
Shows the name of the domain associated with the operation context (see ‘As-
sociated Domain’ on page 65). You cannot set this attribute.
Automatic Acknowledge
Determines the severity level of the alarms that are created as acknowledged
instead of as outstanding (see ‘Automatic Acknowledge’ on page 66). Alarms
with severity levels less than or equal to this value are automatically created
as acknowledged.
Automatic Acknowledge on Handle

Specifies whether the alarm should be acknowledged automatically when the
alarm is handled.
Automatic Escalation Critical Delta Time

Determines the maximum time an alarm of severity Critical may remain unac-
knowledged before it escalates (see ‘Automatic Escalation Critical Delta Time’
on page 66).
Automatic Escalation Major Delta Time

Determines the maximum time an alarm of severity Major may remain unac-
knowledged before it escalates (see ‘Automatic Escalation Major Delta Time’
on page 66).
Automatic Escalation Minor Delta Time

Determines the maximum time an alarm of severity Minor may remain unac-
knowledged before it escalates (see ‘Automatic Escalation Minor Delta Time’
on page 66).
MA268 • Rev. B1 71
Alarms
Automatic Escalation Warning Delta Time

Determines the maximum time an alarm of severity Warning may remain un-
acknowledged before it escalates (see ‘Automatic Escalation Warning Delta
Time’ on page 66).
Automatic Terminate On Alarm Clearance

Determines whether an alarm received in the operation context is terminated
automatically, when it is correlated with an incoming alarm of severity Clear
(see ‘Automatic Terminate On Alarm Clearance’ on page 67).
Automatic Terminate On Alarm Close

Determines the severity level of the alarms that will be terminated automati-
cally when their Problem Status attribute changes to Closed (see ‘Automatic
Terminate On Alarm Close’ on page 67). Alarms with severity levels less than
or equal to this value are automatically terminated when closed.
Capacity Alarm Threshold

Determines at which capacity threshold a ProcessingErrorAlarm must be gen-
erated to indicate that the alarm log is nearly full (see ‘Capacity Alarm Thresh-
old’ on page 67).
Database Service Name

Provides the name You cannot set this attribute.
Discriminator Construct
Defines an alarm filter. Refer to [8] for further information.
LogFullAction
Determines the behavior of the alarm log when its maximum capacity is
reached (see ‘Max Log Size’ on page 72). You cannot set this attribute.
Value Description
Wrap The oldest alarm data is overwritten by the new

alarm data being logged.
Halt Alarm data is no longer logged.
Max Log Size

Determines the maximum alarm log size. You cannot set this attribute.
Mir Component Version

Indicates the version number of the MIR component. You cannot set this at-
tribute.
Operation Context Description

Determines a user-defined note describing the operation context (see ‘Opera-
tion Context Description’ on page 69).
Owner Id
Shows the user ID of the user who created the operation context. You cannot
set this attribute.
72 MA268 • Rev. B1
Alarms
Ownership Control
Specifies the policy for controlling the alarm life-cycle management.
Value Description
False Any operator is able to change the state of an

alarm when they acknowledge one.
True Only when the user is temip, root or listed as the
Acknowledgement User Identifier are they able to
change the state of the alarm when they acknowl-
edge the alarm.
Outage Policy
Determines the behavior of OutOfService alarms when they are received.
Value Description
NoAction The OutofService alarm object is treated as a nor-

mal alarm object.
Terminate The OutofService alarm object is terminated auto-
matically.
TerminateAndNotify The alarm object is terminated automatically and
the Alarm Object Creation event, followed by
Alarm Object State Change event, is emitted.
Acknowledge The alarm object is acknowledged automatically
and the Alarm Object Creation event is emitted
with an Acknowledged state.
Reduction Mode
Defines whether incoming alarms concerning the same problem are accumu-
lated as similar alarms or not.
Value Description
NonAutomatic The alarms are not accumulated as similar

alarms.
Automatic Similar alarms are accumulated according to the
criterion defined by the Similarity Mode attribute
(see ‘Similarity Mode’ on page 74).
Reduction Scope
Specifies the scope of the similarity algorithm. This algorithm is applied to
only alarm objects that have the state matching the Reduction Scope.
Value Description
NotTerminatedAO All alarm objects that are not in a Terminated

state are considered for similarity processing.
OutStandingAO All alarm objects that are in an Outstanding state
are considered for similarity processing.
MA268 • Rev. B1 73
Alarms
Repository Location
Shows the directory pathname of the alarm log (see ‘Repository Location’ on
page 69). You cannot set this attribute.
Responsible Operators
May hold the user IDs of the operators responsible for monitoring the opera-
tion context.
Scheduling Package
Defines specific periods of alarm collection activity. Refer to [8] for further in-
formation.
Severity Propagation Mode

Defines how the value of the alarm object’s Perceived Severity attribute is de-
termined, according to the severities of the accumulated similar alarms.
Value Description
Highest The highest severity among the incoming similar

alarms in the accumulation is used. This is the de-
fault value.
First The severity of the first alarm (the Original Alarm
Object) is used.
Latest The severity of the latest similar alarm in the ac-
cumulation is used (excluding clearance alarms).
Similarity Mode
Defines the criterion that is used during automatic alarm accumulation to de-
cide whether alarms are similar (see ‘Reduction Mode’ on page 73).
Value Description
NotApplicable No accumulation of similar alarms.

SameProblemType Alarms are similar if they have the same problem
for the same managed object. This is the default
value.
SameProblemTypeAnd- Alarms are similar if they have the same problem
Severity and severity for the same managed object.
Termination Policy
Specifies the criteria for automatic termination of the Alarm Object.
Value Description
None An alarm object can be terminated using the Ter-

minate directive. This attribute supersedes the
value for ‘Automatic Terminate On Alarm Clear-
ance’ on page 67.
74 MA268 • Rev. B1
Alarms
Value Description
AckAndCleared Automatic termination is possible when the

alarm object is cleared and the state is Acknowl-
edged.
Cleared Automatic termination is possible when the
alarm object is cleared.
6.1.4 Status Attributes for Operation Contexts
Description You cannot set the Status attributes for operation contexts.
Administrative State
Shows whether alarm collection is suspended. Initially, this attribute has the
same value as Initial Administrative State (see ‘Initial Administrative State’ on
page 68). Later it is set to Locked if the Suspend operation is carried out, and
to Unlocked if the Resume operation is carried out (see ‘9.1 Special Operations
for Operation Contexts’ on page 107).
Value Description
Locked Alarm collection is suspended.

Unlocked Alarm collection is not suspended.
Shutting down The selected entity is being deleted.
Note: Alarms are only collected when Administrative State is set to Unlocked,
and Operational State is set to Enabled (see ‘Operational State’ on page
78).
Administrative State Change Timestamp

Shows the last time the Administrative State attribute was changed (see ‘Ad-
ministrative State’ on page 75).
Archive AO Age
Shows the value of the AO Age parameter (see ‘Archive’ on page 110).
Archive AO Severity
Shows the value of the Severity parameter (see ‘Archive’ on page 110).
Archive Begin Time

Shows the value of the Begin Time parameter (see ‘Archive’ on page 110).
Archive Database Filename

Shows the value of the Database Name parameter (see ‘Archive’ on page 110).
Archive End Time

Shows the value of the End Time parameter (see ‘Archive’ on page 110).
MA268 • Rev. B1 75
Alarms
Archive Error Status

Shows the last error that occurred as a result of an automatic Archive operation
is carried out in the background (see ‘Archive’ on page 110).
Archive Interval
Shows the value of the Interval parameter (see ‘Archive’ on page 110).
Archive Last Time

Shows when the last automatic Archive operation (see ‘Archive’ on page 110)
was carried out. No value is returned if the last Archive operation was carried
out manually.
Archive Next Time

Shows when the next automatic Archive operation will be carried out (see ‘Ar-
chive’ on page 110). No value is returned if Archiving Status is set to Back-
ground Archive is Idle.
Archive Sequence Name

Shows the value of the Sequence Name parameter (see ‘Archive’ on page 110).
Archive Sequence Number

Shows the value of the Sequence Number parameter (see ‘Archive’ on page
110).
Archive and Purge

Shows the value of the Purge parameter (see ‘Archive’ on page 110).
Archiving Status
Shows whether an automatic Archive operation is running in the background
(see ‘Archive’ on page 110).
Value Description
Background Archive is Idle No automatic Archive operation is

running in the background.
Background Archive is Active An automatic Archive operation is
running in the background.
Associated Notif EFD

The value of this attribute is set each time a new Notify request call is issued
by the AH FM. This attribute makes the OC monitoring and diagnosing easier
when investigations are required.
76 MA268 • Rev. B1
Alarms
Availability Status
Elaborates on the operational state of the operation context (see ‘Operational
State’ on page 78).
Description of
Value Availability Sta- Description
tus
Enabled { } The operation context is fully en-

abled. This is the normal setting.
Degraded The operation context is enabled and
continues to work although a tran-
sient problem has been detected.
Off duty The operation context is enabled but
currently in an inactive period of a
scheduling process.
Disabled Failed The operation context is disabled
due to a fatal processing error.
Dependency The operation context is disabled
due to an error in TeMIP Frame-
work, the operating system or the
database on which it depends.
Log Full The operation context is disabled be-
cause the alarm log is full. You can
perform operations on existing oper-
ation contexts, but no new alarms
can be handled.
In Test The TeMIP Alarm Handling func-
tion is starting up.
Power OFF The operation context is disabled be-
cause the alarm collection has been
stopped by use of the temip_kill utili-
ty.
Availability Status Change Timestamp

Shows the last time the Availability Status attribute was changed (see ‘Avail-
ability Status’ on page 77).
Composite State
The value of this attribute reflects the health of the Operation Context (OC) in-
stance in terms of service availability. This attribute reflects a combination of
the Operation State and the Administrations State (see ‘Administrative State’
on page 75).
Value Description
Active The Administration State of the OC is unlocked

and the collection is active.
Idle The OC is locked.
MA268 • Rev. B1 77
Alarms
Value Description
Not Functional A critical problem occurred implying that the OC

becomes disabled and alarm collection is dis-
abled.
Composite State Explanation

Explains the current Composite State value (see ‘Composite State’ on page 77).
Composite State Change Timestamp

Defines the time of the last Composite State change.
Creation Timestamp
Shows when the operation context was created.
Error Condition Status

Shows the status of the last error that caused the Operational State or Availabil-
ity Status to change (see ‘Operational State’ on page 78 and ‘Availability Sta-
tus’ on page 77).
Monitored By
Shows a list of IDs of the users who have opened the operation context.
Operational State
Shows whether the operation context is working. The operational state is de-
termined by internal conditions within Tellabs 6300 manager.
Value Description
Enabled The operation context is working.

Disabled The operation context is not working.
Note: Alarms are only collected when Operational State is set to Enabled, and
Administrative State is set to Unlocked (see ‘Administrative State’ on
page 75).
Operational State Change Timestamp

Shows the last time the Operational State attribute was changed (see ‘Opera-
tional State’ on page 78).
Purge AO Age
Shows the value of the AO Age parameter (see ‘Purge_alarms’ on page 108).
Purge AO Severity
Shows the value of the Severity parameter (see ‘Purge_alarms’ on page 108).
Purge AO State
Shows the value of the State parameter (see ‘Purge_alarms’ on page 108).
78 MA268 • Rev. B1
Alarms
Purge Begin Time

Shows the value of the Begin Time parameter (see ‘Purge_alarms’ on page
108).
Purge End Time

Shows the value of the End Time parameter (see ‘Purge_alarms’ on page 108).
Purge Error Status

Shows the last error that occurred as a result of an automatic Purge_alarms op-
eration carried out in the background (see ‘Purge_alarms’ on page 108).
Purge Interval
Shows the value of the Interval parameter (see ‘Purge_alarms’ on page 108).
Purge Last Time

Shows when the last automatic Purge_alarms operation was carried out (see
‘Purge_alarms’ on page 108). No value is returned if the last Purge_alarms op-
eration was carried out manually.
Purge Next Time

Shows when the next automatic Purge_alarms operation will be carried out
(see ‘Purge_alarms’ on page 108). No value is returned if Purge Status is set to
Background Purge is Idle.
Purge Status
Shows whether an automatic Purge_alarms operation is running in the back-
ground (see ‘Purge_alarms’ on page 108).
Value Description
Background Purge is Idle No automatic Purge_alarms opera-

tion is running in the background.
Background Purge is Active An automatic Purge_alarms opera-
tion is running in the background.
Resumed By User
Shows the ID of the user who carried out the last Resume operation (see ‘Re-
sume’ on page 108).
Status Condition Explanation

Shows a text describing the last error or event that caused Operational State or
Availability Status to change (see ‘Operational State’ on page 78 and ‘Availabil-
ity Status’ on page 77).
Suspended By User
Shows the ID of the user who carried out the last Suspend operation (see ‘Sus-
pend’ on page 108).
MA268 • Rev. B1 79
Alarms
6.1.5 Counters Attributes for Operation Contexts
Description The Counters attributes for operation contexts describe the current contents of
the alarm log for the operation context in question. Counters are updated
when an alarm is received and when you (or Tellabs 6300 manager) perform
Acknowledge, Terminate, Archive, and Purge_alarms operations (see
‘9.1 Special Operations for Operation Contexts’ on page 107).
You cannot set the Counters attributes of operation contexts.
AO Acknowledged
Shows the number of alarms that have been acknowledged, but not terminat-
ed.
AO Archived
Shows the number of alarms that have been archived, but not purged.
AO Closed
Shows the sum of alarms that have been terminated and archived.
AO Handled
Shows the number of terminated alarms.
AO Not Handled
Shows the number of alarms that have not yet been terminated.
AO Outstanding
Shows the number of alarms that have not yet been acknowledged.
AO Terminated
Shows the number of terminated alarms.
AO Total
Shows the number of alarms found in the alarm log.
6.1.6 Routing Attributes for Operation Contexts
Managing Director
Identifies the server that is responsible for the operation context entity. You
cannot set this attribute.
6.2 Alarm Object Attributes
Introduction The following attribute types are available for alarm objects:
• ‘6.2.1 Identifiers Attributes for Alarm Objects’ on page 81
• ‘6.2.2 Characteristics Attributes for Alarm Objects’ on page 81
• ‘6.2.3 Status Attributes for Alarm Objects’ on page 86
80 MA268 • Rev. B1
Alarms
• ‘6.2.4 Counters Attributes for Alarm Objects’ on page 88
6.2.1 Identifiers Attributes for Alarm Objects
Identifier
Shows the number of the alarm, assigned sequentially within the operation
context. You cannot set this attribute.
6.2.2 Characteristics Attributes for Alarm Objects
Additional Information
Not used.
Additional Text
Shows a text produced by the alarm generator, for instance an NE, to describe
the alarm. You cannot set this attribute.
Alarm Class
Shows whether the alarm is an alarm object or a similar alarm.
Value
AlarmObject
SimilarAlarm
Alarm Object Operator Note

Allows you to assign a user-defined note to the alarm, for instance a descrip-
tion of the circumstances in which the alarms occurred or of actions to be tak-
en. You may use up to 255 characters. Note that you can also set this attribute
by selecting Operation →Set Operator Note... in the Alarm Handling window.
Alarm Origin
Not used.
Alarm Type
Shows the OSI and ITU-T type of the alarm. Example: An NE will generate an
alarm of the CommunicationsAlarm type if transmission problems are detect-
ed, and an alarm of the EquipmentAlarm type if a fault in the transmission
equipment is detected. You cannot set this attribute.
Value
CommunicationsAlarm
EnvironmentalAlarm
EquipmentAlarm
IntegrityViolation
OperationalViolation
MA268 • Rev. B1 81
Alarms
Value
PhysicalViolation
ProcessingErrorAlarm
QualityofServiceAlarm
SecurityServiceOrMechanismViolation
TimeDomainViolation
Backed Up Status
Shows whether the entity from which the alarm originated is backed up by an-
other entity. You cannot set this attribute.
Backup Object
Shows the entity that backs up the entity from which the alarm originated.
You cannot set this attribute.
Correl Notif Info

Applies to clearance alarms. Used in the automatic clearance of alarms. You
cannot set this attribute. It consists of two fields:
• SourceObjectInst
• correlatedNotification
SourceObjectInst
Shows the value(s) of the Managed Object attribute for alarms matched (corre-
lated) with this one.
correlatedNotification
Shows the value of the Notification Identifier attribute for alarms matched (cor-
related) with this one.
Domain
Shows the domain in which the alarm originated, that is the domain contain-
ing the equipment or the alarm rule that generated the alarm. You cannot set
this attribute.
Escalated and Cleared Flag

Shows whether an escalation alarm related to this alarm has been cleared. You
cannot set this attribute.
Value Description
True The alarm has been cleared.

False The alarm has not been cleared.
Event Time
Shows when the alarm was generated, that is the time stamp supplied by the
equipment or by the alarm rule. You cannot set this attribute.
Note: This attribute is updated each time a new similar alarm occurs. The time
of the original alarm is kept in ‘Original Event Time’ on page 83.
82 MA268 • Rev. B1
Alarms
Export Sequence Name

Shows the name of the particular alarm’s archive. You cannot set this at-
tribute.
Export Sequence Number

Shows the sequence number of the particular alarm’s archive. You cannot set
this attribute.
Logical_Operator_And
An operator that forms part of a boolean expression. The default value is and.
Managed Object
Shows the name of the entity from which the alarm originated. This is the en-
tity that is affected by the alarm and that changes color in the map window.
Monitored Attributes
Not used.
Notification Identifier
Shows a number which identifies the alarm for future matching with a clear-
ance alarm. You cannot set this attribute.
OC Name
Shows the full name of the operation context with which the alarm is associ-
ated. You cannot set this attribute.
Original Event Time

Shows the time that the original alarm occurred. You cannot set this attribute.
Original Severity
Shows the original severity of the alarm. You cannot set this attribute.
Parent Alarm Object

Not used.
Perceived Severity
Shows the OSI and ITU-T severity level, assigned to the alarm by the equip-
ment or by the alarm rule that generated it. You cannot set this attribute.
Value Description
Indeterminate The highest severity. Appears in the Sev. col-

umns in the Alarm Handling and the Alarms View
windows as Ind.
Critical The second-highest severity. Appears in the Sev.
columns in the Alarm Handling and the Alarms
View windows as Cri.
MA268 • Rev. B1 83
Alarms
Value Description
Major The third-highest severity. Appears in the Sev.

View windows as Maj.
Minor The third-lowest severity. Appears in the Sev.

View windows as Min.
Warning The second-lowest severity. Appears in the Sev.

View windows as War.
Clear The lowest severity. Appears in the Sev. columns

in the Alarm Handling and the Alarms View win-
dows as Cle.
Probable Cause
Shows the probable cause of the alarm. See Chapter 11 for a complete list of
OSI and ITU-T probable causes. For alarms generated by alarm rules on
SNMP agents, 8 additional probable causes may appear (see ‘Probable Cause’
on page 93). Example: An NE will generate an alarm with the probable cause
LossOfSignal, if a cable rupture occurs. You cannot set this attribute.
Proposed Repair Actions

Not used.
Rule Name
Shows the name of the alarm rule that generated the alarm. You cannot set this
attribute.
Security Alarm Cause

Shows the probable cause of the security alarm.
Security Alarm Detector

Not used.
Service Provider
Not used.
Service User
Not used.
Specific Problems
Describes the probable cause in more detail.
State Change Definition

Not used.
84 MA268 • Rev. B1
Alarms
Target Entities
Shows the names of the entities that will react to the alarm. This is usually the
same entity as Managed Object (see ‘Managed Object’ on page 83). You cannot
set this attribute.
Threshold Info
Applies to alarms generated because a threshold has been exceeded, for in-
stance a threshold specified in the Capacity Alarm Threshold attribute for an
operation context (see ‘Capacity Alarm Threshold’ on page 67). You cannot set
this attribute. It consists of a number of fields showing, for instance, the
threshold in question (triggerThreshold) and the actual value that was ob-
served (observedValue).
Trend Indication
Shows the development of the alarm. You cannot set this attribute.
Value
Less Severe
No Change
More Severe
User Identifier
Identifies the user that created the alarm object. The text is free-form and is de-
fined by the user.
User Text
A free-form text string defined by the user who created the alarm object.
MA268 • Rev. B1 85
Alarms
6.2.3 Status Attributes for Alarm Objects
Description You cannot set the Status attributes for alarm objects.
Acknowledgement Time Stamp

Shows when the alarm was acknowledged for the first time.
Acknowledgement User Identifier

Shows the ID of the user who acknowledged the alarm.
Archive Time Stamp

Shows when the alarm was archived.
Automatic Terminate On Close

Defines the severity level for automatic termination of alarms whose Problem
Status attribute changes to Closed. Alarms with severity less than or equal to
the specified level are automatically terminated when closed.
Value Description
Indeterminate All alarms are automatically terminated when

closed.
are automatically terminated when closed.
jor ones are automatically terminated when
closed.
Warning Warning alarms and clearance alarms are auto-
Clear Clearance alarms are automatically terminated
when closed.
not-automatic No alarms are automatically terminated when
closed.
Clearance Report Flag

Shows whether the alarm has been cleared.
Value Description
True The alarm has been cleared because a matching

alarm of severity Clear has been received.
Clearance Time Stamp

Shows when the alarm was cleared.
86 MA268 • Rev. B1
Alarms
Close Time Stamp

Shows when the alarm was closed.
Close User Identifier

Shows the ID of the first user who closed the alarm.
Closed By
Shows a list of the associated TTRs that have been closed.
Creation Timestamp
Shows when the alarm was created as an object in Tellabs 6300 manager.
Escalated Alarm
Shows whether the alarm has escalated.
Value Description
True The alarm has escalated because it was not ac-

knowledged within the time set in Automatic Es-
calation <severity> Delta Time for the severity in
question (see the description of the correspond-
ing attributes).
Handle Time Stamp

Shows when the alarm was handled for the first time.
Handled By
Shows the TTR (or list of TTRs) with which the alarm is associated.
Handled User Identifier

Shows the ID of the first user who handled the alarm.
Problem Status
Shows the status of the problem.
Value Description
Not-Handled The problem has not been handled.

Handled The problem has been handled but not yet closed.
Closed The problem has been closed.
Release Time Stamp

Shows when the alarm was released from association with TTRs for the first
time.
Release User Identifier

Shows the ID of the first user who released the alarm from association with
TTRs.
MA268 • Rev. B1 87
Alarms
State
Shows the state of the alarm.
Value Description
Outstanding The alarm has not been acknowledged.

Acknowledged The alarm has been acknowledged but not yet
terminated.
Terminated The alarm has been terminated but not yet ar-
chived.
Archived The alarm has been archived.
Termination Time Stamp

Shows when the alarm was terminated.
Termination User Identifier

Shows the ID of the user who terminated the alarm.
6.2.4 Counters Attributes for Alarm Objects
Description The Counters attributes for alarm objects describe how many alarms of a sim-
ilar type that have been received.
Clear Problem Occurrences

Shows the total number of clearance alarms (severity Clear) that have been re-
ceived for the same problem.
Critical Problem Occurrences

Shows the total number of alarms with the severity Critical that have been re-
Indeterminate Problem Occurrences

Shows the total number of alarms with the severity Indeterminate that have
been received for the same problem.
Major Problem Occurrences

Shows the total number of alarms with the severity Major that have been re-
Minor Problem Occurrences

Shows the total number of alarms with the severity Minor that have been re-
Problem Occurrences
Shows the total number of alarms that have been received for the same prob-
lem.
88 MA268 • Rev. B1
Alarms
SA Total
Shows the current number of similar alarms associated with the alarm object.
Warning Problem Occurrences

Shows the total number of alarms with the severity Warning that have been re-
MA268 • Rev. B1 89
Alarms
90 MA268 • Rev. B1
Tellabs® 6300 Network Manager 7 Alarm Rule Attributes
Alarms
7 Alarm Rule Attributes
Overview This chapter describes the attributes for the alarm rule entity. This entity is
used to help equipment generate alarms, as described in ‘2.1.2 The Alarm
Rule’ on page 22.
Most alarm rule attributes are conveniently contained in a special alarm rule
attribute group named Rule attributes as well as in the usual attribute groups.
The only exception is the Status attribute Error Entity (see ‘Error Entity’ on
page 99). Therefore, an alarm rule is most easily shown and modified by using
Show and Set with the Rule attributes group.
7.1 Attributes for Registration
Domain
Determines to which domain the alarm rule applies. Set the attribute to the
name of the domain.
<Alarm Rule Type>

The field name reflects the selected alarm rule type (Change of Rule, Compari-
son Rule, Expression Rule, Occurs Rule and Occurs N Time Rule).
Allows you to enter a unique name for the alarm rule. Use a descriptive name
to easily identify the alarm rule.
Rules for entity names The following rules apply to entity names:
• The name must be unique among all global entities.
• The maximum length of an entity name is 511 characters.
• The following characters are allowed:
• !$-_0123456789
• abcdefghijklmnopqrstuvwxyz
• ABCDEFGHIJKLMNOPQRSTUVWXYZ
• If Tellabs 6300 manager is configured to support special national charac-
ters, an extended set of characters can be used, for instance special Scandi-
navian characters such as æ, ø and å.
• If the entity name is enclosed in quotation marks (“ “), an extended set of
characters can be used, for instance spaces, if you want to break the name
into multiple words. The following characters can be used:
• #%&’()*+,./:;<=>?@[\]^{|}~
Nick Name
Allows you to specify a descriptive name for the alarm rule icon.
A nick name can be defined during registration of an entity. If you define a
nick name, this name appears below the entity icon in the map window in-
stead of the entity name. This is useful if your network plan uses abbreviated
names and you want to show more descriptive names in the map window.
Note: The nick name is not an attribute. It is associated with the entity icon in
the map window in which the entity was created. If the entity is regis-
MA268 • Rev. B1 91
Alarms
tered in two domains, it may have different nick names in the two map
windows. Therefore, you cannot show or set the nick name using the
Show and Set operations. If you need to change the nick name after reg-
istration, use the Change Entity Attributes... item in the pop-up menu.
Severity
Determines the OSI and ITU-T severity level that is assigned to alarms that are
generated when the alarm rule is fulfilled.
Value Description
Indeterminate The highest severity. Appears in the Sev. col-

umns in the Alarm Handling and the Alarms View
windows as Ind.
Critical The second-highest severity. Appears in the Sev.
View windows as Cri.
Major The third-highest severity. Appears in the Sev.

View windows as Maj.
Minor The third-lowest severity. Appears in the Sev.

View windows as Min.
Warning The second-lowest severity. Appears in the Sev.

View windows as War.
Clear The lowest severity. Appears in the Sev. columns

in the Alarm Handling and the Alarms View win-
dows as Cle.
Auto Enable
Determines whether the alarm rule is enabled automatically when it is creat-
ed. Later you can disable and enable it using the Disable and Enable opera-
tions (see ‘9.2 Special Operations for Alarm Rules’ on page 112).
Value Description
Yes The alarm rule is working immediately.

No The alarm rule is not working until an Enable op-
eration is performed.
Category
Determines whether the alarm rule belongs to a user-defined group. Set the
attribute to the name of the group.
Description
Allows you to assign a user-defined note describing the alarm, for instance a
description of the circumstances in which the alarms occurred or of actions to
be taken. You may use up to 255 characters.
92 MA268 • Rev. B1
Alarms
Alarm Fired Procedure

Specifies a script which is executed if the alarm fires. The script is typically
made by the system manager (see [7]).
Alarm Fired Parameters

Not used.
Alarm Exception Procedure

Not used.
Event Type
Assigns a predefined alarm type to the alarms generated by the alarm rule.
Note: This attribute is not implemented. All alarms generated by alarm rules
have Alarm Type set to QualityofServiceAlarm (see ‘Alarm Type’ on page
81).
Value
CommunicationsAlarm
EnvironmentalAlarm
EquipmentAlarm
ProcessingErrorAlarm
QualityofServiceAlarm
Probable Cause
Defines the text to be displayed, for instance, in the Alarm Handling window,
as the probable cause of the alarm. The allowed probable causes form a subset
of the OSI and ITU-T probable causes, which are listed in Appendix A.
Value
Unknown
AdapterError
ApplicationSubsystemFailure
BandwidthReduced
CallEstablishmentError
CommunicationsProtocolError
CommunicationsSubsystemFailure
ConfigurationOrCustomizationError
Congestion
CorruptData
CpuCyclesLimitExceeded
DataSetOrModemProblem
MA268 • Rev. B1 93
Alarms
Value
DegradedSignal
DTE-DCEInterfaceError
EnclosureDoorOpen
EquipmentMalfunction
ExcessiveVibration
FileError
FireDetected
FloodDetected
FramingError
HeatingOrVentilationOrCoolingSystemProblem
HumidityUnacceptable
InputOutputDeviceError
InputDeviceError
LANError
LeakDetected
LocalNodeTransmissionError
LossOfFrame
LossOfSignal
MaterialSupplyExausted
MultiplexerProblem
OutofMemory
OutputDeviceError
PerformanceDegraded
PowerProblem
PressureUnacceptable
ProcessorProblem
PumpFailure
QueueSizeExceeded
ReceiveFailure
ReceiverFailure
RemoteNodeTransmissionError
ResourceAtOrNearingCapacity
ResponseTimeExcessive
94 MA268 • Rev. B1
Alarms
Value
RetransmissionRateExcessive
SoftwareError
SoftwareProgramAbnormallyTerminated
SoftwareProgramError
StorageCapacityProblem
TemperatureUnacceptable
ThresholdCrossed
TimingProblem
ToxicLeakDetected
TransmitFailure
TransmitterFailure
UnderlyingResourceUnavailable
VersionMismatch
SnmpTrapColdStart
SnmpTrapWarmStart
SnmpTrapLinkDown
SnmpTrapLinkUp
SnmpTrapAuthenticationFailure
SnmpTrapEgpNeighborloss
SnmpTrapEnterpriseSpecific
SnmpTrapLinkUpDown
Rule Expression
Not used. Applies to expression rules only.
Start Time
Does not apply to expression rules. Determines when the monitoring of the
entity will start. The default setting is now. The format is yyyy-mm-dd-
hh:mm:ss.
Example: 1997-07-30-16:00:00
End Time
Does not apply to expression rules. Determines when the monitoring of the
entity will stop. The default setting is never. The format is yyyy-mm-dd-
hh:mm:ss.
Example: 1997-08-31-16:00:00
MA268 • Rev. B1 95
Alarms
Polling Interval
Applies to change of rules and comparison rules only. Determines the interval
between two subsequent data readings. The default setting is 15 minutes. The
format is hh:mm:ss.
Example: 00:30:00
Duration Interval
Applies only to comparison rules collecting statistics. Determines the length
of time to collect statistics. The default setting is one minute. The format is
hh:mm:ss.
Example: 00:02:00
Entity
Does not apply to expression rules. Determines to which global entity the
alarm rule applies. Specify the full name (including the entity group) or use a
wildcard.
Example: AC1_30 ac1_1
Attribute Name
Applies to change of rules and comparison rules only. Determines which at-
tribute is monitored.
Example: equipment module aggr_pos_3 laser temperature
Relational Operator
Applies to comparison rules only. Determines the relational operator of the
comparison.
Value Description
EQ Equal to
LT Less than
GT Greater than
LE Less than or equal to
GE Greater than or equal to
NE Not equal to
Comparison Values
Applies to change of rules only. Determines how the attribute is required to
change to generate an alarm. Specify a combination of value(s) and wild-
card(s).
Value Description
value,value Generates an alarm when the attribute changes

from the first specified value to the second.
value,* Generates an alarm when the attribute changes
from the specified value to any other value.
96 MA268 • Rev. B1
Alarms
Value Description
*,value Generates an alarm when the attribute changes

from any value to the specified value
*,* Generates an alarm when the attribute changes
from any value to any other value.
Comparison Value
Applies to comparison rules only. Determines the constant value that the at-
tribute value is compared to.
Event Name
Applies to occurs rules and occurs n time rules only. Determines which event
is monitored.
Example: For a rule on an SNMP (Simple Network Management Protocol)
agent, the possible event names are:
Value
COLDSTART
WARMSTART
LINKDOWN
LINKUP
AUTHENTICATIONFAILURE
EGPNEIGHBORLOSS
ENTERPRISESPECIFIC
IPREACHABILITYUP
IPREACHABILITYDOWN
Count
Applies to occurs n time rules only. Specifies the number of times the moni-
tored event must occur within the time period specified by Delta Time to gen-
erate an alarm (see ‘Delta Time’ on page 97).
Example: 3 (with Delta Time set to 01:00:00, the event must occur three times
within one hour).
Delta Time
Applies to occurs n time rules only. Specifies the time period during which the
monitored event should occur the number of times specified by Count to gen-
erate an alarm (see ‘Count’ on page 97).
Example: 01:00:00 (with Count set to 3, the event should occur three times
within one hour).
MA268 • Rev. B1 97
Alarms
7.2 Identifiers Attributes
Description The Identifiers attribute for alarm rules is also contained in the Alarm Rules at-
tribute group.
Name
Shows the Tellabs 6300 manager name of the alarm rule. You cannot set this
attribute.
7.3 Characteristics Attributes
Description All Characteristics attributes for alarm rules are also contained in the Alarm
Rules attribute group.
Alarm Exception Procedure

Not used.
Alarm Fired Parameters

Not used.
Alarm Fired Procedure

Specifies a script which is executed if the alarm fires. The script is typically
made by the system manager (see [7]).
Category
Determines whether the alarm rule belongs to a user-defined group (see ‘Cat-
egory’ on page 92). Not shown if it has no value.
Description
Allows you to attach a note to the alarm rule (see ‘Description’ on page 92).
Not shown if it has no value.
Expression
Defines the expression used to evaluate the rule. There are four types of ex-
pressions, namely change of rules, comparison rules, occurs rules and occurs
n time rules. Refer to [10] for details on the proper syntax of alarm rule expres-
sions.
Probable Cause
Defines the text to be displayed, for instance, in the Alarm Handling window,
as the probable cause of the alarm (see ‘Probable Cause’ on page 93).
Severity
Determines the OSI and ITU-T severity level that is assigned to alarms that are
generated when the alarm rule is fulfilled (see ‘Severity’ on page 92).
98 MA268 • Rev. B1
Alarms
7.4 Status Attributes
Description All Status attributes for alarm rules, except Error Entity, are also contained in
the Alarm Rules attribute group. They cannot be set.
Warning: There is a set of Status attributes for each user. This means, for in-
stance, that an alarm rule may be enabled by someone else, even
though it appears to you as disabled in a Show Status operation (see
‘State’ on page 100). If you enable an alarm rule that is already en-
abled, alarms due to this rule will be duplicated and appear twice.
Current Severity
Shows a severity determined by Result of Last Evaluation (see page 99) and Se-
verity (see page 92).
Value Description
Indeterminate Either Result of Last Evaluation is Error, or Result

of Last Evaluation is True and Severity is Indeter-
minate.
Critical Result of Last Evaluation is True and Severity is

Critical.
Major Result of Last Evaluation is True and Severity is

Major.
Minor Result of Last Evaluation is True and Severity is Mi-

nor.
Warning Result of Last Evaluation is True and Severity is

Warning.
Clear Either Result of Last Evaluation is False, or Result

of Last Evaluation is True and Severity is Clear.
Disable Time
Only present if the alarm rule has been disabled. Shows when this happened.
Error Condition
Only present if an error occurred during evaluation of the alarm rule expres-
sion. Holds an error message.
Error Entity
Holds the Tellabs 6300 manager name of the equipment monitored by the
alarm rule. This attribute is not contained in the Alarm Rules attribute group.
Result of Last Evaluation

Shows the result of the last evaluation of the alarm rule expression.
Value Description
True The alarm rule was fulfilled and an alarm was

generated.
MA268 • Rev. B1 99
Alarms
Value Description
False The alarm rule was not fulfilled and no alarm

was generated.
Error An error occurred in the evaluation.
State
Shows whether the alarm rule is working.
Value Description
Enabled The alarm rule is working, either as the result of

an Enable operation, or because Auto Enable (see
page 92) was set to Yes at registration.
Disabled The alarm rule is not working, either as the result
of a Disable operation, or because Auto Enable
(see page 92) was set to No at registration.
Substate
Gives further information about the state of the alarm rule.
Value Description
Running The alarm rule is working, either as the result of

an Enable operation, or because Auto Enable (see
page 92) was set to Yes at registration.
Disabled by user action The alarm rule is not working, either as the result
of a Disable operation, or because Auto Enable
(see page 92) was set to No at registration.
Time of Last Evaluation

Shows when the alarm rule expression was last evaluated.
7.5 Counters Attributes
Description All Counters attributes for alarm rules are also contained in the Alarm Rules
attribute group. They cannot be set.
Creation Timestamp
Holds the time for the creation of the alarm rule.
Evaluation Error
Counts the number of times that the evaluation of the alarm rule expression
has resulted in an error, since the alarm rule was last enabled. To reset the at-
tribute, perform a Disable operation followed by an Enable operation.
100 MA268 • Rev. B1

Alarms
Evaluation False
Counts the number of times that the alarm rule expression has been evaluated
to the value False, since the alarm rule was last enabled. To reset the attribute,
perform a Disable operation followed by an Enable operation.
Evaluation True
Counts the number of times that the alarm rule expression has been evaluated
to the value True, that is the number of times the alarm rule has fired, since the
alarm rule was last enabled. To reset the attribute, perform a Disable operation
followed by an Enable operation.
MA268 • Rev. B1 101

Alarms
102 MA268 • Rev. B1

Tellabs® 6300 Network Manager 8 Alarm Rules for System Monitoring
Alarms
8 Alarm Rules for System Monitoring
Overview This chapter describes the attribute values for various Tellabs 6300 manager
alarms received during self-monitoring.
8.1 Introduction
Alarm recognition Tellabs 6300 manager monitors itself on a number of points to guarantee that
it is working properly. Key aspects of computer hardware, computer software
and of the data communication network are monitored. You can recognize a
Tellabs 6300 manager alarm by its values for the following attributes:
• Managed Object. Appears as Managed Object in the Real Time View win-
dow.
• Perceived Severity. Appears as Sev. in the Real Time View window.
• Alarm Type. Appears as Type in the Real Time View window.
• Probable Cause. Appears as Cause in the Real Time View window.
• Additional Text. Appears as Text in the Real Time View window.
8.2 Computer Hardware Alarms
Introduction Often, the computer hardware of Tellabs 6300 manager cannot generate
alarms itself. Therefore, it is monitored by means of alarm rules, which recur-
rently check key parameters. If severe deviations from desired values are
found, alarms are generated.
All computer hardware alarms will appear in the oc_sys_man operation con-
text since the alarm rules for computer hardware are placed in the sys_man
domain (and subdomains thereof).
8.2.1 Alarm Rules for SNMP Entities
Description All SNMP entities of the sys_man domain can be monitored using the IP Pol-
ler entity which by default is registered in this domain. The IP Poller polls all
SNMP entities for IP reachability every 60 seconds. An IP Poller alarm is au-
tomatically cleared when the SNMP entity is reachable again.
Attribute values The table shows the attribute values of the IP Poller alarms.
Attribute Value
Managed Object SNMP <entity name>

(Example: SNMP LOCAL_NS:.ncd1)
Perceived Severity Critical
Alarm Type CommunicationsAlarm
Probable Cause CommunicationsSubsystemFailure
MA268 • Rev. B1 103

Alarms
Attribute Value
Additional Text “IP Reachability Down ICMP ping failed on previ-

ously reachable entity. IP-Address = <IP-addr>”
8.2.2 Alarm Rules for Bridge LAN Interfaces
Description A bridge has two interfaces: an interface for the local area network (Ethernet)
and an interface for transmitting Ethernet traffic on a 2 Mbit/s leased line.
Alarm rules for supervision of the Ethernet local area network are found in the
sys_man domain.
Attribute values The table shows the attribute values of the Ethernet LAN alarms.
Attribute Value
Managed Object SNMP <bridge name> INTERFACE 1

(Example: SNMP brouter1 INTERFACE 1)
Perceived Severity Major
Alarm Type QualityOfServiceAlarm
Probable Cause LANError
Additional Text Ethernet degraded
8.2.3 Alarm Rules for Bridge Leased Lines Interfaces
Description A bridge has two interfaces: an interface for the local area network (Ethernet)
and an interface for transmitting Ethernet traffic on a 2 Mbit/s leased line.
Alarm rules for supervision of LAN-interconnecting leased lines are found in
the sys_man domain.
Attribute values The table shows the attribute values of the Ethernet leased lines alarms.
Attribute Value
Managed Object SNMP <bridge name> INTERFACE 2

(Example: SNMP brouter1 INTERFACE 2)
Perceived Severity Major
Probable Cause LossOfSignal
Additional Text Leased line interface on brouter lost
104 MA268 • Rev. B1

Alarms
8.2.4 Alarm Rules for Disk Storage
Description The disk storage of Tellabs 6300 manager is divided into a number of disk do-
mains. Each disk domain stores characteristic information, for instance pro-
gram files of Tellabs 6300 manager or alarm reports.
Each disk domain is monitored by an alarm rule, generating an alarm when
the disk domain is 95% full. The alarm rules are found in the computersystem
domain.
Attribute values The table shows the attribute values of the disk storage alarms.
Attribute Value
Managed Object Script .disks mcc_df <disk name>

(Example: Script .disk mcc_df /usr)
Perceived Severity Minor
Probable Cause StorageCapacityProblem
Additional Text Partition <disk name> more than 95% full

(Example: Partition /usr more than 95% full)
Note: The term partition is used for disk domain in the Additional Text at-
tribute.
8.3 Computer Software Alarms
Introduction Tellabs 6300 manager is based on software components that are able to detect
many different kinds of errors and violations. Appropriate error messages
will be displayed if errors are detected during operation.
• An alarm log is nearly full (see Section 8.3.1).
• No network operator or other Tellabs 6300 manager user seems to re-
spond to alarms in a certain operation context (see Section 8.3.2).
Both types of alarms will appear in the oc_man_env operation context.
8.3.1 Alarm Rules for Alarm Logs
Description If an alarm log is getting nearly full, alarms with increasing severity may be
generated. The number of alarms, and when they are generated, are deter-
mined by the Capacity Alarm Threshold attribute (see page 67). A maximum of
four alarms may be generated, ranging from Warning to Critical.
Attribute values The table shows the attribute values of the alarm log alarms.
Attribute Value
Managed Object OPERATION_CONTEXT <operation context name>

(Example: OPERATION_CONTEXT oc_nwlms_test)
MA268 • Rev. B1 105

Alarms
Attribute Value
Perceived Severity Not fixed
Alarm Type ProcessingErrorAlarm
Probable Cause StorageCapacityProblem
Additional Text
8.3.2 Alarm Rules for Alarm Escalation
Description If an alarm is not acknowledged within a certain fixed time, a new alarm may
be generated to notify, for instance, a management headquarter that some-
thing may be wrong.
Attribute values The table shows the attribute values of the alarm escalation alarms.
Attribute Value
Managed Object OPERATION_CONTEXT <operation context name>

alarm object <alarm Id>
(Example: OPERATION_CONTEXT oc_vc4_net2
alarm object 1039)
Perceived Severity Not fixed
Probable Cause ResponseTimeExcessive
Additional Text
Note: This alarm occurs only if your Tellabs 6300 manager includes the alarm
escalation function.
106 MA268 • Rev. B1

Tellabs® 6300 Network Manager 9 Operations
Alarms
9 Operations
Overview This chapter describes the special operations and their parameters for the en-
tities connected to alarms. Default parameter values, if any, are either men-
tioned in the text or indicated in the tables by underscore.
9.1 Special Operations for Operation Contexts
Overview The following operations are described:

• ‘Register’ on page 107
• ‘Directory’ on page 107
• ‘Resume’ on page 108
• ‘Suspend’ on page 108
• ‘Purge_alarms’ on page 108
• ‘Cancel_purge’ on page 110
• ‘Archive’ on page 110
• ‘Cancel_archive’ on page 112.
Register
Description Registers an operation context that has previously been partially registered.
Managing Director
Specifies the managing director for the selected operation context.
Operation
Determines whether the registration will be completed (if possible) or forced
to be partial.
Value Description
COMPLETE The registration will be completed, if possible.

This is the normal setting.
PLAN The registration will only be partial. You cannot
perform management operations on the entity
until the registration has been completed.
Directory
Description Shows the name of the selected operation context.
MA268 • Rev. B1 107

Alarms
Resume
Description Resumes alarm collection for the selected operation context.
Suspend
Description Suspends alarm collection for the selected operation context.
Purge_alarms
Description Permanently removes alarms of a certain age and severity from the alarm log.
Therefore, you cannot access purged alarms from the Alarms View window.
The age and severity are determined by the AO Age and Severity parameters.
Alarm purging can be performed manually or can be set up to be performed
automatically (as a background process), for instance every day at 02:00. You
set up background alarm purging by specifying one or more of the time pa-
rameters Begin Time, End Time and Interval. If the three time parameters are all
left blank, a single, manual alarm purging is performed.
If you set up automatic purging, it is recommended that you set the State pa-
rameter to Archived in order to ensure that alarms are not purged before they
are archived.
Note: As default, automatic purging of all terminated alarms older than 60
days is set up to be performed once a day.
Note: A running (automatic) Purge_alarms operation cannot be modified. Use
the Cancel_purge operation (see page 110) followed by a new
Purge_alarms operation to modify a background alarm purging pro-
cess. The current state of a background alarm purging process can be
examined with a Show operation performed on the Status attributes of
the operation context in question.
Note: You do not have to use the Purge_alarms operation to set up an auto-
matic purge process. Instead, you can set the Purge parameter of the Ar-
chive operation to True. This will cause alarms to be purged when they
have been archived.
AO Age
Defines an age limit for purging. Alarms older than the specified age will be
purged, provided the Severity and State conditions are fulfilled. The format is
dd-hh:mm:ss. The default setting is 0, requiring no age for an alarm to be
purged.
Example: 45-00:00:00
Severity
Defines the severity level for purging. Alarms with severity less than or equal
to the specified level will be purged, provided the AO Age and State condi-
tions are fulfilled. The default setting is none, in which case all alarms fulfill-
ing the AO Age and State conditions are purged.
Value Description
Indeterminate All alarms will be purged.
108 MA268 • Rev. B1

Alarms
Value Description
Critical All alarms except indeterminate ones will be

purged.
will be purged.
jor ones will be purged.
Warning Warning alarms and clearance alarms will be
purged.
Clear Clearance alarms will be purged.
State
Determines which alarms fulfilling the specified Severity and AO Age condi-
tions will be purged.
Value Description
Terminated All terminated alarms fulfilling the conditions

will be purged whether they are archived or not.
Archived Only archived alarms fulfilling the conditions
will
be purged.
Begin Time
Determines when the alarm purging operation starts. If specified, an automat-
ic alarm purging process will be set up in the background (see the introduc-
tion to this section). The format is yyyy-mm-dd, hh:mm:ss or yyyy-mm-dd-
hh:mm:ss. If the date part is omitted, the current date is used; if the time part is
omitted, purging starts at midnight. The default setting is now.
Example: 1997-05-15-10:30:00
End Time
Determines when the alarm purging operation stops. If specified, an automat-
ic alarm purging process will be set up in the background (see the introduc-
tion to this section). The format is yyyy-mm-dd, hh:mm:ss or yyyy-mm-dd-
hh:mm:ss. If the date part is omitted, the current date is used; if the time part is
omitted, purging stops at midnight. The default setting is December 31st 9999.
Example: 1997-06-15-10:30:00
Interval
Specifies the interval between two subsequent alarm purging operations for
an automatic background alarm purging process. If specified, an automatic
alarm purging process will be set up in the background (see the introduction
to this section). The format is dd-hh:mm:ss. The minimum permitted interval is
1 minute. The default setting is one day.
Example: 0-01:00:00
MA268 • Rev. B1 109

Alarms
Cancel_purge
Description Cancels automatic alarm purging for the selected operation context. See
‘Purge_alarms’ on page 108.
Archive
Description Archives terminated alarms of a certain age and severity in an external data-
base. The age and severity are determined by the AO Age and Severity param-
eters.
Archiving can be performed manually or can be set up to be performed auto-
matically (as a background process), for instance every 24 hours. You set up
background archiving by specifying one or more of the time parameters Begin
Time, End Time and Interval. If the three time parameters are all left blank, a
single, manual archiving is performed.
Note: As default, automatic archiving of all Critical and Major alarms older
than 2 weeks is set up to be performed once a day.
Note: Before you perform an Archive operation, be sure that the system man-
ager has initialized a database for archiving alarms, see [4].
Note: A running (automatic) Archive operation cannot be modified. Use the
Cancel_archive operation (see page 112) followed by a new Archive op-
eration to modify a background archiving process. The current state of
a background archiving process can be examined with a Show opera-
tion performed on the Status attributes of the operation context in ques-
tion.
database name
Specifies the name of the database into which alarms are to be archived. Use
only database names in accordance with the established convention in your
setting. The default setting is temip_ah.
Sequence Name
Specifies the name of the current archive. Use only sequence names in accor-
dance with the established convention in your setting. The default setting is
oc_archive.
Sequence Number
Specifies the sequence number of the current archive. Use only sequence num-
bers in accordance with the established convention in your setting. The de-
fault setting is 0.
AO Age
Defines an age limit for archiving. Alarms older than the specified age will be
archived, provided the Severity condition is fulfilled. The format is dd-
hh:mm:ss. The default setting is 0, requiring no age for an alarm to be archived.
Example: 7-00:00:00
Severity
Defines the severity level for archiving. Alarms with severities greater than or
equal to the specified level will be archived, provided the AO Age condition is
110 MA268 • Rev. B1

Alarms
fulfilled. The default setting is none, in which case all terminated alarms ful-
filling the AO Age condition are archived.
Value Description
Indeterminate Indeterminate alarms will be archived.

Critical Indeterminate and critical alarms will be ar-
chived.
Major Major, critical and indeterminate alarms will be
archived.
Minor All alarms except warning and clearance alarms
will be archived.
Warning All alarms except clearance alarms will be ar-
chived.
Clear All alarms will be archived.
Purge
Determines whether alarms will be purged automatically from the alarm log
when archived.
Value Description
False Alarms are not automatically purged.

True Alarms are automatically purged.
Begin Time
Determines when the archiving operation starts. If specified, an automatic ar-
chiving process will be set up in the background (see the introduction to this
section). The format is yyyy-mm-dd, hh:mm:ss or yyyy-mm-dd-hh:mm:ss. If
the date part is omitted, the current date is used; if the time part is omitted,
archiving starts at midnight. The default setting is now.
Example: 1997-05-15-10:30:00
End Time
Determines when the archiving operation stops. If specified, an automatic ar-
chiving process will be set up in the background (see the introduction to this
section). The format is yyyy-mm-dd, hh:mm:ss or yyyy-mm-dd-hh:mm:ss. If
the date part is omitted, the current date is used; if the time part is omitted,
archiving stops at midnight. The default setting is December 31st 9999.
Example: 1997-05-15-10:30:00
Interval
Specifies the interval between two subsequent archiving operations for an au-
tomatic background archiving process. If specified, an automatic archiving
process will be set up in the background (see the introduction to this section).
The format is dd-hh:mm:ss. The minimum permitted interval is 1 minute. The
default setting is one day.
Example: 0-01:00:00
MA268 • Rev. B1 111

Alarms
Cancel_archive
Description Cancels automatic alarm archiving for the selected operation context. See Ar-
chive in Section 29.3.7.
9.2 Special Operations for Alarm Rules

• ‘Copy’ on page 112
• ‘Disable’ on page 112
• ‘Enable’ on page 112.
Copy
Description Copies the selected alarm rule into the same or another domain. You specify
the target domain in the New Domain Name parameter. The target may be an
existing domain or a new domain. Refer to [9] for further information on the
Copy operation.
Modify Copied Rule

Allows you to modify the attributes of the alarm rule copy before it is placed
in the target domain.
Value Description
No The attributes are not modified. Note that you

can modify them later using the Set operation.
Yes You can modify the attributes in the management
window that appears when you have started the
Copy operation.
New Domain Name

Specifies the domain into which the alarm rule will be copied. The default set-
ting is the current domain.
New Rule Name

Specifies the name of the new alarm rule.
Disable
Description Disables an alarm rule.
Enable
Description Enables an alarm rule.
112 MA268 • Rev. B1

Alarms
9.3 Special Operations for Alarm Objects

• ‘Summarize’ on page 113
• ‘Acknowledge’ on page 113
• ‘Terminate’ on page 113.
Summarize
Description Not used.
Acknowledge
Description Acknowledges the selected alarm(s).
Terminate
Description Terminates the selected alarm(s). The alarm(s) will be removed from the alarm
information list in the Alarm Handling window, but they can be studied in the
Alarms View window.
MA268 • Rev. B1 113

Alarms
114 MA268 • Rev. B1

Tellabs® 6300 Network Manager 10 Alarm Text Descriptions
Alarms
10 Alarm Text Descriptions
Overview Here the individual alarms of the Tellabs 6300 manager are described. The
alarms are sorted alphabetically by their alarm text.
Actual module not expected

Appears when the actual module in question is present but not expected.
Actual transceiver not expected

Appears when the actual transceiver in question is present but not expected.
Air compressor failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Air com-
pressor failure is selected in the Input Alarm Text: drop-down list for the auxil-
iary port in question. Appears when the signal on the port is high or low de-
pending on the value selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to Air compressor failure. Appears when the signal on the
port is high or low depending on the setting of Polarity.
Air conditioning failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Air condi-
tioning failure is selected in the Input Alarm Text: drop-down list for the auxil-
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Air conditioning failure. Appears when the signal on the
Air dryer failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Air dryer
failure is selected in the Input Alarm Text: drop-down list for the auxiliary port
in question. Appears when the signal on the port is high or low depending on
the value selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Air dryer failure. Appears when the signal on the port is
high or low depending on the setting of Polarity.
AIS
Appears when an AIS is detected in the signal.
MA268 • Rev. B1 115

Alarms
AIS insertion forced

This alarm indicates that an AIS is forced into the corresponding signal.
Alarm received from NE in illegal format

Appears when an invalid alarm message is received from the NE.
Note: This alarm is not cleared automatically. You must clear it manually.
Alarm surveillance disabled

Appears when alarm surveillance has been disabled for the NE in question.
This alarm indicates that no alarms are reported from the NE.
Ambient high temperature

Appears when the ambient air temperature of one of the fan modules increas-
es above the upper high temperature threshold specified in the Subrack
[<Rack ID>-<Subrack ID>] Power and Temperature window. The alarm is
cleared when the temperature decreases below the upper low temperature
threshold.
APS architecture mismatch

Appears when the switching type is bidirectional, and the value of the re-
ceived architecture indication, K2[5], has not matched the architecture to
which the NE is configured, for more than 50 ms. The alarm is cleared when
the received architecture indication and the configured architecture match
again.
APS default signalling

Appears when the values of all the APS signalling attributes of the Incoming
APS Signalling window has been 0 for more than 60 seconds. This indicates
that an NE exists in the ring, for which the value of the Current Mode: field in
the Operate MS-SPRing window is Init.
APS FOP, received default code (slot <1, 6>)

Appears when the received APS signalling contains the default APS code for
more than 60 seconds. The purpose of FOP is to detect nodes in the ring that
do not have the MS-SPRing function activated (or still have Operation Mode set
to Init after MS-SPRing has been activated). The rather long detection time has
been set in order not to detect FOPs when a neighboring node is booting (fol-
lowing, for instance, a power-on) during which time the actual APS signalling
out of that node cannot be guaranteed. The alarm is detected per interface
(East (slot 6) and West (slot 1)). FOP detection is disabled while SSF (for the
relevant direction) is active.
Note: This alarm can be caused by:
• An operator forgetting to activate all the nodes in an MS-SPRing ring
• An operator forgetting to set Operation Mode to Normal for all nodes
• A neighboring node taking too long to boot
APS FOP, received node ID (slot <1, 6>)

Appears when the destination node ID or source node ID in a received APS
message does not correspond to a node present in the ring (according to the
node map stored in the connection function's APS processor) for more than 2.5
seconds. The alarm is detected per interface (East (slot 6) and West (slot 1)).
FOP detection is disabled while SSF (for the relevant direction) is active.
116 MA268 • Rev. B1

Alarms
Note: This alarm can be caused, for example, by faulty configuration of a node
map.
APS FOP, received request code (slot <1, 6>)

Appears when an illegal bridge request code is being received for more than
2.5 seconds. Illegal codes are: 0010, 0100, 0111, 1001, 1010, 1100, 1110. The
alarm is detected per interface (East (slot 6) and West (slot 1)). FOP detection
is disabled while SSF (for the relevant direction) is active.
Note: This alarm is not caused by any operator error, but its likely cause is an
equipment fault in the MS-SPRing function in a node in the ring.
APS FOP, switching state (slot <1, 6>)

Appears when the APS signalling does not work correctly, because the node
APS controller stays in one of the following states for more than 2.5 seconds:
• the bridged state, irrespective of incoming signalling
• the bridged and switched state, while either idle or bridged status is re-
ceived from the NE at the far end
The direction indication for this alarm is that corresponding to a bridge re-
quest that would produce the bridge/switch state in which the node stays for
too long. Hence, the actual physical bridging/switching occurs in the module
opposite the direction indication.
APS FOP, time-out (slot <1, 6>)

Appears when the APS signalling does not work correctly, because the port in
question has not received a valid response to a signalled switch (or Exercise)
request within 2.5 seconds. In most cases the response should originate from
the NE at the far end, but in cases with multiple requests in a ring, a valid re-
sponse could originate from another NE. The alarm is detected per interface
(East (slot 6) and West (slot 1)).
APS FOP, unstable signalling (slot <1, 6>)

Appears when one of the APS signalling channels is declared unstable. That
is, if 3 identical sets of values of bits 1 to 5 of the K1 and K2 bytes are not re-
ceived within 8 consecutive frames. The alarm is detected per interface (East
(slot 6) and West (slot 1)).
APS illegal node ID

question has received an illegal node ID (not present in the ring node map) in
bits 5 to 8 of the K1 byte or in bits 1 to 4 of the K2 byte.
APS illegal request

Appears for MS-SPRing protection when the APS signalling does not work
correctly, because the port in question has received an illegal switch request
code in bits 1 to 4 of the K1 byte.
MA268 • Rev. B1 117

Alarms
Appears for MSP 1+1 protection when the switching type is bidirectional, and
an illegal request code is received consistently.
APS illegal state

question stays in one of the following states for more than 2.5 seconds:
• the bridged state, irrespective of the received signalling
• the bridged and switched state, while either idle or bridged status is re-
ceived from the NE at the far end
APS inappropriate request

Appears when the switching type is bidirectional, and an inappropriate re-
quest code is received consistently. Appropriate codes are requests with the
same or higher priority than the local request, or the Reverse request in re-
sponse to the Exercise request or requests with higher priority than that.
APS selector mismatch

Appears when the switching type is bidirectional, and a mismatch between
the received local bridged signal number and the sent request signal number
persists for more than 50 ms.
APS timeout
question has not received a valid response to a switch request within 2.5 sec-
onds. In most cases the response should originate from the NE at the far end,
but in cases with multiple requests in a ring, a valid response could originate
from another NE.
APS unstable
Appears for MS-SPRing protection when one of the APS signalling channels
is declared unstable.
Appears for MSP 1+1 protection when the APS signalling does not work cor-
rectly, because the port in question has not received identical values in bits 1
to 5 of the K1 and K2 bytes for three consecutive frames out of the last twelve
frames.
Battery discharging
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Battery
discharging is selected in the Input Alarm Text: drop-down list for the auxiliary
port in question. Appears when the signal on the port is high or low depend-
ing on the value selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Battery discharging. Appears when the signal on the
Battery failure
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Battery
118 MA268 • Rev. B1

Alarms
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Battery failure. Appears when the signal on the port is
Cabling error
Appears when the cable between the main subrack and a tributary subrack in
question is not connected.
CCM loss of communication

Applies when Input is selected in the Direction: drop-down list, and CCM loss
of communication is selected in the Input Alarm Text: drop-down list for the
auxiliary port in question. Appears when the signal on the port is high or low
depending on the value selected in the Input Polarity: drop-down list.
Client Signal Fail

Appears when a client signal failure (CSF) indication is received by the proto-
col (GFP) sink. This is similar to raising an AIS alarm upon receiving an AIS
signal.
Commercial power failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Commer-
cial power failure is selected in the Input Alarm Text: drop-down list for the aux-
iliary port in question. Appears when the signal on the port is high or low de-
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Commercial power failure. Appears when the signal on
the port is high or low depending on the setting of Polarity.
Configuration error
Appears when resynchronization has been selected for a module other than a
TEX1 Resync or TEX1P Resync (mon PDH) module.
Cooling fan failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Cooling
fan failure is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Cooling fan failure. Appears when the signal on the port
is high or low depending on the setting of Polarity.
MA268 • Rev. B1 119

Alarms
Degraded signal
Appears when the bit error ratio for the signal in question exceeds the thresh-
old defined in the corresponding BER Threshold attribute.
Digital diagnostics not supported

The transceiver does not support digital diagnostics. Or the transceiver is
turned off.
DTMF EOW failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and DTMF
EOW failure is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to DTMF EOW failure. Appears when the signal on the port
EFD <ID> overwritten

Appears when the Tellabs 6300 manager starts supervising the NE while at
the same time causing another management system to stop supervising the
NE, because the maximum number of 8 management systems supervising the
NE simultaneously would otherwise be exceeded.
Enclosure door open

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Enclosure
door open is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Enclosure door open. Appears when the signal on the
Engine failure
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Engine fail-
ure is selected in the Input Alarm Text: drop-down list for the auxiliary port in
question. Appears when the signal on the port is high or low depending on
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Engine failure. Appears when the signal on the port is
120 MA268 • Rev. B1

Alarms
Equipment cooling failure

Applies when Input is selected in the Direction: drop-down list, and Equipment
cooling failure is selected in the Input Alarm Text: drop-down list for the auxil-
Equipment fan malfunction

Applies when Input is selected in the Direction: drop-down list, and Equipment
fan malfunction is selected in the Input Alarm Text: drop-down list for the aux-
Equipment protection configuration error

Only applies to 1:n equipment protection. Appears when the working TEX1P
modules are not positioned in the slots closest possible to the protection
TEX1P module.
ESM critical alarm active

Appears if one or more critical alarms are active in the ETEX NE in question.
ESM major alarm active

Appears if one or more major alarms are active in the ETEX NE in question.
ESM minor alarm active

Appears if one or more minor alarms are active in the ETEX NE in question.
ESM slot mismatch

Appears if the actual slot of an actual ETEX NE module does not match the
slot address stored in the module.
ESM usage mismatch

Appears when an ETEX NE module cannot impose the configured module us-
age due to an inconsistency with its current transport configuration.
ESM warning alarm active

Appears if one or more warning alarms are active in the ETEX NE in question.
ETEX critical
Appears if one or more critical alarms are active in the ETEX NE in question.
ETEX major
Appears if one or more major alarms are active in the ETEX NE in question.
ETEX minor
Appears if one or more minor alarms are active in the ETEX NE in question.
ETEX warning
Appears if one or more warning alarms are active in the ETEX NE in question.
Excessive errors
Appears when the bit error ratio in the multiplex section exceeds 10-3.
MA268 • Rev. B1 121

Alarms
Explosive gas
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Explosive
gas is selected in the Input Alarm Text: drop-down list for the auxiliary port in
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Explosive gas. Appears when the signal on the port is
Fan degraded
One of the three fans in the fan module is not functioning correctly. This may
be due to a reduced nominal normal speed or that the fan has stopped com-
pletely.
Fan failure
Two or all of the fans in the fan module are not functioning correctly. This may
be due to a reduced nominal normal speed or that the fans have stopped com-
pletely.
Fan speed low

Appears when the rotational speed of one of the fans in the FAN module in
question falls below 90% of the nominal normal speed.
Fan speed very low

Appears when the rotational speed of one of the fans in the FAN module in
question falls below 75% of the nominal normal speed.
Fire
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Fire is se-
lected in the Input Alarm Text: drop-down list for the auxiliary port in question.
Appears when the signal on the port is high or low depending on the value
selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Fire. Appears when the signal on the port is high or low
depending on the setting of Polarity.
Fire detector failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Fire detec-
tor failure is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Fire detector failure. Appears when the signal on the port
122 MA268 • Rev. B1

Alarms
Flood
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Flood is
selected in the Input Alarm Text: drop-down list for the auxiliary port in ques-
tion. Appears when the signal on the port is high or low depending on the val-
ue selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Flood. Appears when the signal on the port is high or
low depending on the setting of Polarity.
Forced switch pending

Appears when a Forced Switch command or a Forced Switch Away command
is pending.
FPGA failure
Appears when the FPGA file is missing for the slot in question.
Frequency out of range

Appears when the frequency of the signal received at the input port in ques-
tion is out of range, or when the frequency of the clock signal from the PLL
circuit on the receiver side is unlocked.
Fuse failure
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Fuse fail-
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Fuse failure. Appears when the signal on the port is high
or low depending on the setting of Polarity.
Generator failure
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Generator
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Generator failure. Appears when the signal on the port
GFP type mismatch

Appears when the actual GFP type is not one of the supported types.
MA268 • Rev. B1 123

Alarms
High humidity
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and High hu-
midity is selected in the Input Alarm Text: drop-down list for the auxiliary port
For 6325, 6340, 6345 and 6350.
with Alarm Text set to High humidity. Appears when the signal on the port is
High temperature
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and High tem-
perature is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to High temperature. Appears when the signal on the port
High wind
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and High wind
is selected in the Input Alarm Text: drop-down list for the auxiliary port in
For 6325, 6340, 6345 and 6350.
with Alarm Text set to High wind. Appears when the signal on the port is high
Ice build up
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Ice build
up is selected in the Input Alarm Text: drop-down list for the auxiliary port in
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Ice build up. Appears when the signal on the port is high
Insertion test access connection active

Appears when an insertion test access connection has been established with
the object in question as destination.
124 MA268 • Rev. B1

Alarms
Internal HISI degraded

Appears when the number of parity errors on one of the internal interfaces be-
tween the components on the module in question increases above a fixed
threshold value defined by the factory.
Internal HISI failure

Appears when the frame signal is lost on one of the internal interfaces be-
tween the components on the module in question.
Internal oscillator failure

Appears when the frequency of the incoming timing signal deviates more
than 12 ppm from the frequency of the internal timing oscillator.
Internal section degraded

Appears when the number of parity errors on the internal section interface in
question increases above a fixed threshold value defined by the factory.
Internal section failure

For 6330.
Appears when the frame signal is lost in one of the internal traffic interfaces
to the module.
• A tributary module is connected to both aggregate modules. Therefore, if
the alarm appears for a tributary module, the fault can be in either of the
two aggregate modules, in the tributary module itself, or in the backplane.
• An aggregate module is connected to all other modules in the subrack.
Therefore, if the alarms appears for an aggregate module, the fault cannot
be localized to any particular module.
For 6325, 6340, 6345 and 6350.
Appears when the frame signal on the internal section interface in question is
lost.
Intrusion detection
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Intrusion
detection is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Intrusion detection. Appears when the signal on the port
ISI Degraded
Appears when erroneous bits are transferred between modules on the internal
section interface (the NE backplane). This could indicate a problem with one
or more of the modules.
ISI Failure
Appears when there is an equipment failure. Either a module or the backplane
itself has a critical error and needs immediate attention.
MA268 • Rev. B1 125

Alarms
Laps frame mismatch

Appears when a frame received has header values different from the expected
values for the attributes Address, Control and SAPI.
Laser Bias Current Out of Range

Appears when the laser bias increases above or decreases below the fixed
threshold values defined by the equipment.
Laser degraded
Appears when the laser power, the laser modulation current, the laser bias
current or the laser temperature increases above or decreases below fixed
threshold values defined by the equipment.
Lifetime expectancy exceeded

Appears when the expected lifetime of the fans has been exceeded.
LFP caused link shut down

Appears when a link fault passthrough (LFP) signal or client signal fail (CSF)
signal is received by the ETEX equipment at the boundary between the SDH
and Ethernet networks. The link port is then shut down.
Lockout of protection pending

Appears when a Lock out of Protection command or a Lock Out of Protection
command is pending.
Loop back active

Appears when Loopback is set to Line or Terminal, or a loopback test access
connection has been established, for the object in question.
Loss of alignment
Appears when the alignment of the incoming signal is lost.
Loss of channel counting

Appears when the counting of channels present in the output signal has
stopped.
Loss of frame
Appears when the frame alignment of the incoming signal is lost.
Loss of multiframe
Appears when the multiframe alignment of the incoming signal is lost.
Loss of optical signal

Applies when Input is selected in the Direction: drop-down list, and Loss of op-
tical signal is selected in the Input Alarm Text: drop-down list for the auxiliary
Loss of pointer
Appears when the pointer in the incoming signal cannot be recovered correct-
ly.
126 MA268 • Rev. B1

Alarms
Loss of reference source

Appears when the timing signal from the input port in question is considered
lost.
Loss of signal
Appears when the incoming signal is lost.
Loss of timing
For 6330.
Appears when the module in question has lost its timing signal (the internal
timing reference T0 of the NE).
For 6340.
Appears when the module in question has lost its timing signal from the in-
ternal clock.
For 6345 and 6350.
Appears when the M3-1 or M6-1 module has lost the T0 clock from the corre-
sponding M3-1 or M6-1 module.
Low battery threshold

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Low bat-
tery threshold is selected in the Input Alarm Text: drop-down list for the auxil-
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Low battery threshold. Appears when the signal on the
Low cable pressure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Low cable
pressure is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Low cable pressure. Appears when the signal on the port
Low fuel
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Low fuel
For 6325, 6340, 6345 and 6350.
MA268 • Rev. B1 127

Alarms
with Alarm Text set to Low fuel. Appears when the signal on the port is high or
Low humidity
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Low hu-
midity is selected in the Input Alarm Text: drop-down list for the auxiliary port
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Low humidity. Appears when the signal on the port is
Low temperature
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Low tem-
perature is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Low temperature. Appears when the signal on the port
Low water
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Low water
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Low water. Appears when the signal on the port is high
Main power input supply failed

Appears when the PSF module in question has switched from the main power
supply to the secondary power supply.
Missing bus clock

Appears when the bus clock at the backplane of the module is detected as
missing.
Module Response Fail

The CCMC module cannot communicate with the module in the slot.
128 MA268 • Rev. B1

Alarms
MSP IF degraded
Appears when the number of parity errors on the internal MSP interface sec-
tion in question increases above a fixed threshold value defined by the factory.
MSP IF failure
Appears when the frame signal is lost on the internal MSP interface section in
question.
NE software error: <error-specific text>

Appears when an invalid message is received from an NE.
OFA Gain control not supported

Appears when the selected Gain Control attribute value is not supported by
the actual module.
OFA Gain lock active

Appears when the Gain Locked attribute is set to TRUE or the gain is locked by
an incoming received OFA lock status signal.
OFA Gain lock not supported

Appears when the Gain Locked attribute is set to TRUE and the gain locked
feature is not supported by the actual module.
OFA Loss of power matching reference

Appears when the Gain Control attribute is set to Pwr. Match and the output
power reference value is lost.
OFA Manual gain set out of range

Appears when the Gain Control attribute is set to Man. Gain and the Manual
Gain Value (dB) attribute is set outside of the supported ranges.
Optical frequency offset too high

Appears when the Enable Frequency Offset Alarm attribute is selected and op-
tical frequency offset exceeds the value defined for the Alarm On attribute in
the Optical Frequency Offset Thresholds (GHz) group box.
Optical transmit degraded

Appears when power of the transmitted laser signal has degraded.
Optical transmit failure

Appears when the transmitted laser signal is lost.
OSA channel missing

Appears when the OSA module detects that a channel is missing.
OSA input channel power low

Appears when the OSA module detects that the average power per channel
on the input port is too low.
OSA no input signal

Appears when the OSA module detects that the signal on the input port is lost.
MA268 • Rev. B1 129

Alarms
OSA receiver overload

Appears when the OSA module detects that the average channel input power
level on the input port is too high.
OSA unexpected signal

Appears when the OSA module detects one or more unexpected signals on
the input port. Where an unexpected signal has a frequency that does not
match those specified by the channel termination equipment.
OSC link down

Appears when the OSC link is down.
OSNR too low

Appears when the Enable OSNR Alarm attribute is selected and optical signal
to noise ratio exceeds the value defined for the Alarm On attribute in the OSNR
Thresholds (dB) group box.
Out of locked mode

Appears when the selector in question enters the unlocked mode (selector A),
or the free-running mode or the hold-over mode (selector B).
Output degraded
Appears when the power of the output signal is so low that it is considered
lost.
Output power out of range

Appears when Output Power Offset is set to a value that is not supported by
the hardware revision of the module in question.
Path trace mismatch

Appears when the actual received trail trace identifier does not match the val-
ue of Expected TTI.
Path unequipped
Appears when the corresponding termination point is not connected.
Appears when the VC-4, VC-3 or VC-12 channel awaits real traffic from the far
end, but the value of Signal Label for Payload Structure or Received Signal La-
bel is Unequipped.
Payload type mismatch

Appears when the actual received signal label does not match the expected
signal label.
Power down
Appears when the subrack has been powered down.
Power failure (Alternative 1)

For 6310, 6320, 6340 and 6370.
Appears when a problem has occurred in one of the power supply modules in
the subrack in question, or when the power for the module in question re-
ceived from the power supply module increases above or decreases below
130 MA268 • Rev. B1

Alarms
fixed threshold values defined by the equipment, or when the tertiary power
for the module in question is lost.
For 6330.
Appears when the tertiary power for the module in question is lost.
Power failure (Alternative 2)

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Power
problem is selected in the Input Alarm Text: drop-down list for the auxiliary
Port forced off

Appears when the Port Forced Off attribute is selected in the Traffic Manage-
ment window, and the output from an electrical port (2 Mbit/s port) is turned
off.
Power load too high

Appears when the power load of the power supply module increases above
the specified upper high limit. The alarm is cleared when the load decreases
below the specified upper low limit.
Power problem (Alternative 1)

with Alarm Text set to Power problem. Appears when the signal on the port is
Power problem (Alternative 2)

Appears when the tertiary power is lost for a module.
Power too high

Appears when the power level of the incoming or outgoing signal increases
above the upper high power-level threshold specified in the Thresholds win-
dow. The alarm is cleared when the power level decreases below the upper
low power-level threshold.
Power too low

Appears when the power level of the incoming or outgoing signal decreases
below the lower low power-level threshold specified in the Thresholds win-
dow. The alarm is cleared when the power level increases above the lower
high power-level threshold.
Proprietary information missing

Appears when proprietary information in the EEPROM is missing or is not
valid.
Protection module incapable of protecting

Appears when the capabilities of the protection module in question are less
than those of the/all corresponding working module(s).
MA268 • Rev. B1 131

Alarms
Protection module used

Appears when the protection module in question is active due to a failure on
the working module.
Protection voltage failure

Appears when the voltage of the secondary power supply is too low.
Protection voltage too low

Appears when the voltage of the secondary power supply is too low.
Pump failure
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Pump fail-
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Pump failure. Appears when the signal on the port is
RDI
Appears when an RDI is received in the overhead. An RDI indicates that the
other end of the section or path does not receive a signal from this end.
Receiver overload
Appears when the receiver detects an overload on the input port.
Rectifier failure
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Rectifier
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Rectifier failure. Appears when the signal on the port is
Rectifier high voltage

For 6310, 6320, 6330 and 6370.
high voltage is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Rectifier high voltage. Appears when the signal on the
132 MA268 • Rev. B1

Alarms
Rectifier low voltage

For 6310, 6320, 6330 and 6370.
low voltage is selected in the Input Alarm Text: drop-down list for the auxiliary
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Rectifier low voltage. Appears when the signal on the
RTM failure
Appears when the real-time marker is missing in the module in question.
SC AIS inserted
Appears if the administrative state of the station clock output in question is
not locked, and the quality level of the signal from selector C falls below the
configured quality level threshold of the output causing the output to send an
AIS.
Section trace mismatch

Appears when the actual received trail trace identifier does not match the val-
ue of Expected TTI.
Selector A output squelched

Appears if the administrative state of the station clock output in question is
not locked, and the quality level of the signal from selector C falls below the
configured quality level threshold of the output.
Sequence indicator mismatch

Appears when the sequence number of the received VCG member does not
match the sequence number assigned to the specific VCG member.
Slot mismatch
Appears if the actual slot of an actual ETEX module does not match the slot
address stored in the module.
Smoke
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Smoke is
selected in the Input Alarm Text: drop-down list for the auxiliary port in ques-
tion. Appears when the signal on the port is high or low depending on the val-
ue selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Smoke. Appears when the signal on the port is high or
MA268 • Rev. B1 133

Alarms
Software failure
Appears when the software used by the module in the slot in question con-
stantly resets.
SSF
Appears when an SSF (server signal fail) is detected, that is the normal signal
has been interrupted due to a failure in the server layer.
Storage capacity problem

Appears when an overflow of events occurs in the FIFO buffer in the NE. In
this situation all events are deleted from the buffer.
Switch FET temperature too high

Appears when the temperature of a switch FET on the PSF module in question
increases above a fixed threshold value defined by the factory.
Switch to secondary power

Appears when the PSF module in question has switched from the main power
supply to the secondary power supply.
Synchronization source frequency out of range

Appears when frequency of the signal in question is out of range.
T4 output squelched
Appears when the timing source selected in the Selector C window has been
suppressed because its quality level was too low compared to the level speci-
fied in Squelch quality Threshold.
TCXO (oscillator) failure

Appears when the signal from the temperature-controlled crystal oscillator in
the module is lost.
Temperature too high

Appears when the temperature of the power supply module increases above
the specified upper high limit. The alarm is cleared when the temperature de-
creases below the specified upper low limit.
TIP missing
Appears when one or both TIP modules are missing for the SIM1e module in
question.
Toxic gas
For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Toxic gas
For 6325, 6340, 6345 and 6350.
134 MA268 • Rev. B1

Alarms
with Alarm Text set to Toxic gas. Appears when the signal on the port is high
Transceiver Response Fail

The appears when the module cannot communicate with the transceiver. This
may be due to the transceiver output being turned off (when possible).
Transceiver Supply Voltage Out of Range

This alarm appears when the power supply to the transceiver is no longer
within the permitted range. This alarm could indicate that the transceiver is
degraded. Therefore, it may be time to change the transceiver before the trans-
ceiver fails.
Transceiver Temperature Out of Range

This alarm appears when the measured temperature inside the transceiver is
no longer within the permitted range. This alarm could indicate that the trans-
ceiver is degraded. Therefore, it may be time to change the transceiver before
the transceiver fails.
Transmit degraded
Appears when power of the transmitted laser signal has degraded.
Transmit fail
Appears when the transmitted laser signal is lost.
UB power too high

Appears when the voltage of the secondary supply port that is currently active
increases above the specified upper high limit. The alarm is cleared when the
voltage decreases below the specified upper low limit.
UB power too low

Appears when the voltage of the secondary supply port that is currently active
decreases below the specified lower low limit. The alarm is cleared when the
voltage increases above the specified lower high limit.
UB1 power missing

Appears when the UB1 secondary supply voltage is lost.
UB2 power missing

Appears when the UB2 secondary supply voltage is lost.
Unit initialising
Appears when the software used by the module in the slot in question is re-
setting and rebooting.
Unit main type mismatch

Appears when the expected subrack or module type does not match the actual
subrack or module type. When the alarm appears on a module, the module
cannot be managed.
MA268 • Rev. B1 135

Alarms
Unit missing
Appears when a module is expected in the slot in question, but no module is
physically present in the slot.
Unit sub type mismatch

Appears when the expected subrack type or module subtype does not match
the actual subrack type or module subtype.
Unit temperature too high

Appears when the temperature of the module increases above a fixed thresh-
old value defined by the equipment.
Unit temperature too low

Appears when the temperature of the module decreases beneath a fixed
threshold value defined by the equipment.
Unknown LMIP probable cause <ID>

Appears when an alarm is received from the NE with an unknown LMIP
probable cause.
User defined <1, 2, ..., 8>

Applies when Input is selected in the Direction: drop-down list, and User de-
fined <1, 2, ..., 8> is selected in the Input Alarm Text: drop-down list for the aux-
User-defined <1, 2, ..., 8>

with Alarm Text set to User-defined <1, 2, ..., 8>. Appears when the signal on
Vcc (+5V) voltage too high

Appears when the +5 V tertiary supply voltage of the power supply module
increases above the specified upper high limit. The alarm is cleared when the
voltage decreases below the specified upper low limit.
Vcc (+5V) voltage too low

Appears when the +5 V tertiary supply voltage of the power supply module
decreases below the specified lower low limit in vccValueThresholds. The
alarm is cleared when the voltage increases above the specified lower high
limit.
VCO (oscillator) failure

Appears when the signal from the voltage-controlled oscillator in the module
is lost.
VCXO (oscillator) failure

Appears when the signal from the voltage-controlled crystal oscillator in the
module is lost.
136 MA268 • Rev. B1

Alarms
Vee (-5V) voltage too high

Appears when the absolute value of the –5 V tertiary supply voltage of the
power supply module increases above the specified upper high limit. The
alarm is cleared when the voltage decreases below the specified minimum up-
per limit.
Vee (-5V) voltage too low

Appears when the absolute value of the –5 V tertiary supply voltage of the
power supply module decreases below the specified lower low limit. The
alarm is cleared when the voltage increases above the specified maximum
lower limit.
Ventilations system failure

For 6310, 6320, 6330 and 6370.
Applies when Input is selected in the Direction: drop-down list, and Ventila-
tions system failure is selected in the Input Alarm Text: drop-down list for the
auxiliary port in question. Appears when the signal on the port is high or low
depending on the value selected in the Input Polarity: drop-down list.
For 6325, 6340, 6345 and 6350.
with Alarm Text set to Ventilations system failure. Appears when the signal on
MA268 • Rev. B1 137

Alarms
138 MA268 • Rev. B1

Tellabs® 6300 Network Manager 11 Probable Causes
Alarms
11 Probable Causes
This chapter contains the probable causes as defined in the Open Systems In-
terconnection (OSI) framework and by the International Telecommunication
Union (ITU, former CCITT).
• Unknown
• AdapterError
• ApplicationSubsystemFailure
• BandwidthReduced
• CallEstablishmentError
• CommunicationsProtocolError
• CommunicationsSubsystemFailure
• ConfigurationOrCustomizationError
• Congestion
• CorruptData
• CpuCyclesLimitExceeded
• DataSetOrModemProblem
• DegradedSignal
• DTE-DCEInterfaceError
• EnclosureDoorOpen
• EquipmentMalfunction
• ExcessiveVibration
• FileError
• FireDetected
• FloodDetected
• FramingError
• HeatingOrVentilationOrCoolingSystemProblem
• HumidityUnacceptable
• InputOutputDeviceError
• InputDeviceError
• LANError
• LeakDetected
• LocalNodeTransmissionError
• LossOfFrame
• LossOfSignal
• MaterialSupplyExausted
• MultiplexerProblem
• OutofMemory
• OutputDeviceError
MA268 • Rev. B1 139

Alarms
• PerformanceDegraded
• PowerProblem
• PressureUnacceptable
• ProcessorProblem
• PumpFailure
• QueueSizeExceeded
• ReceiveFailure
• ReceiverFailure
• RemoteNodeTransmissionError
• ResourceAtOrNearingCapacity
• ResponseTimeExcessive
• RetransmissionRateExcessive
• SoftwareError
• SoftwareProgramAbnormallyTerminated
• SoftwareProgramError
• StorageCapacityProblem
• TemperatureUnacceptable
• ThresholdCrossed
• TimingProblem
• ToxicLeakDetected
• TransmitFailure
• TransmitterFailure
• UnderlyingResourceUnavailable
• VersionMismatch
• SnmpTrapColdStart
• SnmpTrapWarmStart
• SnmpTrapLinkDown
• SnmpTrapLinkUp
• SnmpTrapAuthenticationFailure
• SnmpTrapEgpNeighborloss
• SnmpTrapEnterpriseSpecific
• SnmpTrapLinkUpDown
• UnspecifiedReason
• SectionTraceMismatch
• BackupFailed
• gfpLossOfClientSignal
• gfpLossOfClientSynchronization
• vcgLossOfPartialCapacity
140 MA268 • Rev. B1

Alarms
• vcgLossOfFullCapacity
• lapfFrameMismatch
• lapfLmiLinkDown
• mplsOamTTSIMismatch
• mplsOamTTSIMismerge
• mplsOamLossOfCV
• mplsOamExcess
• etherOamLinkDown
• systemConfigUpgradeFailure
• freqOutOfRange
• lcpLinkDown
• psuInputMissing
• replacableUnitFailure
• linkShutDown
• clientSignalFail
• intraSectionFail
• intraSectionDegraded
• /* ITU-T (CCITT) probable causes from M3100 set */
• Indeterminate
• AIS
• CallSetUpFailure
• DegradedSignal_m3100
• FarEndReceiverFailure
• FramingError_m3100
• LossOfFrame_m3100
• LossOfPointer
• LossOfSignal
• PayloadTypeMismatch
• TransmissionError
• RemoteAlarmInterface
• ExcessiveBER
• PathTraceMismatch
• Unavailable
• SignalLabelMismatch
• LossOfMultiFrame
• ReceiveFailure_m3100
• TransmitFailure_m3100
• ModulationFailure
MA268 • Rev. B1 141

Alarms
• DemodulationFailure
• BroadCastChannelFailure
• ConnectionEstablishmentError
• InvalidMessageReceived
• LocalNodeTransmissionError_m3100
• RemoteNodeTransmissionError_m3100
• RoutingFailure
• RxFail
• RxLOS
• DemodulationFail
• DemLOS
• TxFail
• TxLOS
• ModulationFail
• ModLOS
• BackplaneFailure
• DataSetProblem
• EquipmentIdentifierDuplication
• ExternalIFDeviceProblem
• LineCardProblem
• MultiplexerProblem_m3100
• NEIdentifierDuplication
• PowerProblem_m3100
• ProcessorProblem_m3100
• ProtectionPathFailure
• ReceiverFailure_m3100
• ReplaceableUnitMissing
• ReplaceableUnitTypeMismatch
• SynchronizationSourceMismatch
• TerminalProblem
• TimingProblem_m3100
• TransmitterFailure_m3100
• TrunkCardProblem
• ReplaceableUnitProblem
• RealTimeClockFailure
• AntennaFailure
• BatteryCharginFailure
• DiskFailure
142 MA268 • Rev. B1

Alarms
• FrequencyHoppingFailure
• IODeviceError
• LossOfSynchronisation
• LossOfRedundancy
• PowerSupplyFailure
• SignalQualityEvaluationFailure
• TransceiverFailure
• AirCompressorFailure
• AirConditioningFailure
• AirDryerFailure
• BatteryDischarging
• BatteryFailure
• CommercialPowerFailure
• CoolingFanFailure
• EngineFailure
• FireDetectorFailure
• FuseFailure
• GeneratorFailure
• LowBatteryThreshold
• PumpFailure_m3100
• RectifierFailure
• RectifierHighVoltage
• RectifierLowFVoltage
• VentilationsSystemFailure
• EnclosureDoorOpen_m3100
• ExplosiveGas
• Fire
• Flood
• HighHumidity
• HighTemperature
• HighWind
• IceBuildUp
• IntrusionDetection
• LowFuel
• LowHumidity
• LowCablePressure
• LowTemperature
• LowWater
MA268 • Rev. B1 143

Alarms
• Smoke
• ToxicGas
• CoolingSystemFailure
• ExternalEquipmentFailure
• ExternalPointFailure
• StorageCapacityProblem_m3100
• MemoryMismatch
• CorruptData_m3100
• OutOfCPUCycles
• SfwrEnvironmentProblem
• SfwrDownloadFailure
• LossOfRealTime
• Reinitialized
• ApplicationSubsystemFailure_m3100
• ConfigurationOrCustomisationError
• DatabaseInconsistency
• FileError_m3100
• OutOfMemory_m3100
• SoftwareError_m3100
• TimeoutExpired
• UnderlayingResourceUnavailable
• VersionMismatch_m3100
• BandwidthReduced_m3100
• ExcessiveErrorRate
• ExcessiveResponseTime
• ExcessiveRetransmissionRate
• ReducedLoggingCapability
• SystemResourcesOverload
• FDI
• Unequipped
• SSF
• LossOfSequence
• BDI
• LossOfAlignment
• LossOfContinuity
• AutomaticLaserShutdown
• CommunicationProblem
• laserTempOutsideLimit
144 MA268 • Rev. B1

Alarms
• blsrDefaultKBytes
• blsrInconsistentAPSCodes
• blsrNodeIdMismatch
• blsrImproperAPSCodes
• blsrSquelching
• lossOfTimingSource
• apsChannelProcessingFailure
• apsByteFailure
• apsChannelMatchFailure
• apsModeMismatch
• lossOfTUMultiframeIndicator
• pathSelectorFailure
• localUserPartUnavailable
• q752Item1p01
• q752Item1p9
• q752Item2p9
• q752Item2p15
• q752Item2p17
• q752Item3p05
• q752Item3p10
• q752Item4p02
• q752Item4p04
• q752Item4p10
• q752Item4p12
• q752Item5p00
• q752Item5p04
• q752Item5p05
• q752Item5p06
• q752Item5p07
• remoteUserPartUnavailable
• msSPRDefaultKBytes
• msSPRInconsistentAPSCodes
• msSPRNodeIdMismatch
• msSPRImproperAPSCodes
• msSPRApsChannelProcessingFailure
• cellStarvation
• lossOfCellDelineation
• failedRestart
MA268 • Rev. B1 145

Alarms
• LaserBiasOutOfLimit
• LaserShutdownActive
• TransmitPowerLevelLow
• TransmitPowerLevelHigh
• UserInput00
• UserInput01
• UserInput02
• UserInput03
• UserInput04
• UserInput05
• UserInput06
• UserInput07
• UserInput08
• UserInput09
• UserInput10
• UserInput11
• UserInput12
• UserInput13
• UserInput14
• UserInput15
• UserInput16
• UserInput17
• UserInput18
• UserInput19
• airFlowProblem
• fanTrayAssemblyProblem
• replaceableUnitsIncompatible
• replaceableUnitsOutOfSync
• fERFConnectivity
• fERFServer
• fERFPayload
• fEProtectionLineFailure
• mediaMissing
• switchDatabase
• switchExecutable
• lossOfSupervisoryChannel
• overheadAIS
• timingEquipmentRangeProblem
146 MA268 • Rev. B1

Alarms
• lossOfTimingInput
• mtieMaskCrossing
• ConfigurationParameterOutOfRange
• FunctionalityNotSupported
• InternalRxFail
• ExternalPointFailure_tlab
• actualTransceiverNotExpected
• apsArchitectureMismatch
• apsInappropriateRequest
• apsIllegalRequest
• apsSelectorMismatch
• apsUnstable
• apsTimeout
• apsIllegalNodeID
• apsIllegalState
• apsDefaultSignalling
• protectionModuleUsed
• lockoutOfProtectionPending
• forcedSwitchPending
• excessiveError
• rDI
• sSF
• unequippedDefect
• sqMismatch
• maxDiffDelayExceeded
• gfpEXIMismatch
• gfpUPIMismatch
• gfpLossOfFrameAlignment
• etexCritical
• etexMajor
• etexMinor
• etexWarning
• slotMismatch
• ofaGainControlNotSupported
• ofaManualGainSetOutOfRange
• ofaLossOfGainControl
• ofaGainLockNotSupported
• ofaGainLockActivated
MA268 • Rev. B1 147

Alarms
• usageMismatch
• equipmentFanMalFunction
• equipmentCoolingFailure
• mSPNotSupported
• protectionArchitectureMismatch
• inappropriateRequestCodeReceived
• illegalRequestCodeReceived
• selectorControlMismatch
• unstableAPSSignalling
• osaChannelSpacingNotSupported
• osaNoInputSignal
• osaReceiverOverload
• osaInputChannelPowerLow
• osaUnexpectedSignal
• osaChannelMissing
• bitEncodingSchemeNotSupported
• proprietaryInformationMissing
• iApsIllegalRequest
• LayerResourceFailed
• ServerFailure
• laserBiasCurrentOutOfRange
• transceiverTemperatureOutOfRange
• transceiverSupplyVoltageOutOfRange
• transceiverResponseFail
• moduleResponseFail
• lapsFrameMismatch
• sequenceIndicatorMismatch
• digitalDiagnosticsNotSupported
• lossOfInternalTiming
148 MA268 • Rev. B1

Tellabs® 6300 Network Manager Index
Alarms
Index
A for alarm rules 93, 98

Alarm filters 29
Abbreviations 8
setting up 49
Acknowledge an alarm 53
Alarm Fired Parameters attribute
Acknowledge operation 113
for alarm rules 93, 98
Acknowledged icon 26
Alarm Fired Procedure attribute
Acknowledgement Time Stamp attribute
for alarm objects 86
Alarm handling 14, 51
Acknowledgement User Identifier attribute
principles of 13
setting up 43
Actual module not expected alarm 115
Alarm History 56
Actual transceiver not expected alarm 115
Alarm indication 17
Add an operation context 46
icon colors 18
Additional Information attribute
Alarm information 14
Alarm inspection 51
Additional Text attribute
Alarm log 16
alarms for 105
value for alarm escalation alarms 106
applying new search pattern 60
value for alarm log alarms 106
change a search pattern 59
value for bridge LAN interfaces alarms 104
define a search pattern 58
value for bridge leased lines interfaces
deleting search pattern 60
alarms 104
purging alarms 61
value for disk storage alarms 105
searching in 58
value for SNMP entity alarms 104
Alarm Object Operator Note attribute
Additional Text Propagation Mode attribute
for operation contexts 71
Alarm objects
Administrative State attribute
attributes 80
Characteristics attributes 81
Administrative State Change Timestamp attribute
Counters attributes 88
Identifiers attributes 81
Air compressor failure alarm 115
special operations 113
Air conditioning failure alarm 115
Status attributes 86
Air dryer failure alarm 115
Alarm Origin attribute
AIS (alarm indication signal) alarm 115
AIS alarm 115
Alarm presentation 14
AIS insertion forced alarm 116
Alarm received from NE in illegal format
Alarm attributes 23
alarm 116
Alarm Class attribute
Alarm reporting 13
Alarm responsibility 16
Alarm clearance 16
Alarm rules 22
state changes 55
attributes 91
Alarm collection
attributes for registration 91
defining 35
change of rule type 23
Alarm Descriptions 115
Alarm display
comparison rule type 23
disable 48
enable 48
expression rule type 23
Alarm entities 21
for alarm escalation 106
Alarm escalation
for alarm logs 105
alarm rules for 106
for bridge LAN interfaces 104
Alarm Exception Procedure attribute
for bridge leased lines interfaces 104
MA268 • Rev. B1 149

Alarms
for disk storage 105 APS architecture mismatch alarm 116

for SNMP entities 103 APS default signalling alarm 116
for system monitoring 103 APS illegal node ID alarm 117
Identifiers attributes 98 APS illegal request alarm 117
occurs n time rule type 23 APS illegal state alarm 118
occurs rule type 23 APS inappropriate request alarm 118
special operations 112 APS selector mismatch alarm 118
Status attributes 99 APS timeout alarm 118
types of 23 APS unstable alarm 118
Alarm severity levels 25 Archive and Purge attribute
Alarm stages 51 for operation contexts 76
Alarm surveillance 14 Archive AO Age attribute
specifying 45 for operation contexts 75
Alarm surveillance disabled alarm 116 Archive AO Severity attribute
Alarm Text attribute 24 for operation contexts 75
Alarm Type attribute Archive Begin Time attribute
for alarm objects 81 for operation contexts 75
value for alarm escalation alarms 106 Archive Database Filename attribute
value for alarm log alarms 106 for operation contexts 75
value for bridge LAN interfaces alarms 104 Archive End Time attribute
value for bridge leased lines interfaces for operation contexts 75
alarms 104 Archive Error Status attribute
value for disk storage alarms 105 for operation contexts 76
value for SNMP entity alarms 103 Archive Interval attribute
Alarms 115 for operation contexts 76
define filter pattern 49 Archive Last Time attribute
definition of 13 for operation contexts 76
from computer hardware 103 Archive Next Time attribute
from computer software 105 for operation contexts 76
Alarms view filters 29 Archive operation 110
filtering criteria 30 Archive Sequence Name attribute
Alarms View window for operation contexts 76
purging alarms 61 Archive Sequence Number attribute
searching in 58 for operation contexts 76
Ambient high temperature alarm 116 Archive Time Stamp attribute
AO Acknowledged attribute for alarm objects 86
for operation contexts 80 Archiving Status attribute
AO Age parameter for operation contexts 76
of Archive operation 110 Associated Domain attribute
of Purge_alarms operation 108 for operation contexts 65, 71
AO Archived attribute Associated Notif EFD attribute
for operation contexts 80 for operation contexts 76
AO Closed attribute Attribute Name attribute
for operation contexts 80 for alarm rules 96
AO Handled attribute Attribute values
for operation contexts 80 for computer hardware alarms 103
AO Not Handled attribute for computer software alarms 105
for operation contexts 80 Attributes
AO Outstanding attribute display all for an alarm 53
for operation contexts 80 for alarm objects 80
AO Terminated attribute for alarm rules 91
for operation contexts 80 for alarms 23
AO Total attribute for operation contexts 65
for operation contexts 80 Auto Enable attribute
150 MA268 • Rev. B1

Alarms
for alarm rules 92 Change of rule 23

Automatic Acknowledge attribute Change of Rule attribute
for operation contexts 66, 71 for alarm rules 91
Automatic Acknowledge on Handle 71 Characteristics attributes
Automatic Acknowledge on Handle attribute for alarm objects 81
Automatic Escalation attributes for operation contexts 71
for operation contexts 66, 71 Clear Problem Occurrences attribute
Automatic Escalation Critical Delta Time attribute for alarm objects 88
for operation contexts 71 Clearance alarms 16
Automatic Escalation Major Delta Time attribute Clearance attribute 26
for operation contexts 66, 71 Clearance of alarms
Automatic Escalation Minor Delta Time attribute state changes 55
for operation contexts 66, 71 Clearance Report Flag attribute
Automatic Escalation Warning Delta Time for alarm objects 86
attribute icon 26
for operation contexts 66, 72 Clearance report flag icon 26
Automatic Terminate On Alarm Clearance Clearance Time Stamp attribute
attribute for alarm objects 86
for operation contexts 67, 72 Client signal fail alarm 119
Automatic Terminate On Alarm Close attribute Close Time Stamp attribute
for operation contexts 67, 72 for alarm objects 87
Automatic Terminate On Close attribute Close User Identifier attribute
for alarm objects 86 for alarm objects 87
Availability Status attribute Closed By attribute
Availability Status Change Timestamp attribute Colors for alarm indication 18
for operation contexts 77 Commercial power failure alarm 119
Comparison rule 23
Comparison Rule attribute
B for alarm rules 91
Backed Up Status attribute
Comparison Value attribute
for alarm rules 97
Backup Object attribute
Comparison Values attribute
for alarm rules 96
Battery discharging alarm 118
Composite State attribute
Battery failure alarm 118
Begin Time parameter
Composite State Change Timestamp attribute
of Archive operation 111
of Purge_alarms operation 109
Composite State Explanation attribute
Bridge LAN interfaces
alarm rules for 104
Computer hardware
Bridge leased lines interfaces
alarms from 103
alarm rules for 104
Computer software
alarms from 105
C Configuration Error alarm 119
Cabling error alarm 119 Cooling fan failure alarm 119
Cancel_archive operation 112 Copy operation 112
Cancel_purge operation 110 Correl Notif Info attribute 26
Capacity Alarm Threshold attribute for alarm objects 82
for operation contexts 67, 72 icon 27
Category attribute Correlated notif info icon 27
for alarm rules 92, 98 correlatedNotification field
CCM loss of communication alarm 119 for alarm objects 82
MA268 • Rev. B1 151

Alarms
Count attribute using 92

for alarm rules 97 Enclosure door open alarm 120
Counters attributes End Time attribute
for alarm objects 88 for alarm rules 95
for alarm rules 100 End Time parameter
for operation contexts 80 of Archive operation 111
Creation Timestamp attribute of Purge_alarms operation 109
for alarm objects 87 Engine failure alarm 120
for alarm rules 100 Entities 21
for operation contexts 78 alarm rule 22
Critical Problem Occurrences attribute managing 54
for alarm objects 88 operation context 21
Current Severity attribute Entity attribute
for alarm rules 99 for alarm rules 96
Entity Browser
changing operation contexts 40
D Entity View - OPERATION_CONTEXT
database name parameter open window 37
of Archive operation 110 Equipment cooling failure alarm 121
Degraded signal alarm 120 Equipment fan malfunction alarm 121
Delete Equipment protection configuration error
filter 50 alarm 121
Deleting Error Condition attribute
operation context 40 for alarm rules 99
Delta Time attribute Error Condition Status attribute
for alarm rules 97 for operation contexts 78
Description attribute Error Entity attribute
for alarm rules 92, 98 for alarm rules 99
Deselect
Escalated Alarm attribute
filter 51
Detailed Object attribute 24
Escalated and Cleared Flag attribute
Digital diagnostics not supported alarm 120
Directory operation 107
ESM slot mismatch alarm 121
Disable operation 112
ESM usage mismatch alarm 121
using 92
ETEX critical alarm 121
Disable Time attribute
ETEX critical alarm active alarm 121
for alarm rules 99
ETEX major alarm 121
Discriminator Construct attribute
ETEX major alarm active alarm 121
for operation contexts 68, 72
ETEX minor alarm 121
Disk storage
ETEX minor alarm active alarm 121
alarm rules for 105
ETEX warning alarm 121
Display of alarms
ETEX warning alarm active alarm 121
disable 48
Evaluation Error attribute
enable 48
for alarm rules 100
Domain attribute
Evaluation False attribute
for alarm rules 101
for alarm rules 91
Evaluation True attribute
DTMF EOW failure alarm 120
for alarm rules 101
Duration Interval attribute
Event Name attribute
for alarm rules 96
for alarm rules 97
Event Time attribute 24
E for alarm objects 82
EFD <ID> overwritten alarm 120 Event Type attribute
Enable operation 112 for alarm rules 93
152 MA268 • Rev. B1

Alarms
Excessive errors alarm 121 High humidity alarm 124

Explosive gas alarm 122 High temperature alarm 124
Export Sequence Name attribute High wind alarm 124
for alarm objects 83 History View
Export Sequence Number attribute delete filters 50
for alarm objects 83 deselect filter use 51
Expression attribute inspect a filter pattern 50
for alarm rules 98 select filter use 50
Expression rule 23 History View window 56
Expression Rule attribute applying new search pattern 60
for alarm rules 91 change a search pattern 59
define a search pattern 58
deleting search pattern 60
F open 57
Fan speed low alarm 122 terminating alarm 55
Fan speed speed very alarm 122
Filter area
delete a filter pattern 50 I
deselect a filter 51 Ice build up alarm 124
use a filter 50 Icons
Filter Editor window 29 colors indicating alarms 18
define a filter pattern 49 showing clearance 26
setting up a filter 49 showing correlated notif info 27
Filter pattern showing state 25
define 49 Identifier attribute
inspect 50 for alarm objects 81
Filters 29 Identifiers attributes
alarms view filters 29 for alarm objects 81
creating alarms view filter 49 for alarm rules 98
deselect 51 for operation contexts 71
select 50 Implementation Desc attribute
Fire alarm 122 for operation contexts 68
Fire detector failure alarm 122 Indeterminate Problem Occurrences attribute
Flood alarm 123 for alarm objects 88
Forced switch pending alarm 123 Indication of alarms 17
FPGA failure alarm 123 Information about alarms 14
Frequency out of range alarm 123 Initial Administrative State attribute
Fuse failure alarm 123 for operation contexts 68
Insertion test access connection active alarm 124
Internal HISI degraded alarm 125
G Internal HISI failure alarm 125
Generator failure alarm 123 Internal oscillator failure alarm 125
GFP type mismatch alarm 123 Internal section degraded alarm 125
Internal section failure alarm 125
H Interval parameter
Handle Time Stamp attribute of Archive operation 111
for alarm objects 87 of Purge_alarms operation 109
Handled By attribute Intrusion detection alarm 125
Handled User Identifier attribute L
Laps frame mismatch alarm 126
Handling alarms 14
Laser Bias Current Out of Range alarm 126
Hardware
Laser degraded alarm 126
alarms from 103
LFP caused link shut down alarm 126
MA268 • Rev. B1 153

Alarms
Lifetime expectancy exceeded alarm 126 Missing bus clock alarm 128
Location attribute Modify Copied Rule parameter
for operation contexts 68 of Copy operation 112
Lockout of protection pending alarm 126 Module Response Fail alarm 128
LogFullAction attribute Monitored Attributes attribute
Logging of alarms 16 Monitored By attribute
Logical_Operator_And attribute for operation contexts 78
for alarm objects 83 MSP IF degraded alarm 129
Loop back active alarm 126 MSP IF failure alarm 129
Loss of alignment alarm 126
Loss of channel counting alarm 126
Loss of frame alarm 126
N
Loss of multiframe alarm 126 Name attribute
Loss of optical signal alarm 126 for alarm rules 98
Loss of pointer alarm 126 for operation contexts 68, 71
Loss of reference source alarm 127 NE software error: <error-specific text> alarm 129
Loss of signal alarm 127 New Domain Name parameter
Loss of timing alarm 127 of Copy operation 112
Low battery threshold alarm 127 New Rule Name parameter
Low cable pressure alarm 127 of Copy operation 112
Low fuel alarm 127 Nick Name attribute
Low humidity alarm 128 for alarm rules 91
Low temperature alarm 128 Notification Identifier attribute
Low water alarm 128 for alarm objects 83
M O
MAIL Account attribute OC Name attribute
Main Object attribute 24 Occurs n time rule 23
Main power input supply failed alarm 128 Occurs N Time Rule attribute
Major Problem Occurrences attribute for alarm rules 91
for alarm objects 88 Occurs rule 23
Managed Object attribute Occurs Rule attribute
for alarm objects 83 for alarm rules 91
value for alarm escalation alarms 106 OFA gain control not supported alarm 129
value for alarm log alarms 105 OFA gain lock active alarm 129
value for bridge LAN interfaces alarms 104 OFA gain lock not supported alarm 129
value for bridge leased lines interfaces OFA loss of power matching reference alarm 129
OFA manual gain set out of reference alarm 129
alarms 104
Open the alarm log 57
Opening
Managing Director attribute Real Time View window 44
Operation context
Managing Director parameter creating 35
deleting 40
of Register operation 107
managing 36
Managing operation contexts 36
Max Log Size attribute performing operations 40
for operation contexts 72 Operation Context Description attribute
Minor Problem Occurrences attribute for operation contexts 69, 72
Operation Context List window 39
opening 46
Mir Component Version attribute
Operation Context View window 45
add operation context 46
154 MA268 • Rev. B1

Alarms
disabling alarm display 48

enabling alarm display 48
P
Parent Alarm Object attribute
remove operation context 47
Operation contexts 21
Path trace mismatch alarm 130
add in Operation Context View window 46
Path unequipped alarm 130
attributes 65
Payload type mismatch alarm 130
attributes for registration 65
Perceived Severity attribute 25
Identifiers attributes 71
remove from Operation Context View
window 47
Routing attributes 80
alarms 104
special operations 107
Status attributes 75
Operation parameter
Phone Number attribute
of Register operation 107
OPERATION_CONTEXT attribute
Polling Interval attribute
for alarm rules 96
Operational State attribute
Power down alarm 130
Power failure alarm 130, 131
Operational State Change Timestamp attribute
Power load too high alarm 131
Power problem alarm 131
Operations
Power too high alarm 131
performing on operation context 40
Power too low alarm 131
special for alarm objects 113
Presentation of alarms 14
special for alarm rules 112
Principles of alarm handling 13
special for operation contexts 107
Probable Cause attribute
Operator note
for alarm objects 25, 84
creating 54
Optical transmit degraded alarm 129
Optical transmit failure alarm 129
Original Event Time attribute
Original Severity attribute
alarms 104
OSA channel missing alarm 129
OSA input channel power low alarm 129
Probable causes
OSA no input signal alarm 129
list of 139
OSA receiver overload alarm 130
Problem Occurrences attribute
OSA unexpected signal alarm 130
OSC link down alarm 129, 130
Problem Status attribute
OSNR too low alarm 130
Out of locked mode alarm 130
Proposed Repair Actions attribute
Outage Policy attribute
Proprietary information missing alarm 131
Output degraded alarm 130
Protection module incapable of protecting
Output power out of range 130
alarm 131
Outstanding icon 25
Protection module used alarm 132
Owner ID attribute
Protection voltage failure alarm 132
Protection voltage too low alarm 132
Ownership Control attribute
Pseudo-alarm 55
Psuedo Alarm attribute 26
Pump failure alarm 132
MA268 • Rev. B1 155

Alarms
Purge AO Age attribute for alarm rules 91

Purge AO Severity attribute Relational Operator attribute
Purge AO State attribute Release Time Stamp attribute
Purge Begin Time attribute Release User Identifier attribute
Purge End Time attribute Remarks attribute
Purge Error Status attribute Reporting of alarms 13
for operation contexts 79 Repository Location attribute
Purge Interval attribute for operation contexts 69, 74
for operation contexts 79 Responsibility for alarm handling 16
Purge Last Time attribute Responsible Operators attribute
Purge Next Time attribute Responsible Person attribute
Purge parameter Result of Last Evaluation attribute
of Archive operation 111 for alarm rules 99
Purge Status attribute Resume operation 108
for operation contexts 79 using 68, 75
Purge_alarms operation 108 Resumed By User attribute
Purging alarms 61 for operation contexts 79
Routing attributes
R RTM failure alarm 133
RDI (remote defect indicator) alarm 132 Rule Expression attribute
RDI alarm 132
for alarm rules 95
Real Time View
Rule Name attribute
deselect filter use 51
inspect a filter pattern 50
select filter use 50
Real Time View window S
acknowledge an alarm 53 SA Total attribute
creating operator note 54 for alarm objects 89
delete filters 50 SC AIS inserted alarm 133
display all attributes for alarm 53 Scheduling Package attribute
managing entity causing alarm 54 for operation contexts 70, 74
opening 44 Search History View window
terminating alarm 55 applying new search pattern 60
Receiver overload alarm 132 Search pattern
Rectifier failure alarm 132 applying new 60
Rectifier high voltage alarm 132 change 59
Rectifier low voltage alarm 133 define 58
Reduction Mode attribute deleting 60
for operation contexts 69, 73 Searching in alarm log 58
Reduction Scope attribute Section trace mismatch alarm 133
for operation contexts 73 Security Alarm Cause attribute
Reference Operation_Context Name attribute for alarm objects 84
for operation contexts 69 Security Alarm Detector attribute
References 8 for alarm objects 84
Register operation 107 Select
Registration attributes filter 50
156 MA268 • Rev. B1

Alarms
Selector A output squelched alarm 133 Style conventions 8

Sequence indicator mismatch alarm 133 Substate attribute
Sequence Name parameter for alarm rules 100
of Archive operation 110 Summarize operation
Sequence Number parameter for alarm objects 113
of Archive operation 110 Supervising alarms 43
Service Provider attribute Supervision of alarms 14
for alarm objects 84 Surveillance of alarms
Service User attribute specifying 45
for alarm objects 84 Suspend operation 108
Severity using 68, 75
levels 25 Suspended By User attribute
Severity attribute for operation contexts 79
for alarm rules 92, 98 Switch FET temperature too high alarm 134
Severity parameter Switch to secondary power alarm 134
of Archive operation 110 Synchronisation source frequency out of range
of Purge_alarms operation 108 alarm 134
Severity Propagation Mode attribute Synchronization source frequency out of range
for operation contexts 70, 74 alarm 134
Similarity Mode attribute System monitoring
for operation contexts 70, 74 alarm rules for 103
Slot mismatch alarm 133
Smoke alarm 133
SNMP entities
T
alarm rules for 103 T4 output squelched alarm 134
Software Target Entities attribute
alarms from 105 for alarm objects 85
Software failed alarm 134 TCXO (oscillator) failure alarm 134
Tellabs 6300 manager
Software failure alarm 134
alarm rules for monitoring 103
SourceObjectInst field
TeMIP Client window 43
Temperature too high alarm 134
Specific Problems attribute
Terminate operation 113
Terminated icon 26
SSF alarm 134
Terminating an alarm 55
Stages for an alarm 51
Termination Policy attribute
Start Time attribute
for alarm rules 95
Termination Time Stamp attribute
State attribute
for alarm objects 25, 88
Termination User Identifier attribute
for alarm rules 100
icons 25
Text File attribute
State Change Definition attribute
Threshold Info attribute
State icons 25
State parameter
Time of Last Evaluation attribute
of Purge_alarms operation 109
for alarm rules 100
Status attributes
TIP missing alarm 134
Toxic gas alarm 134
for alarm rules 99
Transceiver Response Fail alarm 135
Transceiver Supply Voltage Out of Range
Status Condition Explanation attribute
alarm 135
Transceiver Temperature Out of Range alarm 135
Storage capacity problem alarm 134
Transmit degraded alarm 135
Structure of documentation 7
MA268 • Rev. B1 157

Alarms
Transmit failure alarm 135

Trend Indication attribute
True icon (clearance) 26
True icon (correlated notif info) 27
U
UB power too high alarm 135
UB power too low alarm 135
UB1 power missing alarm 135
UB2 power missing alarm 135
Unit initialising alarm 135
Unit main type mismatch alarm 135
Unit missing alarm 136
Unit sub type mismatch alarm 136
Unit temperature too high alarm 136
Unit temperature too low alarm 136
Unknown LMIP probable cause <ID> alarm 136
User Identifier attribute
User Text attribute
User-defined 1 alarm 136
V
Vcc (+5V) voltage too high alarm 136
Vcc (+5V) voltage too low alarm 136
VCO (oscillator) failure alarm 136
VCXO (oscillator) failure alarm 136
Vee (-5V) voltage too high alarm 137
Vee (-5V) voltage too low alarm 137
Ventilations system failure alarm 137
W
Warning Problem Occurrences attribute
158 MA268 • Rev. B1

Alarm Handling Ma268 b1 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarm Handling Ma268 b1 PDF

Uploaded by

Copyright:

Available Formats

Technical Documentation

Product family Tellabs® 6300 Managed

Title Working in Tellabs 6300 Manager Vol. 3:

Document User’s Manual

Copyright © 2005 Tellabs. All rights reserved.

Revision history This manual has changed as follows:

Rev. Date Description of Changes

A1 Oct. 15, 2002 First revision

Part I: Overview of Alarm Handling

2 Alarm Entities and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Part II: Work Procedures

Part III: Reference Information

7 Alarm Rule Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8 Alarm Rules for System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 103

10 Alarm Text Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

11 Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

The structure of this This documentation is structured as follows:

Abbreviations AIS Alarm Indication Signal

Part I: Overview of Alarm Handling

• ‘1 Alarm Handling’ on page 13

• ‘2 Alarm Entities and Attributes’ on page 21

• ‘3 Alarm Filters’ on page 29

1.1 The Principles of Alarm Handling

Note: If no information is available for one or more of these attributes, then

Alarm logging When an alarm is received, it is immediately registered in an alarm log. An

perceived to have disappeared — for example, due to a repair — a new

1.2 Alarm Indication

Indeterminate Blue violet

2 Alarm Entities and Attributes

2.1 Alarm Entities

2.1.1 The Operation Context

2.1.2 The Alarm Rule

Type of alarm rule Description

change of rule Monitor the value of an attribute and generate an

comparison rule Compare the value of an attribute for, for in-

occurs rule Generate an alarm if a specified event occurs.

occurs n time rule Generate an alarm if a specified event occurs a

2.2 Attributes for Alarms

4 Click OK to make the changes and close the window.

2.2.1 The Event Time Attribute

2.2.2 The Main_Object Attribute

Description The Main_Object attribute is a user-friendly attribute. The information here is

2.2.3 The Detailed_Object Attribute

Description The Detailed_Object attribute is a user-friendly attribute. The information here

2.2.4 The Alarm_Text Attribute

Description The Alarm_Text attribute is a user-friendly attribute. It describes what fault

2.2.5 The Perceived Severity Attribute

Severity level Explanation

Clear A clearance alarm.

Warning A problem that may become worse if not han-

Minor A minor problem, sometimes a consequence of a

Major A severe problem that requires action very soon.

Critical A severe problem that requires immediate action.

Indeterminate The severity level could not be determined. It is

2.2.6 The Probable Cause Attribute

2.2.7 The State Attribute

Icon Name Description of State

Outstanding The alarm has not yet been acknowledged.

Icon Name Description of State

Acknowledged The alarm has been acknowledged but not

Terminated The alarm has been terminated but not yet

2.2.8 The Clearance Attribute

True The alarm has been cleared.