Escolar Documentos
Profissional Documentos
Cultura Documentos
Product family
Product name
Title
Document
Users Manual
MA268 / Revision F1
Legal Notices
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 licenses and copyright laws. Unauthorized reproduction, modification, distribution, 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 Operations, 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, EXPRESS/PATH, FOCUS, MARTIS, MARTISDXX, MARTIS logo, MARTISDXX logo, METROVANTAGE, METROWATCH, NETREACH,
NETWISE, SCULPTURED SOUND, TELLABS, TELLABS and T symbol, 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.
MA268 Rev. F1
Revision Information
Revision Information
Revision history
Date
Description of Changes
A1
First revision
B1
B2
B3
C1
Sept. 1, 2007
C2
D1
E1
F1
Mar 3, 2009
MA268 Rev. F1
Revision Information
MA268 Rev. F1
Contents
Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1
1.2
1.3
2.2
Alarm Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1.1
The Operation Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1.2
The Alarm Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Attributes for Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.1
The Event Time Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.2
The Main_Object Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.3
The Detailed_Object Attribute . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.4
The Alarm_Text Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.5
The Perceived Severity Attribute . . . . . . . . . . . . . . . . . . . . . . 27
2.2.6
The Probable Cause Attribute . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.7
The State Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.8
The Clearance Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.9
The Pseudo Alarm Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.10 The Correlated Notifications Attribute . . . . . . . . . . . . . . . . . . . 28
Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1
Supervising Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1
5.2
5.3
MA268 Rev. F1
Operation Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.1.1
Creating Operation Contexts in a Domain . . . . . . . . . . . . . . . 37
4.1.2
Managing Operation Contexts . . . . . . . . . . . . . . . . . . . . . . . . 38
4.1.3
Deleting Operation Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.1.4
Specifying Accumulation of Similar Alarms . . . . . . . . . . . . . . 44
Contents
6.2
8.3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Computer Hardware Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.2.1
Alarm Rules for SNMP Entities . . . . . . . . . . . . . . . . . . . . . . . 105
8.2.2
Alarm Rules for Bridge LAN Interfaces . . . . . . . . . . . . . . . . . 106
8.2.3
Alarm Rules for Bridge Leased Lines Interfaces . . . . . . . . . 106
8.2.4
Alarm Rules for Disk Storage . . . . . . . . . . . . . . . . . . . . . . . . 107
Computer Software Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.3.1
Alarm Rules for Alarm Logs . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.3.2
Alarm Rules for Alarm Escalation . . . . . . . . . . . . . . . . . . . . . 108
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
9.1
9.2
9.3
153
MA268 Rev. F1
Preface
Preface
The purpose of this
documentation
ple, you must know how to navigate in a tree structure and how to activate 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.
MA268 Rev. F1
Style conventions
Preface
Abbreviations
AIS
CCITT
ITU
OSI
References
[1] MA266, Tellabs 6300 Managed Transport System, Tellabs 6300 Network Manager, Working in Tellabs 6300 Manager, Vol.1: Principles of
Operation, Users Manual
[2] MA267, Tellabs 6300 Managed Transport System, Tellabs 6300 Network Manager, Working in Tellabs 6300 Manager, Vol.2: Using the Network Editor, Users Manual
[3] MA269, Tellabs 6300 Managed Transport System, Tellabs 6300 Network Manager, Working in Tellabs 6300 Manager, Vol.4: Using the Entity
Browser, Users Manual
MA268 Rev. F1
Preface
[4] MA360, Tellabs 6300 Managed Transport System, Tellabs 6300 Network Manager, Managing SDH and Ethernet Trails, Users Manual
[5] MA333, Tellabs 6300 Managed Transport System, System Administration Guide and Reference for FP3.0.x (Alpha), Users Manual
[6] MA370, Tellabs 6300 Managed Transport System, System Administration Guide and Reference for FP3.0.x (SUN), Users Manual
[7] TeMIP Client V5.1 for Windows, On-line help Alarm Handling
[8] TeMIP Client V5.1 for Windows, On-line help Alarm History
[9] TeMIP Client V5.1 for Windows, On-line help TeMIP Desktop
[10] TeMIP Notification FM, Alarm Rules FM and Collection AM Users
Guide
MA268 Rev. F1
10
Preface
MA268 Rev. F1
MA268 Rev. F1
11
12
MA268 Rev. F1
Alarm Handling
This chapter introduces the principles in alarm handling and describes how
alarms are indicated in the Tellabs 6300 manager user interface.
Overview
1.1
1 Alarm Handling
Introduction
Definition of alarms
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 presents the alarms to the operator.
MA268 Rev. F1
13
Alarm information
1 Alarm Handling
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
14
MA268 Rev. F1
1 Alarm Handling
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 enables 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 following attributes:
Alarm Origin
State
Problem Status
Handled by
Alarm Report Clearance Received
Correlated Notifications
Perceived Severity
Event Type
Probable Cause
Managed Object
Target Entity
Additional Text
Event Time
Domain
Operator Note
Specific Problems
OC Name
Identifier
Original Severity
Notification Identifier
Similar Alarms
Problem Occurrences
Original Event Time
User Text
User Identifier
MA268 Rev. F1
15
1 Alarm Handling
Create Statistics on Operation Context this option provides a new window 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 53
Alarm logging
Alarm responsibility
from other areas. Only alarms from his own area will normally be visible.
Note: In Tellabs 6300 manager, the fields of responsibility or areas in connec-
Alarm clearance
16
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
MA268 Rev. F1
1 Alarm Handling
Alarm integration of 7100 alarms via a TMF 854 soap/XML interface to Tellabs 7194 manager is possible. 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
Domain
Peceived Severity
Probable Cause
Alarm Text
Additional Text
1.2
Alarm Indication
MA268 Rev. F1
17
1 Alarm Handling
Links have a series of triangles along the trail that are colored to indicate
the severity of the alarm as configured on server trail.The three alarm indications in the Network Management window - colored background of NE
icon, exclamation mark and colored triangles along the link can appear in
any combination at the same time or either of the three.When the alarm
has been cleared or terminated, the alarm indication display disappears.
Note: For more information about configuring alarm on server trail, see [4]
In the Find Trail window, the complete line of alarm information is colored
and shows the severity of the alarm.
In the Alarm View window, the severity column is colored which also
shows the severity of the alarm.
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 window manually before the color is removed.
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 indicating an alarm and thereby display its child entities.
Note: When several alarms exist for the same entity, the color from the alarm
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 table 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 Network
Management, Trail View, Alarm View and Find Trail windows. For more
18
MA268 Rev. F1
1 Alarm Handling
Examples of alarm
indication in TeMIP
Client
The figure shows how the same alarm is indicated in different ways in different types of windows.
Examples of alarm
indication in 6300
Network Management
The figure shows how the same alarm is indicated in different ways in different types of windows.
1.3
Gathering information
about alarms
MA268 Rev. F1
The Network Management window uses colored background of NE icons, exclamation mark "!" and colored triangles to indicate alarms. The colored background of NE icons indicates alarm in NE and exclamation mark "!" to indicate that NE is unreachable. The colored triangles indicate the severity of the
alarm on links as configured on server trail, for more information about con-
19
1 Alarm Handling
figuring alarm on server trail, see [4]. These three alarm indications in Network
Management window - colored background of NE icon, exclamation mark and
colored triangles along the link can appear in any combination at the same
time or either of the three. Excluding exclamation mark, the colored back
ground of NE icon and triangles give an idea to the severity of the alarm, these
do not give any information about the individual alarm, or alarms. This information is provided by windows that are accessed using the pop-up menu for
the selected item in the Network Management window.
Alarm in
NE
Link
20
Menu item
Result
Description
MA268 Rev. F1
1 Alarm Handling
The Alarm View window displays a list of all the alarms associated with the NE
or link. Each line in the table contains details about the individual alarm.
Note: Alarm information is not updated automatically. You must select View
Refresh to update the contents of the window.
Description
OC
Alarms ID
Severity
Event Time
Alarm Type
A text string that indicates the type of fault that generated the alarm.
Alarm Text
Main Object
Detailed Object
This indicates more accurately where in the Main Object the fault has occurred.
Domain
The Alarm View window has a pop-up menu. When an individual alarm is selected, it is possible to do one or more of the following:
Save all the alarm details in the table to file
Display the all the trails affected by the alarm in the Find Trails window
Show the NE or link that is generating the alarm in the Network Management window
MA268 Rev. F1
21
The relationships
between windows with
alarm indicators
1 Alarm Handling
Several windows in the Network Management window that have alarm indicators are linked. The figure below shows the links between these windows.
Note: For more information about the Find Trails window, see [4].
22
MA268 Rev. F1
Overview
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
The following entities must be set up to enable the reception and handling of
alarms:
Overview
2.1.1
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 divided into a number of domains that together form a hierarchy, where the top domain is at the highest level. The alarm handling function, which receives, handles and logs alarms, is organized in a similar way. Each major domain is assigned an operation context, in which all alarms that originate from that domain are received, handled and stored.
Note: The assignment of an operation context to a domain is fixed and cannot
easily be changed.
In a standard T6300NM FP3.0.x installation, the following domains and operation contexts are created automatically:
network domain and oc_network operation context: these are used to monitor network elements.
lnd_man domain and oc_lnd_man operation context: these are used to
monitor LNDs and trails.
Note: These domains and operation contexts may, or may not, be used in sys-
tems where users have defined new domains and OCs to monitor their
systems.
MA268 Rev. F1
23
An example
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 context for domain B.
Note: Domains b1, b2, and b3 share a single operation context, for instance be-
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
2.1.2
Definition
An alarm log is attached to each operation context. This logs all the alarms received in the operation context. The contents of the alarm log can be displayed, and you can search for specific groups of alarms.
24
MA268 Rev. F1
that is not part of the managed network, such as a thermometer measuring the
temperature in the computer room.
Types of alarm rules
2.2
Description
change of rule
comparison rule
Compare the value of an attribute for, for instance, an NE to a specified constant value by using a relational operator, for example > (greater
than). When you apply a comparison rule, the
system will check the value of the attribute at regular 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 automatically, if the temperature falls below the limit.
expression rule
occurs rule
Information from
attributes
The information contained in the alarm attributes is normally sufficiently detailed for the operator to take appropriate action. However, it is often the combination 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 explanation.
The attributes for an alarm provide information about such things as, for example, 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 82 for a description of all alarm attributes. You can
change the number and type of attributes shown, see To change the alarm attributes shown in the Real Time View window on page 26.
MA268 Rev. F1
25
It is possible to change the number and type of attributes shown in the Real
Time View window and the History View window. To do this:
Step
Action
Open the pop-up menu at the top of the table in the Real Time View or
History View window.
Select Customize....
The RT Alarms window or History Alarms window appears.
Use the buttons in the window to move the relevant field names and
set the order in which they appear.
For a full description of how to customize the attributes shown, see
[7].
2.2.1
Description
2.2.2
Description
2.2.3
Description
2.2.4
Description
26
MA268 Rev. F1
2.2.5
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.
Tellabs 6300 manager as well as the management equipment distinguish between different levels of severity. Some errors are estimated to be severe, because 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 international standards, six levels of severity exist. The table shows them in increasing order of severity.
Severity level
2.2.6
Explanation
Clear
A clearance alarm.
Warning
A problem that may become worse if not handled, for instance that the alarm log is 40% full.
Minor
Major
Critical
Indeterminate
Description
Note: Do not try to interpret this in isolation, but combine it with the other attributes, for example Alarm_Text, to get an idea of the problem causing
the alarm.
2.2.7
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.
Name
Outstanding
MA268 Rev. F1
Description of State
27
Icon
Name
Description of State
Acknowledged
Terminated
Note: The last icon does not appear in the Real Time View window. The com-
2.2.8
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.
Name
True
2.2.9
Description
Description
Note: For details about how to change this setting, see [7].
The clearance report flag
icon
Name
True
2.2.10
Description
28
Description
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-
Name
True
MA268 Rev. F1
Description
29
30
MA268 Rev. F1
3 Alarm Filters
Alarm Filters
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.
Overview
For a full description about creating and using the alarm filters, see [7] and [8].
3.1
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 filter are displayed.
Note: Alarm filters are a display function only. The collection of alarms is not
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
MA268 Rev. F1
The figure shows the Alarm Handling Filter Editor window. You use this window to set up alarm filtering requirements and create alarm filters. To open
31
3 Alarm Filters
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 Filter 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 patterns, see 5.1.3 Setting Up Alarm Filters on page 51.
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. After 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 attributes. 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
32
MA268 Rev. F1
3 Alarm Filters
Identifier
Main_Object
Managed Object
Notification Identifier
OC Name
Operator Note
Original Event Time
Original Severity
Outage Flag
Perceived Severity
Probable Cause
Problem Occurrences
Problem Status
Security Problem Cause
Similar Alarms
Specific Problems
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 82.
Example of a filter
pattern
MA268 Rev. F1
Filter patterns are often used to reduce the number of alarms displayed when
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 displayed. The figure shows how the pattern is defined, how it is displayed in the
33
3 Alarm Filters
Filter View and the effect it has on the alarms displayed in the Real Time View
window
34
MA268 Rev. F1
MA268 Rev. F1
35
36
MA268 Rev. F1
Overview
4.1
Operation Contexts
This section contains the following information:
Overview
4.1.1
Introduction
As mentioned in 2.1.1 The Operation Context on page 23, the total alarm collection 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 operators 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 sub-domains if the parent domain is already covered by an operation context.
The existing operation contexts are represented by icons in the
operation_contexts domain. This is the domain where you create and delete
operation contexts that collect alarms at the network element level. Alarms for
operation contexts present in this domain are used to calculate the operational
state of trails. This, thereby, influences the generation of trail alarms.
To create an operation
context in a domain
This procedure describes how you define an operation context for a specific
domain and register it in the TeMIP database.
Step
Action
Start the T6300 network management system and log on to the correct server.
MA268 Rev. F1
37
Step
3
Action
Keep the Directive View window open as you need to copy the text in
the Entity field later on in this procedure.
4.1.2
38
There are 2 main entry points to manage operation contexts. The entry point
that you use depends on which task you are actually doing at the time. But re-
MA268 Rev. F1
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
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
view from T6300 network
manager
This procedure describes how to open the directive view for an operation context when you open it from the T6300 network manager.
Step
Action
Start the T6300 network management system and log on to the correct server.
MA268 Rev. F1
39
Step
Action
This procedure describes how to open the directive view for an operation context when you open it from the TeMIP Client.
Step
1
Action
Note: This is an example of how the TeMIP Client can appear. How it
40
MA268 Rev. F1
Step
2
Action
If the Operation Context View window is not open in your TeMIP Client window, select Window OC View.
If the OC View window already contains the desired operation context in the list of operation contexts, go to Step 7.
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.
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.
Select the desired operation context(s) and click Add to add it to the
Alarm Handling Operation Context List field.
Click OK. The operations contexts present in the Alarm Handling Operation Context List appear in the OC View window.
In the OC View window, open the pop-up window for the desired operation context and select Open in New Management View....
The OPERATION_CONTEXT <oc name> window appears.
MA268 Rev. F1
41
To perform an operation
on an operation context
This procedure describes how you perform an operation on an operation context in the directive view.
Step
Action
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 39
To open the directive view from the TeMIP Client on page 40
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
The specific operations for operations contexts are described in 9.1 Special
Operations for Operation Contexts on page 109.
Operations
4.1.3
To delete an operation
context
42
This procedure describes how you remove an operation context from the
man_env domain.
Step
Action
Select all the alarms for the desired operation context and terminate
them all (see To terminate an alarm on page 57).
MA268 Rev. F1
Step
Action
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 39
To open the directive view from the TeMIP Client on page 40
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
MA268 Rev. F1
43
Step
Action
10
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
The selected operation context is now removed from operation context list.
4.1.4
To accumulate similar
alarms
This procedure describes how to change the settings for an operation context
so that similar alarms are shown once only.
Step
Action
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 39.
To open the directive view from the TeMIP Client on page 40.
Set the operation contexts Similarity Mode attribute to SameProblemType or SameProblemTypeAndSeverity, depending on the required
similarity criterion.
See Similarity Mode on page 76.
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
The changes are now active in Real Time View window in the TeMIP
Client.
44
MA268 Rev. F1
5 Supervising Alarms
Supervising Alarms
This section contains the work procedures for starting alarm collection and for
inspecting and handling the received alarms. This is described in the following sections:
Overview
Note: If you require full details about the TeMIP Client window, and/or the as-
5.1
Overview
5.1.1
The main window for the alarm handling function of Tellabs 6300 manager is
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 The Operation Context View window on
page 47). You are also able to retrieve alarm information from the alarm log
(the History View window, see The History View window on page 58). The
figure shows the contents of the Real Time View window.
45
5 Supervising Alarms
The operation context view (OC View). This shows a list of operation contexts. 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 happening 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 directive view, which shows all the values for the attributes associated with the
selected alarm.
To open the Real Time
View window
This procedure describes how you open the Real Time View window, which
gives you a list of active alarms.
Step
1
Action
46
MA268 Rev. F1
5.1.2
5 Supervising Alarms
Introduction
The figure shows an example of the Operation Context View window. Within
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.
The OC View contains a number of symbols, or icons. Some of the more common ones are described below. For a complete list of symbols and explanations see [7].
Column
Administrative State
Icon
Description
Locked
Unlocked
Shutting Down
Unknown
Operational State
Unknown
Off
On
MA268 Rev. F1
47
Column
Monitored
5 Supervising Alarms
Icon
Description
This procedure describes how you open the Operation Context List window.
Step
Action
In the OC View window, open the pop-up menu and select OC List....
The Operation Context List window appears.
Note: If you have not used the OC list window, then the fields in the
window are empty.
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.
To add an operation
context to the list in the
OC View
This procedure describes how you include an operation context in the list in
the Operation Context View window.
Step
Action
In the OC View window, open the pop-up menu and select OC List....
The Operation Context List window appears.
Note: If no operation contexts appear, see To open the Operation
Context List window on page 48 and display all the operation contexts.
48
MA268 Rev. F1
5 Supervising Alarms
Step
Action
Select the desired operation context(s) in the Available Operation Context field and click Add.
The selected operation context(s) is added to the list in the Alarm
Handling Operation Context List field.
Click OK.
The OC List window closes and the operations contexts present in the
Alarm Handling Operation Context List appear in the OC View window.
Note: The operation contexts are disabled. While they have this state,
no alarms appear in the Real Time View window.
To remove an operation
context from the list in
the OC View
This procedure describes how you remove an operation context from the list
in the Operation Context View window.
Step
Action
In the OC View window, open the pop-up menu and select OC List....
The Operation Context List window appears.
Note: If no operation contexts appear, see To open the Operation
Context List window on page 48 and display all the operation contexts.
2
Select the desired operation context(s) in the Alarm Handling Operation Context List field and click Remove.
The selected operation context(s) is added to the list in the Available
Operation Contexts field.
MA268 Rev. F1
49
Step
3
5 Supervising Alarms
Action
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.
This procedure describes how you enable the display of alarms from a specific
operation context.
Step
Action
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 48.
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.
This procedure describes how you disable the display of alarms from a specific operation context.
Step
Action
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 48.
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 window are removed.
50
MA268 Rev. F1
5.1.3
5 Supervising Alarms
This procedure describes briefly how you define a pattern for an alarm filter.
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.
Note: Some of the criterion fields support regular expressions (string or entity
data types).
Step
Action
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.
For a full description of how to create, edit and enable alarm filters,
see [7]
2
In the Filter Editor window, provide a name for the filter. (If the editor 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
When you have given a new name, click outside of the editor field to
keep the name.
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.
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.
MA268 Rev. F1
51
Step
7
5 Supervising Alarms
Action
d) Go to Step 8
8
This procedure describes how you inspect the criteria of an existing filter pattern.
Step
Action
In the Real Time View window or the History View window, expand
the tree structure in the alarm filter area.
Select the desired filter from the list and expand the tree structure for
this filter.
The filter patterns 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
Action
In the Real Time View window or the History View window, expand
the tree structure in the alarm filter area.
Open the pop-up menu for the desired filter and select Delete Pattern.
The filter name is removed from the list.
52
This procedure describes how you select a filter pattern that you want to use.
Step
Action
In the Real Time View window or the History View window, expand
the tree structure for the user-defined filter patterns in the alarm filter area.
MA268 Rev. F1
5 Supervising Alarms
Step
2
Action
This procedure describes how you clear the use of any filter whatsoever. That
is, how you display all not-closed alarms again.
Step
Action
In the Real Time View window or the History View window, expand
the tree structure for the user-defined filter patterns in the alarm filter area.
5.2
Introduction
5.2.1
The table describes the stages that an alarm passes through from it is received
till it is archived.
Stage
1
Description
MA268 Rev. F1
53
Stage
3
5 Supervising Alarms
Description
6300 manager. It remains in the alarm log. From here it can be retrieved and inspected later (see 5.3 Using the History View to View
the Alarm Log on page 58).
6
54
MA268 Rev. F1
Stage
7
5 Supervising Alarms
Description
5.2.2
Acknowledging Alarms
To acknowledge an
alarm
This procedure describes how you acknowledge an alarm, to indicate that you
will take action to get the underlying problem solved.
Step
Action
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 more information about the state attributes and icons, see
2.2.7 The State Attribute on page 27.
5.2.3
This procedure describes how you concentrate on only some alarms. For instance, alarms from one operation context or one NE and/or alarms with a
minimum level of severity.
Step
1
Action
MA268 Rev. F1
This procedure describes how you show all attributes that have been set for a
specific alarm.
55
5 Supervising Alarms
Note: The alarm information list in the Real Time View window only shows a
Action
In the Real Time View window, open the pop-up menu for the desired
alarm, or alarms, and select Open in New Management View....
The OPERATION_CONTEXT <oc name alarm_object n> window appears.
Note: There are multiple tabs available in this window. For full de-
tails about this window and the tabs in this window, see [9].
To manage the entity
that caused the alarm
Action
In the Real Time View window, open the pop-up menu for the desired
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
note
Action
In the Real Time View window, open the pop-up menu for the desired
alarm, or alarms, and select Set Operator Note.
The Set Operator Note window appears.
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 55.
56
MA268 Rev. F1
5.2.5
5 Supervising Alarms
Terminating Alarms
To terminate an alarm
Action
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.
For more information about icons, see Attribute icon changes on
page 57.
Attribute icon changes
5.2.6
When an alarm is terminated in the History View window, the attribute icons
change. This is illustrated in the diagram below.
Note: When the alarm is terminated, it is removed from the alarm list in the
Real Time View window.
MA268 Rev. F1
57
Pseudo-alarm
5 Supervising Alarms
When an alarm clearance has been matched to an existing alarm and has terminated it, a pseudo-alarm with information about the clearance is displayed
in the Real Time View window. The pseudo-alarm is indicated by the icon
shown in the figure.
5.3
58
MA268 Rev. F1
5.3.1
5 Supervising Alarms
This procedure describes how you open the alarm log in the TeMIP Client window.
Step
1
Action
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 (History).... 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.
MA268 Rev. F1
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.
59
5.3.2
5 Supervising Alarms
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 [8].
To define a search
pattern
Action
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.
which attributes the search pattern uses. The name cannot be modified once you have moved to the next window.
3
Click OK.
The History Alarm Handling Search Pattern window appears.
60
Select the correct values in the Attribute Name, Condition and Values
fields.
MA268 Rev. F1
Step
6
5 Supervising Alarms
Action
If you want to apply additional attributes to the search pattern, repeat Step 4 and Step 5.
Example - Searching alarms from a specific NE: Select the attribute
name Managed Object and type in the NE name as value, for instance, t6350_21 A_0102. Insert a new row and select the attribute
name Scope and select the value WholeSubtree. The search pattern is
shown in the figure below.
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 patterns are now available in all History View windows.
To change a search
pattern
This procedure describes how you change the attributes of a search pattern.
Note: The search pattern name remains the same.
Step
Action
In the Search Pattern tab of the History View window, open the popup menu for the search pattern you want to change and select Properties.
The History Alarm Handling Search Pattern window appears.
Select the row of attributes you wish to change or click Insert Row if
you want additional attributes included.
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. F1
61
5 Supervising Alarms
Action
In the Search Pattern tab of the History View window, open the popup menu for the search pattern you want to use and select Apply Pattern.
This procedure describes how you apply a search pattern to a list of alarms in
a new window. This enables you to keep the original list alarms open in another History View window.
Step
Action
In the Search Pattern tab of the History View window, open the popup menu for the search pattern you want to use and select Apply Pattern In New.
A new History View window appears. The selected search pattern attributes are already applied to the list of alarms that appears.
To delete a search
pattern
Action
In the Search Pattern tab of the History View window, open the popup 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
Introduction
62
Purging Alarms
When alarms are not purged automatically from the alarm log during the archiving process (see the Purge parameter in the operation Archive on page
112), they can be purged with a specific operation.
MA268 Rev. F1
5 Supervising Alarms
Action
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 39
To open the directive view from the TeMIP Client on page 40
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
All the alarms for this OC are purged.
MA268 Rev. F1
63
5 Supervising Alarms
Step
Action
Depending on the directive view you are using, do one of the following:
Select Operations Start, or
Click the Execute directive button (green arrow).
See the description of the operation and its parameters in
Purge_alarms on page 110.
64
MA268 Rev. F1
MA268 Rev. F1
65
66
MA268 Rev. F1
Overview
6.1
Introduction
6.1.1
OPERATION_CONTEXT
Allows you to enter a name for the operation context. This attribute is mandatory.
Rules for entity names
MA268 Rev. F1
67
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
Critical
Major
Minor
All alarms except indeterminate, critical and major ones are automatically acknowledged.
Warning
Clear
not-automatic
Determines the maximum time an alarm of severity Critical may remain unacknowledged before it escalates. Enter a relative time using the format ddhh:mm:ss. Enter 0 to avoid automatic alarm escalation. This is the default setting.
Automatic Escalation Major Delta Time
Determines the maximum time an alarm of severity Major may remain unacknowledged before it escalates. Enter a relative time using the format ddhh:mm:ss. Enter 0 to avoid automatic alarm escalation. This is the default setting.
Automatic Escalation Minor Delta Time
Determines the maximum time an alarm of severity Minor may remain unacknowledged before it escalates. Enter a relative time using the format ddhh:mm:ss. Enter 0 to avoid automatic alarm escalation. This is the default setting.
Automatic Escalation Warning Delta Time
Determines the maximum time an alarm of severity Warning may remain unacknowledged before it escalates. Enter a relative time using the format ddhh:mm:ss. Enter 0 to avoid automatic alarm escalation. This is the default setting.
68
MA268 Rev. F1
Description
False
True
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
Critical
All alarms except indeterminate ones are automatically terminated when closed.
Indeterminate
Major
Minor
All alarms except indeterminate, critical and major ones are automatically terminated when
closed.
Warning
Warning alarms and clearance alarms are automatically terminated when closed.
Clear
not-automatic
Specifies at which capacity threshold a ProcessingErrorAlarm should be generated 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 specified separated by commas. Alternatively, you can enter the thresholds in separate 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. F1
69
The severity of the generated alarms is determined by the value of the corresponding thresholds as follows:
Value
Description
0 - 40%
Severity: Warning
41 - 60%
Severity: Minor
61 - 80%
Severity: Major
81 - 100%
Severity: Critical
Discriminator Construct
Description
Locked
Unlocked
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 instead 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
70
MA268 Rev. F1
example, if the entity name is defined as oc_sys_man, you may want to show
System Management instead.
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 registered 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 registration, use the Change Entity Attributes... item in the pop-up menu.
Operation Context Description
Allows you to specify the telephone number of the responsible person or center.
Reduction Mode
Defines whether incoming alarms concerning the same problem are accumulated as similar alarms or not.
Value
Description
NonAutomatic
Automatic
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
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 operation context are made.
MA268 Rev. F1
71
Scheduling Package
Defines specific periods of alarm collection activity. Refer to [8] for further information.
Severity Propagation Mode
Defines how the value of the alarm objects Perceived Severity attribute is determined, according to the severities of the accumulated similar alarms.
Value
Description
Highest
First
Latest
The severity of the latest similar alarm in the accumulation is used (excluding clearance alarms).
Similarity Mode
Defines the criterion that is used during automatic alarm accumulation to decide whether alarms are similar (see Reduction Mode on page 71).
Value
Description
NotApplicable
SameProblemType
SameProblemTypeAndSeverity
Termination Policy
Description
None
AckandCleared
Automatic termination is possible when this value is selected and the state of the alarm object is
Acknowledged or Cleared.
Cleared
Automatic termination is possible when this value 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
72
MA268 Rev. F1
6.1.2
Name
Shows the name of the operation context assigned at registration. You cannot
set this attribute.
6.1.3
Description
NoUpdate
Replace
Associated Domain
Shows the name of the domain associated with the operation context (see Associated Domain on page 67). 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 68). Alarms
with severity levels less than or equal to this value are automatically created
as acknowledged.
Automatic Acknowledge on Handle
Determines the maximum time an alarm of severity Critical may remain unacknowledged before it escalates (see Automatic Escalation Critical Delta Time
on page 68).
Automatic Escalation Major Delta Time
Determines the maximum time an alarm of severity Major may remain unacknowledged before it escalates (see Automatic Escalation Major Delta Time
on page 68).
Automatic Escalation Minor Delta Time
Determines the maximum time an alarm of severity Minor may remain unacknowledged before it escalates (see Automatic Escalation Minor Delta Time
on page 68).
MA268 Rev. F1
73
Determines the maximum time an alarm of severity Warning may remain unacknowledged before it escalates (see Automatic Escalation Warning Delta
Time on page 68).
Automatic Terminate On Alarm Clearance
Determines the severity level of the alarms that will be terminated automatically when their Problem Status attribute changes to Closed (see Automatic
Terminate On Alarm Close on page 69). 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 generated to indicate that the alarm log is nearly full (see Capacity Alarm Threshold on page 69).
Database Service Name
Determines the behavior of the alarm log when its maximum capacity is
reached (see Max Log Size on page 74). You cannot set this attribute.
Value
Description
Wrap
Halt
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 attribute.
Operation Context Description
Determines a user-defined note describing the operation context (see Operation Context Description on page 71).
Owner Id
Shows the user ID of the user who created the operation context. You cannot
set this attribute.
74
MA268 Rev. F1
Ownership Control
Description
False
True
Outage Policy
Description
NoAction
Terminate
TerminateAndNotify
Acknowledge
Reduction Mode
Defines whether incoming alarms concerning the same problem are accumulated as similar alarms or not.
Value
Description
NonAutomatic
Automatic
Reduction Scope
MA268 Rev. F1
Description
NotTerminatedAO
OutStandingAO
75
Repository Location
Shows the directory pathname of the alarm log (see Repository Location on
page 71). You cannot set this attribute.
Responsible Operators
May hold the user IDs of the operators responsible for monitoring the operation context.
Scheduling Package
Defines specific periods of alarm collection activity. Refer to [8] for further information.
Severity Propagation Mode
Defines how the value of the alarm objects Perceived Severity attribute is determined, according to the severities of the accumulated similar alarms.
Value
Description
Highest
First
Latest
The severity of the latest similar alarm in the accumulation is used (excluding clearance alarms).
Similarity Mode
Defines the criterion that is used during automatic alarm accumulation to decide whether alarms are similar (see Reduction Mode on page 75).
Value
Description
NotApplicable
SameProblemType
SameProblemTypeAndSeverity
Termination Policy
76
Description
An alarm object can be terminated using the Terminate directive. This attribute supersedes the
value for Automatic Terminate On Alarm Clearance on page 69.
MA268 Rev. F1
Value
6.1.4
Description
AckAndCleared
Cleared
Description
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 70). Later it is set to Locked if the Suspend operation is carried out, and
to Unlocked if the Resume operation is carried out.
For more information, see 9.1 Special Operations for Operation Contexts on
page 109.
Value
Description
Locked
Unlocked
Shutting down
Note: Alarms are only collected when Administrative State is set to Unlocked,
and Operational State is set to Enabled (see Operational State on page
80).
Administrative State Change Timestamp
Shows the last time the Administrative State attribute was changed (see Administrative State on page 77).
Archive AO Age
Shows the value of the AO Age parameter (see Archive on page 112).
Archive AO Severity
Shows the value of the Severity parameter (see Archive on page 112).
Archive Begin Time
Shows the value of the Begin Time parameter (see Archive on page 112).
Archive Database Filename
Shows the value of the Database Name parameter (see Archive on page 112).
Archive End Time
Shows the value of the End Time parameter (see Archive on page 112).
MA268 Rev. F1
77
Shows the last error that occurred as a result of an automatic Archive operation
is carried out in the background (see Archive on page 112).
Archive Interval
Shows the value of the Interval parameter (see Archive on page 112).
Archive Last Time
Shows when the last automatic Archive operation (see Archive on page 112)
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 Archive on page 112). No value is returned if Archiving Status is set to Background Archive is Idle.
Archive Sequence Name
Shows the value of the Sequence Name parameter (see Archive on page 112).
Archive Sequence Number
Shows the value of the Sequence Number parameter (see Archive on page
112).
Archive and Purge
Shows the value of the Purge parameter (see Archive on page 112).
Archiving Status
Description
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.
78
MA268 Rev. F1
Availability Status
Disabled
Description of
Availability Status
Description
{ }
Degraded
Off duty
Failed
Dependency
Log Full
The operation context is disabled because the alarm log is full. You can
perform operations on existing operation contexts, but no new alarms
can be handled.
In Test
Power OFF
The operation context is disabled because the alarm collection has been
stopped by use of the temip_kill utility.
Shows the last time the Availability Status attribute was changed (see Availability Status on page 79).
Composite State
The value of this attribute reflects the health of the Operation Context (OC) instance in terms of service availability. This attribute reflects a combination of
the Operation State and the Administrations State (see Administrative State
on page 77).
Value
MA268 Rev. F1
Description
Active
Idle
The OC is locked.
79
Value
Not Functional
Description
Explains the current Composite State value (see Composite State on page 79).
Composite State Change Timestamp
Shows the status of the last error that caused the Operational State or Availability Status to change (see Operational State on page 80 and Availability Status on page 79).
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 determined by internal conditions within Tellabs 6300 manager.
Value
Description
Enabled
Disabled
Note: Alarms are only collected when Operational State is set to Enabled, and
Administrative State is set to Unlocked (see Administrative State on
page 77).
Operational State Change Timestamp
Shows the last time the Operational State attribute was changed (see Operational State on page 80).
Purge AO Age
Shows the value of the AO Age parameter (see Purge_alarms on page 110).
Purge AO Severity
Shows the value of the Severity parameter (see Purge_alarms on page 110).
Purge AO State
Shows the value of the State parameter (see Purge_alarms on page 110).
80
MA268 Rev. F1
Shows the value of the Begin Time parameter (see Purge_alarms on page
110).
Purge End Time
Shows the value of the End Time parameter (see Purge_alarms on page 110).
Purge Error Status
Shows the last error that occurred as a result of an automatic Purge_alarms operation carried out in the background (see Purge_alarms on page 110).
Purge Interval
Shows the value of the Interval parameter (see Purge_alarms on page 110).
Purge Last Time
Shows when the last automatic Purge_alarms operation was carried out (see
Purge_alarms on page 110). No value is returned if the last Purge_alarms operation was carried out manually.
Purge Next Time
Shows when the next automatic Purge_alarms operation will be carried out
(see Purge_alarms on page 110). 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 background (see Purge_alarms on page 110).
Value
Description
Resumed By User
Shows the ID of the user who carried out the last Resume operation (see Resume on page 110).
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 80 and Availability Status on page 79).
Suspended By User
Shows the ID of the user who carried out the last Suspend operation (see Suspend on page 110).
MA268 Rev. F1
81
6.1.5
Description
Shows the number of alarms that have been acknowledged, but not terminated.
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 alarms that have not yet been terminated.
AO Outstanding
Shows the number of alarms that have not yet been acknowledged.
AO Terminated
6.1.6
Managing Director
Identifies the server that is responsible for the operation context entity. You
cannot set this attribute.
6.2
Introduction
82
MA268 Rev. F1
6.2.1
Identifier
Shows the number of the alarm, assigned sequentially within the operation
context. You cannot set this attribute.
6.2.2
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
Allows you to assign a user-defined note to 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. 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 detected, 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. F1
83
Value
PhysicalViolation
ProcessingErrorAlarm
QualityofServiceAlarm
SecurityServiceOrMechanismViolation
TimeDomainViolation
Backed Up Status
Shows whether the entity from which the alarm originated is backed up by another 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
Shows the value(s) of the Managed Object attribute for alarms matched (correlated) with this one.
correlatedNotification
Shows the value of the Notification Identifier attribute for alarms matched (correlated) with this one.
Domain
Shows the domain in which the alarm originated, that is the domain containing 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
False
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
84
MA268 Rev. F1
Shows the name of the particular alarms archive. You cannot set this attribute.
Export Sequence Number
Shows the sequence number of the particular alarms archive. You cannot set
this attribute.
Logical_Operator_And
An operator that forms part of a boolean expression. The default value is and.
You cannot set this attribute.
Managed Object
Shows the name of the entity from which the alarm originated. This is the entity that is affected by the alarm and that changes color in the map window.
You cannot set this attribute.
Monitored Attributes
Not used.
Notification Identifier
Shows a number which identifies the alarm for future matching with a clearance alarm. You cannot set this attribute.
OC Name
Shows the full name of the operation context with which the alarm is associated. 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 equipment or by the alarm rule that generated it. You cannot set this attribute.
Value
MA268 Rev. F1
Description
Indeterminate
The highest severity. Appears in the Sev. columns in the Alarm Handling and the Alarms View
windows as Ind.
Critical
85
Value
Description
Major
Minor
Warning
Clear
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 95). 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
Not used.
Service Provider
Not used.
Service User
Not used.
Specific Problems
Not used.
86
MA268 Rev. F1
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 85). You cannot
set this attribute.
Threshold Info
Applies to alarms generated because a threshold has been exceeded, for instance a threshold specified in the Capacity Alarm Threshold attribute for an
operation context (see Capacity Alarm Threshold on page 69). 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 observed (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 defined by the user.
User Text
A free-form text string defined by the user who created the alarm object.
MA268 Rev. F1
87
6.2.3
Description
Shows when the alarm was acknowledged for the first time.
Acknowledgement User Identifier
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
Critical
All alarms except indeterminate ones are automatically terminated when closed.
Major
Minor
All alarms except indeterminate, critical and major ones are automatically terminated when
closed.
Warning
Warning alarms and clearance alarms are automatically terminated when closed.
Clear
not-automatic
Description
True
False
88
MA268 Rev. F1
Shows when the alarm was created as an object in Tellabs 6300 manager.
Escalated Alarm
Description
True
The alarm has escalated because it was not acknowledged within the time set in Automatic Escalation <severity> Delta Time for the severity in
question (see the description of the corresponding attributes).
False
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
Description
Not-Handled
Handled
Closed
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. F1
89
State
Description
Outstanding
Acknowledged
Terminated
Archived
6.2.4
Description
The Counters attributes for alarm objects describe how many alarms of a similar type that have been received.
Shows the total number of clearance alarms (severity Clear) that have been received for the same problem.
Critical Problem Occurrences
Shows the total number of alarms with the severity Critical that have been received for the same problem.
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 received for the same problem.
Minor Problem Occurrences
Shows the total number of alarms with the severity Minor that have been received for the same problem.
Problem Occurrences
Shows the total number of alarms that have been received for the same problem.
90
MA268 Rev. F1
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 received for the same problem.
MA268 Rev. F1
91
92
MA268 Rev. F1
Overview
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 101). Therefore, an alarm rule is most easily shown and modified by using Show and Set with the Rule attributes group.
7.1
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, Comparison 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
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 instead 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. F1
93
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 registration, 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. columns in the Alarm Handling and the Alarms View
windows as Ind.
Critical
Major
Minor
Warning
Clear
Auto Enable
Determines whether the alarm rule is enabled automatically when it is created. Later you can disable and enable it using the Disable and Enable operations.
For more information, see 9.2 Special Operations for Alarm Rules on page
114.
Value
Description
Yes
No
Category
Determines whether the alarm rule belongs to a user-defined group. Set the
attribute to the name of the group.
94
MA268 Rev. F1
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.
Alarm Fired Procedure
Specifies a script which is executed if the alarm fires. The script is typically
made by the system manager.
For more information about alarms, see [10].
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
83).
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
MA268 Rev. F1
95
Value
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
PerformanceDegraded
PowerProblem
PressureUnacceptable
ProcessorProblem
PumpFailure
QueueSizeExceeded
ReceiveFailure
96
MA268 Rev. F1
Value
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
Rule Expression
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-ddhh:mm:ss.
Example: 1997-07-30-16:00:00
MA268 Rev. F1
97
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-ddhh:mm:ss.
Example: 1997-08-31-16:00:00
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
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 attribute is monitored.
Example: equipment module aggr_pos_3 laser temperature
Relational Operator
98
Description
EQ
Equal to
LT
Less than
GT
Greater than
LE
GE
NE
Not equal to
MA268 Rev. F1
Comparison Values
Description
value,value
value,*
*,value
*,*
Comparison Value
Applies to comparison rules only. Determines the constant value that the attribute 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 monitored event must occur within the time period specified by Delta Time to generate an alarm (see Delta Time on page 100).
Example: 3 (with Delta Time set to 01:00:00, the event must occur three times
within one hour).
MA268 Rev. F1
99
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 generate an alarm (see Count on page 99).
Example: 01:00:00 (with Count set to 3, the event should occur three times
within one hour).
7.2
Identifiers Attributes
Description
The Identifiers attribute for alarm rules is also contained in the Alarm Rules attribute 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.
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.
For more information, see [10].
Category
Determines whether the alarm rule belongs to a user-defined group (see Category on page 94). Not shown if it has no value.
Description
Allows you to attach a note to the alarm rule (see Description on page 95).
Not shown if it has no value.
Expression
Defines the expression used to evaluate the rule. There are four types of expressions, 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 expressions.
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 95).
100
MA268 Rev. F1
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 94).
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-
Description
Indeterminate
Critical
Major
Minor
Warning
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 expression. 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.
MA268 Rev. F1
101
Shows the result of the last evaluation of the alarm rule expression.
Value
Description
True
False
Error
State
Description
Enabled
Disabled
Substate
Description
Running
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
102
MA268 Rev. F1
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 attribute, perform a Disable operation followed by an Enable operation.
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. F1
103
104
MA268 Rev. F1
Overview
8.1
Introduction
Alarm recognition
8.2
Introduction
All computer hardware alarms will appear in the oc_sys_man operation context since the alarm rules for computer hardware are placed in the sys_man
domain (and subdomains thereof).
8.2.1
Description
All SNMP entities of the sys_man domain can be monitored using the IP Poller 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 automatically cleared when the SNMP entity is reachable again.
Attribute values
Value
SNMP <entity name>
MA268 Rev. F1
Perceived Severity
Critical
Alarm Type
CommunicationsAlarm
Probable Cause
CommunicationsSubsystemFailure
105
Attribute
Additional Text
8.2.2
Value
IP Reachability Down ICMP ping failed on previously reachable entity. IP-Address = <IP-addr>
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
Managed Object
Value
SNMP <bridge name> INTERFACE 1
8.2.3
Perceived Severity
Major
Alarm Type
QualityOfServiceAlarm
Probable Cause
LANError
Additional Text
Ethernet degraded
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
Managed Object
Value
SNMP <bridge name> INTERFACE 2
106
Perceived Severity
Major
Alarm Type
QualityOfServiceAlarm
Probable Cause
LossOfSignal
Additional Text
MA268 Rev. F1
8.2.4
Description
The table shows the attribute values of the disk storage alarms.
Attribute
Managed Object
Value
Script .disks mcc_df <disk name>
Minor
Alarm Type
QualityOfServiceAlarm
Probable Cause
StorageCapacityProblem
Additional Text
tribute.
8.3
Introduction
An alarm log is nearly full (see 8.3.1 Alarm Rules for Alarm Logs on
page 107).
No network operator or other Tellabs 6300 manager user seems to respond to alarms in a certain operation context (see 8.3.2 Alarm Rules for
Alarm Escalation on page 108).
Both types of alarms will appear in the oc_man_env operation context.
8.3.1
Description
MA268 Rev. F1
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 determined by the Capacity Alarm Threshold attribute (see Capacity Alarm Threshold on page 69). A maximum of four alarms may be generated, ranging from
Warning to Critical.
107
Attribute values
The table shows the attribute values of the alarm log alarms.
Attribute
Value
Managed Object
Perceived Severity
Not fixed
Alarm Type
ProcessingErrorAlarm
Probable Cause
StorageCapacityProblem
Additional Text
8.3.2
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 something may be wrong.
Attribute values
The table shows the attribute values of the alarm escalation alarms.
Attribute
Value
Managed Object
Perceived Severity
Not fixed
Alarm Type
QualityOfServiceAlarm
Probable Cause
ResponseTimeExcessive
Additional Text
Note: This alarm occurs only if your Tellabs 6300 manager includes the alarm
escalation function.
108
MA268 Rev. F1
9 Operations
Operations
This chapter describes the special operations and their parameters for the entities connected to alarms. Default parameter values, if any, are either mentioned in the text or indicated in the tables by underscore.
Overview
9.1
Overview
Register
Description
Managing Director
Description
COMPLETE
PLAN
Directory
Description
MA268 Rev. F1
109
9 Operations
Resume
Description
Suspend
Description
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 parameters 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 parameter 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
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 conditions are fulfilled. The default setting is none, in which case all alarms fulfilling the AO Age and State conditions are purged.
Value
Indeterminate
110
Description
Value
9 Operations
Description
Critical
Major
Minor
All alarms except indeterminate, critical and major ones will be purged.
Warning
Clear
State
Determines which alarms fulfilling the specified Severity and AO Age conditions will be purged.
Value
Description
Terminated
Archived
Begin Time
Determines when the alarm purging operation starts. If specified, an automatic alarm purging 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-ddhh: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 automatic alarm purging 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-ddhh: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. F1
111
9 Operations
Cancel_purge
Description
Cancels automatic alarm purging for the selected operation context. See
Purge_alarms on page 110.
Archive
Description
Archives terminated alarms of a certain age and severity in an external database. The age and severity are determined by the AO Age and Severity parameters.
Archiving can be performed manually or can be set up to be performed automatically (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
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 accordance 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 numbers in accordance with the established convention in your setting. The default 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 ddhh: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
112
MA268 Rev. F1
9 Operations
fulfilled. The default setting is none, in which case all terminated alarms fulfilling the AO Age condition are archived.
Value
Description
Indeterminate
Critical
Major
Minor
Warning
Clear
Purge
Determines whether alarms will be purged automatically from the alarm log
when archived.
Value
Description
False
True
Begin Time
Determines when the archiving operation starts. If specified, an automatic archiving 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 archiving 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 automatic 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. F1
113
9 Operations
Cancel_archive
Description
9.2
Cancels automatic alarm archiving for the selected operation context. See Archive in Section 29.3.7.
Overview
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.
Allows you to modify the attributes of the alarm rule copy before it is placed
in the target domain.
Value
Description
No
Yes
Specifies the domain into which the alarm rule will be copied. The default setting is the current domain.
New Rule Name
Enable
Description
114
MA268 Rev. F1
9.3
9 Operations
Overview
Summarize
Description
Not used.
Acknowledge
Description
Terminate
Description
MA268 Rev. F1
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.
115
116
9 Operations
MA268 Rev. F1
Here the individual alarms of the Tellabs 6300 manager are described. The
alarms are sorted alphabetically by their alarm text.
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
MA268 Rev. F1
117
This alarm indicates that an AIS is forced into the corresponding signal.
Alarm received from NE in illegal format
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 increases 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 received 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 (following, 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:
MA268 Rev. F1
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
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 received from the NE at the far end
The direction indication for this alarm is that corresponding to a bridge request 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.
Note: This alarm is not caused by any operator error, but its likely cause is an
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 response could originate from another NE. The alarm is detected per interface
(East (slot 6) and West (slot 1)).
Note: This alarm is not caused by any operator error, but its likely cause is an
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 received within 8 consecutive frames. The alarm is detected per interface (East
(slot 6) and West (slot 1)).
Note: This alarm is not caused by any operator error, but its likely cause is an
Appears when the APS signalling does not work correctly, because the port in
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. F1
119
Appears for MSP 1+1 protection when the switching type is bidirectional, and
an illegal request code is received consistently.
APS illegal state
Appears when the APS signalling does not work correctly, because the port in
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 received from the NE at the far end
APS inappropriate request
Appears when the switching type is bidirectional, and an inappropriate request code is received consistently. Appropriate codes are requests with the
same or higher priority than the local request, or the Reverse request in response to the Exercise request or requests with higher priority than that.
APS selector mismatch
Appears when the APS signalling does not work correctly, because the port in
question has not received a valid response to a switch 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 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 correctly, 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.
Backward defect indication
Appears when a BDI defect is detected in the received signal. BDI Report must
be enabled for this alarm to be generated.
Battery discharging
120
MA268 Rev. F1
Battery failure
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 protocol (GFP) sink. This is similar to raising an AIS alarm upon receiving an AIS
signal.
Commercial power failure
Appears when resynchronization has been selected for a module other than a
TEX1 Resync or TEX1P Resync (mon PDH) module.
Cooling fan failure
MA268 Rev. F1
121
Applies when the AUX port in question is configured as an input AUX port
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.
CTRL CRC error
Appears when five consecutive LCAS control packets are received with incorrect CRCs on a VCG member.
Degraded signal
Appears when the bit error ratio for the signal in question exceeds the threshold defined in the corresponding BER Threshold attribute.
Digital diagnostics not supported
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.
Note: This alarm is not cleared automatically. You must clear it manually.
Enclosure door open
122
MA268 Rev. F1
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, 6335, 6340, 6345 and 6350.
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to Engine failure. Appears when the signal on the port is
high or low depending on the setting of Polarity.
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 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.
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 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.
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 usage 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.
MA268 Rev. F1
123
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.
Explosive gas
Appears when two or more VCG members have been received with the same
SQ number indication in their LCAS control packet SQ fields, or if LCAS control packet CRC errors are detected in one or more members.
Failure of protocol Tx
Appears when an OK VCG member status is received from the far end corresponding to a member that is not presently in the VCG. That is to say, in the
local Tx direction no member with the corresponding SQ number is currently
sending either NORM, EOS, DNU or ADD in the CTRL field of the LCAS control packet.
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 completely.
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 completely.
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.
124
MA268 Rev. F1
Appears when FEC BER Injection is enabled. This warns you that the bits in
the signal are being changed in order to provide a check.
Firmware File Missing
Appears when a file with firmware for a module is missing. The problem can
be solved by downloading the firmware build file for the particular NE type
to the NE.
Fire
Appears when the FPGA file is missing for the slot in question.
MA268 Rev. F1
125
Appears when the frequency of the signal received at the input port in question is out of range, or when the frequency of the clock signal from the PLL
circuit on the receiver side is unlocked.
Fuse failure
Appears when the actual received EXI does not match the value of the expected EXI.
GFP type mismatch
Appears when the actual GFP type is not one of the supported types.
GFP UPI mismatch
Appears when the actual received UPI does not match the value of the expected UPI.
High humidity
126
MA268 Rev. F1
High temperature
Appears when the protection present between the main subrack and the tributary subrack is not coordinated, and the port in question has received a
switch request code that is not appropriate in the current state.
Ice build up
Appears when an insertion test access connection has been established with
the object in question as destination.
Internal HISI degraded
Appears when the number of parity errors on one of the internal interfaces between 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 between the components on the module in question.
MA268 Rev. F1
127
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, 6335, 6340, 6345 and 6350.
Appears when the frame signal on the internal section interface in question is
lost.
Intrusion detection
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 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.
128
MA268 Rev. F1
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.
Locked
Appears when the counting of channels present in the output signal has
stopped.
Loss of character synchronisation
Appears when loss of character synchronization (LCS) is detected in the received signal on the GE or FC-n physical section layer.
Loss of clock
Appears when the clock necessary for processing the traffic signal received on
the port is lost.
Loss of continuity
MA268 Rev. F1
129
Appears when the frame delineation algorithm of the protocol cannot identify
the frame start, and therefore the incoming signal is lost.
Loss of multiframe
Applies when Input is selected in the Direction: drop-down list, and Loss of optical signal 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.
Loss of pointer
Appears when the pointer in the incoming signal cannot be recovered correctly.
Loss of reference source
Appears when the timing signal from the input port in question is considered
lost.
Loss of signal
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 internal clock.
For 6345 and 6350.
Appears when the M3-1 or M6-1 module has lost the T0 clock from the corresponding M3-1 or M6-1 module.
Low battery threshold
130
MA268 Rev. F1
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
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, 6335, 6340, 6345 and 6350.
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to Low cable pressure. Appears when the signal on the port
is high or low depending on the setting of Polarity.
Low fuel
MA268 Rev. F1
131
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to Low water. Appears when the signal on the port is high
or low depending on the setting of Polarity.
Main power input supply failed
Appears when the PSF module in question has switched from the main power
supply to the secondary power supply.
MEG mismerge
Appears when ETH Segment OAM frames from different MEGs have
merged. More specifically, it appears when a MEP has received an OAM
frame with the correct MEG Level but with an unexpected MEG ID.
Member not deskewable
Appears when an LCAS member cannot be aligned with the master (deskewed) within the maximum supported differential delay. This can be
caused by too big a difference in the length of the routes. The signal from the
member is ignored.
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.
MSP IF degraded
Appears when the number of parity errors on the internal MSP interface section 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.
MS-SPRing switch active
Appears when the NE is in a bridged and switched state. This alarm appears
only when MS-SPRing Switch Reported is enabled.
NE software error: <error-specific text>
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.
132
MA268 Rev. F1
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.
Open connection indication
Appears when the Enable Frequency Offset Alarm attribute is selected and optical 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 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.
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
MA268 Rev. F1
133
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.
Partial Loss of Capacity Rx
Appears when fewer members of the VCG than configured in the Partial Loss
of Capacity Alarm Threshold are carrying traffic in the receive (Rx) direction.
Partial Loss of Capacity Tx
Appears when fewer members of the VCG than configured in the Partial Loss
of Capacity Alarm Threshold are carrying traffic in the transmit (Tx) direction.
Path trace mismatch
Appears when the actual received trail trace identifier does not match the value of Expected TTI.
Path unequipped
Appears when the actual received signal label does not match the expected
signal label.
Peer dying gasp
Appears only when power to a Tellabs 6305 ethernet media converter is lost.
Power down
134
MA268 Rev. F1
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)
Appears when the Port Forced Off attribute is selected in the Traffic Management 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)
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to Power problem. Appears when the signal on the port is
high or low depending on the setting of Polarity.
Power problem (Alternative 2)
Appears when the power level of the incoming or outgoing signal increases
above the upper high power-level threshold specified in the Thresholds window. 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 window. The alarm is cleared when the power level increases above the lower
high power-level threshold.
Proprietary information missing
Appears when the capabilities of the protection module in question are less
than those of the/all corresponding working module(s).
MA268 Rev. F1
135
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
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 power level of the incoming signal on the optical port increases to value greater than the value defined in the Upper High (dBm) field
in the Rx Power Threshold window.
Receive power too low
Appears when the power level of the incoming signal on the optical port becomes less than the value defined in the Lower Low (dBm) field in the Rx Power
Threshold window.
Rectifier failure
136
MA268 Rev. F1
Appears when the actual received trail trace identifier does not match the value of Expected TTI.
Selector A output squelched
Appears when the sequence number of the received VCG member does not
match the sequence number assigned to the specific VCG member.
Sequence out of range
Appears when the sequence number of the received VCG member is not within the defined range for the VCG members.
MA268 Rev. F1
137
Slot mismatch
Appears if the actual slot of an actual ETEX module does not match the slot
address stored in the module.
Smoke
Appears when the software used by the module in the slot in question constantly 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.
Note: This alarm is not cleared automatically. You must clear it manually.
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 the timing source selected in the Selector C window has been
suppressed because its quality level was too low compared to the level specified in Squelch quality Threshold.
TCXO (oscillator) failure
138
MA268 Rev. F1
Appears when the temperature of the power supply module increases above
the specified upper high limit. The alarm is cleared when the temperature decreases below the specified upper low limit.
TIP missing
Appears when one or both TIP modules are missing for the SIM1e module in
question.
Total Loss of Capacity Rx
Appears when no members of the VCG are carrying traffic in the receive (Rx)
direction.
Total Loss of Capacity Tx
Appears when no members of the VCG are carrying traffic in the transmit (Tx)
direction.
Toxic gas
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 transceiver 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 transceiver is degraded. Therefore, it may be time to change the transceiver before
the transceiver fails.
Transmit degraded
MA268 Rev. F1
139
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 a MEP has received an ETH Segment OAM frame with an unexpected MEG Level. That is to say, a MEG Level that is lower than the configured level for the MEP.
Unexpected MEP
Appears when a MEP has received an ETH Segment OAM frame with the correct MEG Level and the correct MEG ID but an unexpected MEP ID.
Unexpected period
Appears when a MEP has received an ETH Segment OAM frame with the correct MEG Level, correct MEG ID, and correct MEP ID, but an unexpected value of continuity check period. In this NE, the continuity check period is fixed
100 ms.
Unit initialising
Appears when the software used by the module in the slot in question is resetting 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.
Unit missing
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 threshold value defined by the equipment.
140
MA268 Rev. F1
Applies when Input is selected in the Direction: drop-down list, and User defined <1, 2, ..., 8> 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.
User-defined <1, 2, ..., 8>
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to User-defined <1, 2, ..., 8>. Appears when the signal on
the port is high or low depending on the setting of Polarity.
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.
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 upper 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
MA268 Rev. F1
141
Applies when Input is selected in the Direction: drop-down list, and Ventilations 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, 6335, 6340, 6345 and 6350.
Applies when the AUX port in question is configured as an input AUX port
with Alarm Text set to Ventilations system failure. Appears when the signal on
the port is high or low depending on the setting of Polarity.
142
MA268 Rev. F1
11 Probable Causes
11 Probable Causes
This chapter contains the probable causes as defined in the Open Systems Interconnection (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. F1
143
11 Probable Causes
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
144
MA268 Rev. F1
11 Probable Causes
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. F1
145
11 Probable Causes
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
146
MA268 Rev. F1
11 Probable Causes
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. F1
147
11 Probable Causes
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
148
MA268 Rev. F1
11 Probable Causes
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. F1
149
11 Probable Causes
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
150
MA268 Rev. F1
11 Probable Causes
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. F1
151
11 Probable Causes
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
152
MA268 Rev. F1
Index
Index
A
Abbreviations 8
Acknowledge an alarm 55
Acknowledge operation 115
Acknowledged icon 28
Acknowledgement Time Stamp attribute
for alarm objects 88
Acknowledgement User Identifier attribute
for alarm objects 88
Actual module not expected alarm 117
Actual transceiver not expected alarm 117
Add an operation context 48
Additional Information attribute
for alarm objects 83
Additional Text attribute
for alarm objects 83
value for alarm escalation alarms 108
value for alarm log alarms 108
value for bridge LAN interfaces alarms 106
value for bridge leased lines interfaces
alarms 106
value for disk storage alarms 107
value for SNMP entity alarms 106
Additional Text Propagation Mode attribute
for operation contexts 73
Administrative State attribute
for operation contexts 77
Administrative State Change Timestamp attribute
for operation contexts 77
Air compressor failure alarm 117
Air conditioning failure alarm 117
Air dryer failure alarm 117
AIS (alarm indication signal) alarm 117
AIS alarm 117
AIS insertion forced alarm 118
Alarm attributes 25
Alarm Class attribute
for alarm objects 83
Alarm clearance 16
state changes 57
Alarm collection
defining 37
Alarm Descriptions 117
Alarm display
disable 50
enable 50
Alarm entities 23
Alarm escalation
alarm rules for 108
Alarm Exception Procedure attribute
MA268 Rev. F1
Index
B
Backed Up Status attribute
for alarm objects 84
Backup Object attribute
for alarm objects 84
Backward defect indication alarm 120
Battery discharging alarm 120
Battery failure alarm 121
Begin Time parameter
of Archive operation 113
of Purge_alarms operation 111
Bridge LAN interfaces
alarm rules for 106
Bridge leased lines interfaces
alarm rules for 106
C
Cabling error alarm 121
Cancel_archive operation 114
Cancel_purge operation 112
Capacity Alarm Threshold attribute
for operation contexts 69, 74
Category attribute
for alarm rules 94, 100
MA268 Rev. F1
Index
D
database name parameter
of Archive operation 112
Degraded signal alarm 122
Delete
filter 52
Deleting
operation context 42
Delta Time attribute
for alarm rules 100
Description attribute
for alarm rules 95, 100
Deselect
filter 53
Detailed Object attribute 26
Digital diagnostics not supported alarm 122
Directory operation 109
Disable operation 114
using 94
Disable Time attribute
for alarm rules 101
Discriminator Construct attribute
for operation contexts 70, 74
Disk storage
alarm rules for 107
Display of alarms
disable 50
enable 50
Domain attribute
for alarm objects 84
for alarm rules 93
DTMF EOW failure alarm 122
Duration Interval attribute
for alarm rules 98
156
Index
E
EFD <ID> overwritten alarm 122
Enable operation 114
using 94
Enclosure door open alarm 122
End Time attribute
for alarm rules 98
End Time parameter
of Archive operation 113
of Purge_alarms operation 111
Engine failure alarm 122
Entities 23
alarm rule 24
managing 56
operation context 23
Entity attribute
for alarm rules 98
Entity Browser
changing operation contexts 42
Entity View - OPERATION_CONTEXT
open window 39
Equipment cooling failure alarm 123
Equipment fan malfunction alarm 123
Equipment protection configuration error
alarm 123
Error Condition attribute
for alarm rules 101
Error Condition Status attribute
for operation contexts 80
Error Entity attribute
for alarm rules 101
Escalated Alarm attribute
for alarm objects 89
Escalated and Cleared Flag attribute
for alarm objects 84
ESM slot mismatch alarm 123
ESM usage mismatch alarm 123
ETEX critical alarm 123
ETEX critical alarm active alarm 123
ETEX major alarm 123
ETEX major alarm active alarm 123
ETEX minor alarm 124
ETEX minor alarm active alarm 123
ETEX warning alarm 124
ETEX warning alarm active alarm 123
Evaluation Error attribute
for alarm rules 103
Evaluation False attribute
for alarm rules 103
Evaluation True attribute
for alarm rules 103
Event Name attribute
for alarm rules 99
Event Time attribute 26
MA268 Rev. F1
F
Fan speed low alarm 124
Fan speed speed very alarm 124
FEC bit error injection active alarm 125
Filter area
delete a filter pattern 52
deselect a filter 53
use a filter 52
Filter Editor window 31
define a filter pattern 51
setting up a filter 51
Filter pattern
define 51
inspect 52
Filters 31
alarms view filters 31
creating alarms view filter 51
deselect 53
select 52
Fire alarm 125
Fire detector failure alarm 125
Flood alarm 125
Forced switch pending alarm 125
FPGA failure alarm 125
Frequency out of range alarm 126
Fuse failure alarm 126
G
Generator failure alarm 126
GFP EXI mismatch alarm 126
GFP type mismatch alarm 126
GFP UPI mismatch alarm 126
H
Handle Time Stamp attribute
for alarm objects 89
Handled By attribute
MA268 Rev. F1
Index
I
Ice build up alarm 127
Icons
colors indicating alarms 18
showing clearance 28
showing correlated notif info 29
showing state 27
Identifier attribute
for alarm objects 83
Identifiers attributes
for alarm objects 83
for alarm rules 100
for operation contexts 73
Implementation Desc attribute
for operation contexts 70
Indeterminate Problem Occurrences attribute
for alarm objects 90
Indication of alarms 17
Information about alarms 14
Initial Administrative State attribute
for operation contexts 70
Insertion test access connection active alarm 127
Internal HISI degraded alarm 127
Internal HISI failure alarm 127
Internal oscillator failure alarm 128
Internal section degraded alarm 128
Internal section failure alarm 128
Interval parameter
of Archive operation 113
of Purge_alarms operation 111
Intrusion detection alarm 128
157
L
Laps frame mismatch alarm 128
Laser Bias Current Out of Range alarm 128
Laser degraded alarm 129
LFP caused link shut down alarm 129
Lifetime expectancy exceeded alarm 129
Locating and Identifying Alarms in Network
Management 19
Location attribute
for operation contexts 70
Locked alarm 129
Lockout of protection pending alarm 129
LogFullAction attribute
for operation contexts 74
Logging of alarms 16
Logical_Operator_And attribute
for alarm objects 85
Loop back active alarm 129
Loss of alignment alarm 129
Loss of channel counting alarm 129
Loss of clock alarm 129
Loss of continuity 129
Loss of frame alarm 129
Loss of frame delineation alarm 130
Loss of multiframe alarm 130
Loss of optical signal alarm 130
Loss of pointer alarm 130
Loss of reference source alarm 130
Loss of signal alarm 130
Loss of timing alarm 130
Low battery threshold alarm 130
Low cable pressure alarm 130
Low fuel alarm 131
Low humidity alarm 131
Low temperature alarm 131
Low water alarm 131
M
MAIL Account attribute
for operation contexts 70
Main Object attribute 26
Main power input supply failed alarm 132
Major Problem Occurrences attribute
for alarm objects 90
Managed Object attribute
for alarm objects 85
value for alarm escalation alarms 108
value for alarm log alarms 108
value for bridge LAN interfaces alarms 106
value for bridge leased lines interfaces
alarms 106
value for disk storage alarms 107
value for SNMP entity alarms 105
158
Index
N
Name attribute
for alarm rules 100
for operation contexts 70, 73
NE software error: <error-specific text> alarm 132
New Domain Name parameter
of Copy operation 114
New Rule Name parameter
of Copy operation 114
Nick Name attribute
for alarm rules 93
Notification Identifier attribute
for alarm objects 85
O
OC Name attribute
for alarm objects 85
Occurs n time rule 25
Occurs N Time Rule attribute
for alarm rules 93
Occurs rule 25
Occurs Rule attribute
for alarm rules 93
OFA gain control not supported alarm 132
OFA gain lock active alarm 132
OFA gain lock not supported alarm 133
OFA loss of power matching reference alarm 133
OFA manual gain set out of reference alarm 133
MA268 Rev. F1
Index
P
Parent Alarm Object attribute
for alarm objects 85
Path trace mismatch alarm 134
Path unequipped alarm 134
Payload type mismatch alarm 134
Peer dying gasp alarm 134
Perceived Severity attribute 27
for alarm objects 85
value for alarm escalation alarms 108
value for alarm log alarms 108
value for bridge LAN interfaces alarms 106
value for bridge leased lines interfaces
alarms 106
value for disk storage alarms 107
value for SNMP entity alarms 105
Phone Number attribute
for operation contexts 71
Polling Interval attribute
for alarm rules 98
Power down alarm 134
Power failure alarm 134, 135
Power load too high alarm 135
Power problem alarm 135
Power too high alarm 135
Power too low alarm 135
Presentation of alarms 14
Principles of alarm handling 13
Probable Cause attribute
for alarm objects 27, 86
for alarm rules 95, 100
value for alarm escalation alarms 108
value for alarm log alarms 108
value for bridge LAN interfaces alarms 106
value for bridge leased lines interfaces
alarms 106
value for disk storage alarms 107
159
R
RDI (remote defect indicator) alarm 136
RDI alarm 136
Real Time View
deselect filter use 53
inspect a filter pattern 52
select filter use 52
Real Time View window
acknowledge an alarm 55
creating operator note 56
160
Index
delete filters 52
display all attributes for alarm 55
managing entity causing alarm 56
opening 46
terminating alarm 57
Receiver overload alarm 136
Rectifier failure alarm 136
Rectifier high voltage alarm 137
Rectifier low voltage alarm 137
Reduction Mode attribute
for operation contexts 71, 75
Reduction Scope attribute
for operation contexts 75
Reference Operation_Context Name attribute
for operation contexts 71
References 8
Register operation 109
Registration attributes
for alarm rules 93
for operation contexts 67
Relational Operator attribute
for alarm rules 98
Release Time Stamp attribute
for alarm objects 89
Release User Identifier attribute
for alarm objects 89
Remarks attribute
for operation contexts 71
Reporting of alarms 13
Repository Location attribute
for operation contexts 71, 76
Responsibility for alarm handling 16
Responsible Operators attribute
for operation contexts 76
Responsible Person attribute
for operation contexts 71
Result of Last Evaluation attribute
for alarm rules 102
Resume operation 110
using 70, 77
Resumed By User attribute
for operation contexts 81
Routing attributes
for operation contexts 82
RTM failure alarm 137
Rule Expression attribute
for alarm rules 97
Rule Name attribute
for alarm objects 86
S
SA Total attribute
for alarm objects 91
MA268 Rev. F1
Index
T
T4 output squelched alarm 138
Target Entities attribute
for alarm objects 87
TCXO (oscillator) failure alarm 138
Tellabs 6300 manager
alarm rules for monitoring 105
TeMIP Client window 45
Temperature too high alarm 139
Terminate operation 115
Terminated icon 28
Terminating an alarm 57
161
Index
W
Warning Problem Occurrences attribute
for alarm objects 91
U
UB power too high alarm 140
UB power too low alarm 140
UB1 power missing alarm 140
UB2 power missing alarm 140
Unexpected MEG level alarm 140
Unexpected MEP level alarm 140
Unexpected period alarm 140
Unit initialising alarm 140
Unit main type mismatch alarm 140
Unit missing alarm 140
Unit sub type mismatch alarm 140
Unit temperature too high alarm 140
Unit temperature too low alarm 141
Unknown LMIP probable cause <ID> alarm 141
User Identifier attribute
for alarm objects 87
User Text attribute
for alarm objects 87
User-defined 1 alarm 141
V
Vcc (+5V) voltage too high alarm 141
Vcc (+5V) voltage too low alarm 141
VCO (oscillator) failure alarm 141
VCXO (oscillator) failure alarm 141
Vee (-5V) voltage too high alarm 141
Vee (-5V) voltage too low alarm 141
162
MA268 Rev. F1