You are on page 1of 60

Title page

1360 COM
SNMP Alarm Forwarding Administrator Guide
255-400-466
Issue 4 | March 2015

Legal notice
Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2015 Alcatel-Lucent. All rights reserved.

Contents
About this document
Purpose

............................................................................................................................................................................................. ix
ix

Changes to this document .......................................................................................................................................................... ix
ix
Reason for reissue

........................................................................................................................................................................ ix
ix

Content ............................................................................................................................................................................................... xx
Intended audience

......................................................................................................................................................................... xi
xi

Terminological conventions ...................................................................................................................................................... xi
xi
Conventions used .......................................................................................................................................................................... xi
xi
Related information
How to comment
1

.................................................................................................................................................................... xii
xii

......................................................................................................................................................................... xii
xii

About alarm forwarding
Overview ...................................................................................................................................................................................... 1-1
1-1
Forwarding traps

....................................................................................................................................................................... 1-1
1-1

Forwarding changed alarm severity ................................................................................................................................... 1-3
1-3
Alarm resynchronization ........................................................................................................................................................ 1-6
1-6
Decreasing the probability of trap overflows
2

Alarm resynchronization
Resynching Alarms

3

................................................................................................................. 1-6
1-6

.................................................................................................................................................................. 2-1
2-1

SNMPNITF configuration
SNMP North Bound Interface .............................................................................................................................................. 3-1
3-1

4

1360 COM MIB support for alarm forwarding
Supported MIBs

........................................................................................................................................................................ 4-1
4-1

....................................................................................................................................................................................................................................
1360 COM
iii
255-400-466
Issue 4 March 2015

..733 Detailed format of SNMP NBI traps compared to X...............................................................................................................................................................733 ............................ 5-1 5-1 Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ........ B-1 B-1 Glossary Index ...........................................................Contents ......................................................................................................................................................................................................................................................... A-1 A-1 B SNMP Traps and X........................................................................... 1360 COM iv 255-400-466 Issue 4 March 2015 .................................................................................................................................... 5 Accessing the Network Element list Access the Network Element list A ...................................................................

............................List of tables 1 Reason for revision ........................ ix ix 2 Reason for revision .................................................................................................................................................................................................... B-1 B-1 ............................................................ x x 4 Reason for revision ............................................................................... 1360 COM v 255-400-466 Issue 4 March 2015 ........................ x x B-1 Alarm mapping ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. x x 3 Reason for revision ..............................................................

............................................. 1360 COM vi 255-400-466 Issue 4 March 2015 .....................................................................................................................List of tables ........................................................................................................................................................................................................................................................................................ ...............

.....................................................................................................List of figures 1-1 Change alarm severity ....................................................................................................................................................................................................................................................... 1-4 1-4 1-2 Changed alarm x2 .................................................................. 1-6 1-6 ................................... 1-5 1-5 1-3 OSS filter example ....................................................................................................................... 1360 COM vii 255-400-466 Issue 4 March 2015 ....................................................................................................

............................................................................................................................... .......................................................................................................................................................................................... 1360 COM viii 255-400-466 Issue 4 March 2015 ....................................................................................List of figures ............................................................

..... the following changes have been made to this document: • • This document has been retitled for easy searchability renumbering this document preserves all past releases and issues that are supported on 1360 COM • This document is cumulative and previous 1360 COM 1........ Information presented in this document applies to the 1360 COM releases... ....................................................... The layout of GUI screens provided in this document may vary slightly from your actual GUI...... 1360 COM ix 255-400-466 Issue 4 March 2015 .................. Changes to this document Starting with 1360 COM release 2...................... This document will be reissued with a new issue number when changes are made.......About this document About this document Purpose This operator guide describes how to monitor alarms of Network Elements (NEs) from the Alcatel-Lucent 1360 Centralized Operations Manager (COM) in a normal operational context............................0..... Reason for reissue Issue 4 Table 1 Reason for revision Chapter Description 1 A new section Decreasing the probability of trap overflows is added......x versions are included........... This document may be reissued concurrently with a software release or between releases for updates or to fix bugs................................................................

.....1 Alarm forwarding preserves severity for OMC-18895.................. “SNMPNITF configuration” About SNMPNITF Configuration Chapter 4................................ Appendix A Add new entries for AlarmEntry and update Changed Alarm Trap for OMC-19556............................................................................................. Issue 2 Table 3 Reason for revision Chapter Description 1 Starting with COM 3............... “About alarm forwarding” About Alarm Forwarding Chapter 2...............................About this document . Content Chapter Description Chapter 1............................ Issue 1 Table 4 Reason for revision Chapter Description All The supported release number style has been changed............................ “1360 COM MIB support for alarm forwarding” About the MIB supported by 1360 COM for Alarm Forwarding ............... Issue 3 Table 2 Reason for revision Chapter Description Appendix A Add new MIB including Reason and alarm_list_alignment_ requirement for OMC-19556................ Trap types formerly not supported are now supported for OMC-19556.......................................................................................... 1360 COM x 255-400-466 Issue 4 March 2015 .................................. “Alarm resynchronization” About Alarm Resynchronization Chapter 3......................................... The document supports all previous releases and will only be reissued for bug fixes and new content.....................

................................................................................... Chapter Description Chapter 5.............................................................733 Alarms and SNMP NBI Traps “Glossary” Lists the form of all the abbreviations used in this guide Index Lists the main topics and their location in this guide Intended audience This guide is intended for operators responsible for monitoring alarms of NEs from an Alcatel-Lucent 1360 COM..... This document uses abbreviations developed from the English extended form when available...................... Certain abbreviations may be French-based when no English extended form exists........ALARMFORWARDING-MIB Appendix B......... keyboard keys.. • UNIX is a registered trademark of The Open Group.....733” Conversion of SNMP SBI Traps to X.......... Terminological conventions The following terminological conventions are used in this document: • • The terminology used is that specified by the International Telecommunication Union Telecommunication standardization sector (ITU-T) and European Telecommunications Standards Institute (ETSI) standards............................................ Inc..................... “Accessing the Network Element list” How to obtain the list of the Network elements Appendix A........................ 1360 COM xi 255-400-466 Issue 4 March 2015 .......................... menus................. “Priority MIB” ALCATEL-OMCCN.. Java is a trademark of Sun Microsystems............................................. tab names text in [bold italics in square brackets]: window titles and dialog box names • • ......................... Conventions used This guide uses the following typographical conventions: • • text in italics: document titles text in bold: important information • text in courier: command typed by an operator and messages displayed by the system text in bold italics: dialog box buttons and fields.....About this document ......................... “SNMP Traps and X......................... Alcatel-Lucent acknowledges the following trademarks for company names or products mentioned within Alcatel-Lucent documents: • • CORBA is a registered trademark of Object Management group....... menu options....

................................................. 255-400-454.. .............................About this document .............com/comments/) or email your comments to the Comments Hotline (comments@alcatel-lucent......................................................................................................................... alcatel-lucent................................. 1360 COM xii 255-400-466 Issue 4 March 2015 ........ go to the Online Comment Form (https://infoproducts................................... How to comment To comment on this document..............................................com).................................................... • • The ♢ symbol indicates an example Information links indicates relevant information links related to the preceding section or sub-section Related information Documents related to this guide include: • Alcatel-Lucent 1360 COM Platform Management Operator Guide............................................................................

..........................................1 About alarm forwarding 1 Overview Purpose The Alcatel-Lucent 1360 COM provides integrated management for the core network NEs.................... the 1360 COM is responsible for centralized alarm reception for a set of NEs in the network and for centralized alarm forwarding based on SNMP to a NMS........................................................ all alarms are forwarded as traps by the 1360 COM.. NMS is the Network management System that is client of the SNMP interface provided by the 1360 COM.... Contents Forwarding traps 1-1 Forwarding changed alarm severity 1-3 Alarm resynchronization 1-6 Decreasing the probability of trap overflows 1-6 Forwarding traps Purpose This topic discusses sending traps on the 1360 COM........................... In particular. Overview The 1360 COM forwards alarms managed by the 1360 COM as SNMP traps: • • For SNMP NEs........................ ............... 1360 COM 1-1 255-400-466 Issue 4 March 2015 ................. For other NEs sending alarms natively... only traps received from NEs and mapped into alarms (those displayed in 1360 COM fault management GUI) are forwarded as traps by the 1360 COM..........................

..........................733”......... .. 1360 COM 1-2 255-400-466 Issue 4 March 2015 ..................Cleared Alarm Trap x6 ................ “Priority MIB”............................Acknowledge State Changed Trap x4 ......About alarm forwarding Forwarding traps ......................Comment Added Trap (not supported) • • x5 ..... The traps and the fields of the traps are described in the MIB file....... If 3GPP north interface is not installed as a package of 1360 COM................ These trap types are: • • • • x1 .. The mapping between the X.. “SNMP Traps and X...Alarm List Rebuilt Trap (available only when optional 3GPP component is running) • x7 ................................. After the rebuild.............................. 1360 COM trap content is similar to the 3GPP definition of an alarm.........Changed Alarm Trap x3 ............................................................................... Comment Added Trap is not supported.....Potential Faulty Alarm List Trap (available only when optional 3GPP component is running) The supported SNMP V2c/V3 traps are: • • • • • • NotifyNewAlarm: triggered when a new alarm occurs in the NE and has been detected by 1360 COM NotifyAckStateChanged: triggered when the Acknowledge state of an alarm has been changed (the alarm has been acknowledged by a user) NotifyClearedAlarm: triggered when an alarm is cleared NotifyAlarmListRebuilt: triggered when the alarm list in 1360 COM has been rebuilt................... This trap is triggered after the trap NotifyPotentialFaultyAlarmList NotifyPotentialFaultyAlarmList: triggered when the 1360 COM cannot determine the integrity of its alarm list and is to rebuild its alarm list................................... Please refer to the Appendix A...733 attributes of an alarm (as seen in the 1360 COM fault management GUI) and the trap fields is described in the Appendix B................ NotifyAlarmListRebuilt is triggered NotifyHeartBeat: triggered periodically by 1360 COM to notify NMS of the sequence number of the last trap sent.............New Alarm Trap x2 ..................... AlarmListRebuild(x6) and PotentialFaultyAlarmList(x7) are generated because these two alarms are produced by the 3GPP feature......................................................

........................... Select the severity to change the alarm to from the pull down menu...................................................................... Useful information includes former severity level and the reason for change................................................ or with that severity change removed.... select Tools> Alarm Analysis> Exception.......... checkbox and enter some text to identify the changed alarm for future reference.. Forwarding changed alarm severity Overview Alarm severity change within the 1360 COM's Fault Management module (CFMA) has been supported.................................................................................... .......... Click the Change severity to checkbox............. 1360 COM 1-3 255-400-466 Issue 4 March 2015 ................................ The Analysis Filter — Exceptions window displays........... 3 Click the Apply alarm exceptions checkbox................................ 1 Open the Fault Management module........ but the change was internal to the COM only and did not propagate if the alarm was forwarded............................ ........................................................ Change severity and forward ........................ Starting in COM 3......................................About alarm forwarding Forwarding changed alarm severity ......................................... ................................ ............................................................................................................1......................................................................................................................................................................................... 2 From the menu bar................. propagation of alarms with changed severity is configurable........... That allows the option of having alarms whose severity has been changed within COM propagate northbound with that severity change intact............................................................................................... ........................................................... Click the Update additional text to be ................

..........................................................................................................................................About alarm forwarding Forwarding changed alarm severity ............................................... as shown in the figure...................................................................................................................................................................................................................................................................................................................................................................................................... 1360 COM 1-4 255-400-466 Issue 4 March 2015 ..... Figure 1-1 Change alarm severity ......................... 4 The changed alarm has a type name including x2................................................ .

About alarm forwarding

Forwarding changed alarm severity

....................................................................................................................................................................................................................................

Figure 1-2 Changed alarm x2

...................................................................................................................................................................................................

5

Filters can be applied on northbound OSS to not receive notifyChangedAlarm traps.

....................................................................................................................................................................................................................................
1360 COM
1-5
255-400-466
Issue 4 March 2015

About alarm forwarding

Forwarding changed alarm severity

....................................................................................................................................................................................................................................

Figure 1-3 OSS filter example

E...................................................................................................................................................................................................
N D O F S T E P S

Alarm resynchronization
Overview

NMS can obtain all active alarms of NEs by sending out SNMP GET/GETNEXT request
to 1360 COM SNMPNITF.
SNMP versions supported by Alarm Forwarding are SNMP V2c and SNMP V3.

Decreasing the probability of trap overflows
Overview

Note: This feature is applicable only for SNMP-based NEs.
....................................................................................................................................................................................................................................
1360 COM
1-6
255-400-466
Issue 4 March 2015

About alarm forwarding

Decreasing the probability of trap overflows

....................................................................................................................................................................................................................................

This feature helps in decreasing the impact on COM capacity when there is a trap flood
on a NE. When COM detects a trap flood from a NE, and when the alarm count for the
NE crosses the trap flood threshold configured on COM (default is 3000), COM raises a
critical alarm “too many alarms” for the NE. Also, COM stops handing the new trap
mapping and alarm resynchronization for the NE till the NE is recovered from trap flood.
For NEs like LCP, with manager and discovered NEs, the new alarm is only raised for the
manager. But COM stops receiving new traps for all NEs and stops resynchronization for
all NEs.
Configuration

To enable this feature, contact your Services Business Group representative.

....................................................................................................................................................................................................................................
1360 COM
1-7
255-400-466
Issue 4 March 2015

...........................................................................................................................................................................................................................................................................................About alarm forwarding Decreasing the probability of trap overflows ..................................... 1360 COM 1-8 255-400-466 Issue 4 March 2015 ............................................................................................................................ .............

............................................................... 1360 COM 2-1 255-400-466 Issue 4 March 2015 ........... If one of the row statuses is 0 (typically the last row).... the alarm table is retrieved successfully.............................. If all row statuses are 1............................................................................... The result is incomplete and uncertain..........2 Alarm resynchronization 2 Resynching Alarms Overview The Alarm Resynchronization retrieves active alarms from the NEs managed by 1360 COM and sends out these alarms as SNMP response to SNMP GET/GETNEXT request......... something failed during the operation.............. ..... Note: Row status is used to detect whether the operation of get alarm table is completed and successful..........

....................................................................................................................................................................................... ....................................................................................................................................................................................................................................Alarm resynchronization Resynching Alarms ............................................ 1360 COM 2-2 255-400-466 Issue 4 March 2015 ..

.... the following parameters (non exhaustive list) can be configured: • • • Agent port number (default value: 16100) In the case of SNMP V2c use: Read Community Name (default value: omccn) SNMP Version (default value : SNMP2c) • • OSS configuration Filtering In the case of SNMP V3 use: • • Authentication Protocol Engine ID • • • Privacy Encryption Security Level User Name For more information about this configuration..... For example.... .......... select the COM Configuration tab. In the [Platform Management] window........................................ chapter 'SNMP North Bound Interface'.................................. refer to the Alcatel-Lucent 1360 COM..................3 SNMPNITF configuration 3 SNMP North Bound Interface Overview The SNMPNITF configuration is performed through the Platform Management application.............................................................. Platform Management Operator Guide. 255-400-454..... 1360 COM 3-1 255-400-466 Issue 4 March 2015 .. The SNMP North Bound Interface parameters are available under the COM Common configuration folder -> SNMP North Bound Interface sub-folder....................................................

.......................................................................................................................... ........................................................... 1360 COM 3-2 255-400-466 Issue 4 March 2015 ...............................................................................................................................................SNMPNITF configuration SNMP North Bound Interface .....................................................................................................................................

....... See the Appendix A.. It is accessible by sftp from the guest account "expftp" in /pub/omc/MIB (for example for further use by a MIB browser)............................ “Priority MIB”................................................. Proprietary MIB: ALCATEL-OMCCN-ALARMFORWARDING-MIB.................................. ................................................................................. 1360 COM 4-1 255-400-466 Issue 4 March 2015 .......................4 4360 COM MIB support for 1 alarm forwarding Supported MIBs Overview The MIBs supported by the 1360 COM are: • • Standard MIB: MIB II / RFC 1213 except for the EGP group and the if MIB group.........

........................................................................................................................................... 1360 COM 4-2 255-400-466 Issue 4 March 2015 ......................................................................................................................................................................................................................................1360 COM MIB support for alarm forwarding Supported MIBs .............................................. ..........................................

... Supervision State............ NE Release..................... 255-400-457.................... each line contains attributes such as: Friendly Name........ the file /nedata/NetworkTopology contains the list of the NEs supervised by the 1360 COM.............. Geographical Site.......... Timezone.......... SNMP port.............. .. NE Type.... IP Address................................................ It contains a line per NE. Virtual group. chapter 'Accessing the NetworkTopology file by FTP/SFTP'....................... It is a csv file that provides information about the list of NEs in the 1360 COM.. Secondary IP Address.. and Communication State The process to get this file is described in the Alcatel-Lucent 1360 COM Network Management Guide... Additional addresses.. It is updated every 2 minutes....... Hostname.. Applications................5 5 ccessing the Network A Element list Access the Network Element list Overview On the 1360 COM... Master friendly name............. 1360 COM 5-1 255-400-466 Issue 4 March 2015 .........

.................................................................................................................................................................................................................................................................................................................... 1360 COM 5-2 255-400-466 Issue 4 March 2015 ....................................................................................................Accessing the Network Element list Access the Network Element list ..................... ............................

.........2011/10/13 P....... org OBJECT IDENTIFIER ::= { iso 3 } dod OBJECT IDENTIFIER ::= { org 6 } internet OBJECT IDENTIFIER ::= { dod 1 } private OBJECT IDENTIFIER ::= { internet 4 } enterprises OBJECT IDENTIFIER ::= { private 1 } alcatel OBJECT IDENTIFIER ::= { enterprises 637 } omccn OBJECT IDENTIFIER ::= { alcatel 1 } alarmForwarding OBJECT IDENTIFIER ::= { omccn 1 } alarmTable OBJECT-TYPE SYNTAX SEQUENCE OF AlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The active alarm table contains all active alarms in COM.2009/02/04 Zhang Tingyu CR OCNA01CAG229337 -........2010/10/25 P.............................2013/18/13 V....2010/08/31 Dev Team FR OCNA01FAG256290 : Field additional_ information of the COM NBI MIB (SNMP forwarding) tagged as DisplayString even can contain binary information -..... -.....2007/07/13 Song Song Change item "event_name" to "event_type" for OCNA01FAG195094 -....2006/12/05 Gu Xiangguo Add alarmTable/alarmEntry/AlarmEntry definition -...................................... David OMC-12080 Alarm severity change should be propagated on SNMP NBI IMPORTS enterprises FROM RFC1155-SMI DisplayString FROM RFC1213-MIB OBJECT-TYPE FROM RFC-1212 NOTIFICATION-TYPE FROM SNMPv2-SMI.. 1360 COM A-1 255-400-466 Issue 4 March 2015 ...........................2009/04/09 Zhang Tingyu CR OCNA01CAG229337 -.................................................... -....................Appendix A: Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB Overview ALCATEL-OMCCN-ALARMFORWARDING-MIB DEFINITIONS ::= BEGIN -.......2006/12/05 Gu Xiangguo Add trap_number -........ Giaume OMC-8533 renaming..... Giaume FR OCNA01FAG231829 : fix AlarmEntry.........." ...

........... clear_user_id DisplayString........ managed_object_instance DisplayString....................... system_dn DisplayString..............1............4................ ack_user_id DisplayString........... back_up_object DisplayString.. threshold_info DisplayString. specific_problem DisplayString. row_status INTEGER } trap_version OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "It carries the format version of the trap. 1360 COM A-2 255-400-466 Issue 4 March 2015 ...................... reason DisplayString........... additional_information OCTET STRING...................1......1..........637......... notification_id INTEGER....637.6...............4 ::= { alarmForwarding 4 } alarmTraps OBJECT IDENTIFIER ::= { alarmTable 0 } alarmEntry OBJECT-TYPE SYNTAX AlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the alarm table defines the alarm structure...........3............. perceived_severity INTEGER...... additional_text DisplayString............1.... ack_state INTEGER... backed_up_status DisplayString...................6........................1..........3. alarm_id DisplayString..... probable_cause INTEGER..........................1..........4......" INDEX { sequence_number } -....Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ..4.1................1 ::= { alarmTable 1} AlarmEntry ::= SEQUENCE { sequence_number INTEGER.1..... clear_system_id DisplayString...1........................... trap_type DisplayString...... proposed_repair_actions DisplayString............... trap_version DisplayString..........." ............ ack_system_id DisplayString.. event_time DisplayString................... alarm_list_alignment_requirement INTEGER... trend_indication INTEGER........ event_type DisplayString. -...1....................

.......1........3...........1.. 1360 COM A-3 255-400-466 Issue 4 March 2015 ...1....6.INTEGRITY_VIOLATION x7 ............3..........1 ::= { alarmEntry 1 } trap_type OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies one of the following trap types: x1 ...2 ::= { alarmEntry 2 } event_type OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies one of the following alarm types: x1 ........1.........PHYSICAL_VIOLATION x9 .......1..................COMMUNICATIONS_ALARM x2 .......1..1.....3......TIME_DOMAIN_VIOLATION " -....4...........Comment Added Trap(not supported) x5 .3 ::= { alarmEntry 3 } managed_object_instance OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the source of this alarm notification.....4 ::= { alarmEntry 4 } notification_id OBJECT-TYPE .........637..6.......................6....637............1..1......1....1..........." -....Ackowledge State Changed Trap x4 ........4.......3.1.....4.....1..........OPERATIONAL_VIOLATION x8 ......SECURITY_SERVICE_OR_MECHANISM_VIOLATION x10 ......................4.4.6.........Changed Alarm Trap x3 ..............EQUIPMENT_ALARM x6 ....Alarm List Rebuilt Trap(available only when optional 3GPP component is running) x7 ................1....................1.......... -..4..Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ..........1.637.1...637......ENVIRONMENTAL_ALARM x4 ..........4.....Cleared Alarm Trap x6 ...1.................PROCESSING_ERROR_ALARM x3 ....Potential Faulty Alarm List Trap(available only when optional 3GPP component is running) " -...............1.........1.....................4.1.........................New Alarm Trap x2 .1....1...................QUALITY_OF_SERVICE_ALARM x5 ..1..

........ 2 ...4.... 5 ..........1.... then the event time is the NE time........1...6..1.....4..6. 1360 COM A-4 255-400-466 Issue 4 March 2015 ..1..1........................1..637...INDETERMINATE......................1..........1............ALARM_INDICATION_SIGNAL..3.....DEGRADED_SIGNAL.. SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the notification that carries the trap.. It also consists of a time displacement factor in the form of minutes of displacement from the Greenwich Meridian............. " -.........5 ::= { alarmEntry 5 } event_time OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The time refers to time in Greenwich Time Zone... then the event time is the OMC-CN time..FRAMING_ERROR." -......... // Values below correspond to M.................... 0 .4................ 4 .............1.....................1...........FAR_END_RECEIVER_FAILURE......3.......6..........................1....................Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ..3...........3100..4. It carries the distinguished name of the IRPAgent.............. If the alarm is generated by OMC-CN.... // Probable causes originating from M..1...1.....1.1.....637..........637...........4.......... 3 .................3100 values.......1.................................CALL_SETUP_FAILURE........ ......7 ::= { alarmEntry 7 } probable_cause OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the probable cause of a reported alarm...... 1 ...1....1...." -.4............................6 ::= { alarmEntry 6 } system_dn OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the IRPAgent (an entity in OMCCN related to the alarms).... If the alarm is forwarded by OMC-CN from a NE.

.. 102 ......LOSS_OF_POINTER........MODULATION_FAILURE....... 62 ......................PROTECTION_PATH_FAILURE.REPLACEABLE_UNIT_MISSING...........SIGNAL_LABEL_MISMATCH.............. 19 ............AIR_COMPRESSOR_FAILURE..DEMODULATION_FAILURE.EQUIPMENT_IDENTIFIER_DUPLICATION..REPLACEABLE_UNIT_PROBLEM..3100 potential future extensions 101 ........ // Values 83-100 are reserved for M............REMOTE_ALARM_INTERFACE.......................... 67 .....PAYLOAD_TYPE_MISMATCH....NE_IDENTIFIER_DUPLICATION.....MULTIPLEXER_PROBLEM.. 64 ....PROCESSOR_PROBLEM....... 57 ... 61 .......3100 potential future extensions 51 .......PATH_TRACE_MISMATCH... 63 .. 69 ....... 58 ............ 68 .UNAVAILABLE... // Values 10 correspond to a duplicated probable cause 11 ..............LOSS_OF_SIGNAL......... 106 ...PROTECTION_MECHANISM_FAILURE...EXTERNAL_IF_DEVICE_PROBLEM. 103 ... 12 .....TRANSMITTER_FAILURE..AIR_DRYER_FAILURE........ 8 ......... 13 .......REAL_TIME_CLOCK_FAILURE.. // Values 71-80 correspond to duplicated probable causes 81 .. 15 ..TIMING_PROBLEM...POWER_PROBLEM.. 65 .............AIR_CONDITIONING_FAILURE............. 56 .. // Values 21-26 correspond to duplicated probable causes // Values 27-50 are reserved for M.. 60 . 20 ......... 18 . 55 .. 7 .BATTERY_DISCHARGING....REPLACEABLE_UNIT_TYPE_MISMATCH............... 1360 COM A-5 255-400-466 Issue 4 March 2015 .. 6 .. 82 ...EXCESSIVE_BIT_ERROR_RATE.........................TERMINAL_PROBLEM..TRUNK_CARD_PROBLEM...................COMMUNICATIONS_RECEIVE_FAILURE....LOSS_OF_FRAME.. 66 ...............DATA_SET_PROBLEM....... 52 . .....SYNCHRONIZATION_SOURCE_MISMATCH......... 14 .BATTERY_FAILURE...........RECEIVER_FAILURE. 104 ...LOSS_OF_MULTI_FRAME.... 59 .........BACK_PLANE_FAILURE..COMMERCIAL_POWER_FAILURE... 70 ...COMMUNICATIONS_TRANSMIT_FAILURE.... 105 ....... 9 ....... 16 .. 53 ............. 54 ...Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ......... 17 ....LINE_CARD_PROBLEM............PROTECTING_RESOURCE_FAILURE...

. .... ........HIGH_HUMIDITY........ 156 ... 118 ........FIRE.............. // Values 137-150 are reserved for potential M. 158 .........LOW_HUMIDITY...LOW_TEMPERATURE.... 133 .. 117 ......... 120 ............. 124 .LOW_FUEL. 123 .... 154 ......... 121 .OUT_OF_CPU_CYCLES. 119 ... ........LOW_WATER. 126 ...... 122 .......Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB .......RECTIFIER_FAILURE.......... 128 ...........VENTILATION_SYSTEM_FAILURE....INTRUSION_DETECTION....LOSS_OF_REAL_TIME...... // Values 204-207 correspond to duplicated probable causes // Values 208-300 are reserved for potential M.... 107 108 109 110 111 112 113 114 115 ..................COOLING_FAN_FAILURE. .. 155 ....... 130 . 131 ...........ENCLOSURE_DOOR_OPEN........... 129 ...............RECTIFIER_LOW_F_VOLTAGE.......................................... ..SOFTWARE_ENVIRONMENT_PROBLEM...... 1360 COM A-6 255-400-466 Issue 4 March 2015 ...ICE_BUILD_UP... 125 ........ .........3100 future extensions // Values 201-202 correspond to duplicated probable causes 203 .........3100 future extensions 151 .... // Values 134-135 correspond to duplicated probable causes 136 ..RECTIFIER_HIGH_VOLTAGE.SOFTWARE_DOWNLOAD_FAILURE.....TOXIC_GAS...SMOKE.........FIRE_DETECTOR_FAILURE...............HIGH_WIND......... // Values 159-167 correspond to duplicated probable causes // Values 168-200 are reserved for potential M....... 152 ....... 153 ..............STORAGE_CAPACITY_PROBLEM......FLOOD............EXPLOSIVE_GAS.HIGH_TEMPERATURE....CORRUPT_DATA.....LOW_CABLE_PRESSURE..LOW_BATTERY_THRESHOLD.......MEMORY_MISMATCH.REINITIALIZED.... .. ..EXTERNAL_POINT_FAILURE...........721.. 127 .............721 values with an offset of 300... 116 .....ENGINE_FAILURE..FUSE_FAILURE...EXCESSIVE_ERROR_RATE. //Values below correspond to X..................... 132 .... 157 .... ...PUMP_FAILURE.......3100 future extensions //Probable causes originating from X............GENERATOR_FAILURE..

..... 323 ............. // Value 312 corresponds to a duplicated probable cause 313 .....INPUT_OUTPUT_DEVICE_ERROR......... 340 ... 333 ....... // Values 328-329 correspond to duplicated probable causes 330 .........................CPU_CYCLES_LIMIT_EXCEEDED......EQUIPMENT_MALFUNCTION......PERFORMANCE_DEGRADED.......QUEUE_SIZE_EXCEEDED..REMOTE_NODE_TRANSMISSION_ERROR... // Value 331 corresponds to a duplicated probable cause 332 . // Values 318-320 correspond to duplicated probable causes 321 ... // Value 349 corresponds to a duplicated probable cause 350 ..SOFTWARE_PROGRAM_ERROR.......EXCESSIVE_VIBRATION.....APPLICATION_SUBSYSTEM_FAILURE.............. 316 .......... // Value 341 corresponds to a duplicated probable cause 342 ... 325 ...... 345 ......Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ... 351 .................COMMUNICATIONS_PROTOCOL_ERROR..... 347 .. 302 .. 308 .................PRESSURE_UNACCEPTABLE. 324 ...LOCAL_NODE_TRANSMISSION_ERROR............. // Value 304 corresponds to a duplicated probable cause 305 ..RESPONSE_TIME_EXCESSIVE........BANDWIDTH_REDUCED..LEAK_DETECTED.....RESOURCE_AT_OR_NEARING_CAPACITY...........THRESHOLD_CROSSED.. 301 .... 326 ..LAN_ERROR.. // Value 314 corresponds to a duplicated probable cause 315 . 303 ... 343 ....SOFTWARE_ERROR........ 317 ....................FILE_ERROR........INPUT_DEVICE_ERROR..... 327 ..............OUT_OF_MEMORY........ 306 ................TEMPERATURE_UNACCEPTABLE.......HEATING_OR_VENTILATION_OR_COOLING_SYSTEM_PROBLEM........ 322 ......ADAPTER_ERROR..................... // Value 352 corresponds to a duplicated probable cause 353 ...... 307 .......TOXIC_LEAK_DETECTED..........COMMUNICATIONS_SUBSYSTEM_FAILURE...CONGESTION.HUMIDITY_UNACCEPTABLE.RETRANSMISSION_RATE_EXCESSIVE.... .....MATERIAL_SUPPLY_EXHAUSTED............... 1360 COM A-7 255-400-466 Issue 4 March 2015 ............................ 344 ........RECEIVE_FAILURE.. 346 . // Value 309 corresponds to a duplicated probable cause 310 .CONFIGURATION_OR_CUSTOMIZATION_ERROR........DTE_DCE_INTERFACE_ERROR...DATA_SET_OR_MODEM_ERROR... 311 .... // Value 335 corresponds to a duplicated probable cause 336 ......... 348 .................... // Values 337-338 correspond to duplicated probable causes 339 ...OUTPUT_DEVICE_ERROR.SOFTWARE_PROGRAM_ABNORMALLY_TERMINATED..... 334 .....

.........TRANSCEIVER_PROBLEM.............TRANSMITTER_OFF_FREQUENCY.. // Value 524 corresponds to a duplicated probable cause 525 .......... 514 ..VERSION_MISMATCH... 503 .. 513 .. 520 . 526 .A_BIS_TO_BTS_INTERFACE_FAILURE........LOST_REDUNDANCY..TRANSMITTER_LOW_VOLTAGE_OR_CURRENT.....TRANSMIT_FAILURE..................DISK_PROBLEM.. 522 .......... 533 . 523 ......RECEIVER_ANTENNA_FAULT...EXCESSIVE_TRANSMITTER_TEMPERATURE.... 541 ... 527 ... 529 .. 518 ....UNDERLYING_RESOURCE_UNAVAILABLE.TRANSCODER_PROBLEM..... 540 ...... 515 . 536 .. 501 ........... 539 ...... 531 ...... 537 . 517 ..................DATABASE_INCONSISTENCY. // Values 358-500 are reserved for potential X.CLOCK_SYNCHRONIZATION_PROBLEM.... 512 ........ 508 ........LOSS_OF_SYNCHRONIZATION.......MESSAGE_NOT_EXPECTED....MAINS_BREAKDOWN_WITH_BATTERY_BACKUP... .BATTERY_CHARGING_FAULT..... 519 ........ 532 ..FREQUENCY_HOPPING_FAILURE...... 502 .RECEIVER_MULTICOUPLER_FAILURE. // Value 355 corresponds to a duplicated probable cause 356 ...... 1360 COM A-8 255-400-466 Issue 4 March 2015 ..A_BIS_TO_TRX_INTERFACE_FAILURE....ANTENNA_PROBLEM.Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ... 516 ........ 504 ...... 528 .............TIMESLOT_HARDWARE_FAILURE.............INVALID_POINTER.FILE_SYSTEM_CALL_UNSUCCESSFUL........REDUCED_TRANSMITTER_OUTPUT_POWER............ // Value 509 corresponds to a duplicated probable cause 510 .........TRANSCODER_OR_RATE_ADAPTER_PROBLEM..POWER_SUPPLY_FAILURE.........MAINS_BREAKDOWN_WITHOUT_BATTERY_BACKUP.................LINK_FAILURE............FREQUENCY_HOPPING_DEGRADED.....TRANSMITTER_ANTENNA_NOT_ADJUSTED......SIGNAL_QUALITY_EVALUATION_FAULT........ 521 . 542 ........ 506 ............. 507 ......................TRANSMITTER_ANTENNA_FAILURE..............INVALID_PARAMETER. 530 ..INPUT_PARAMETER_OUT_OF_RANGE. 357 ..... // Value 534 corresponds to a duplicated probable cause 535 .COMBINER_PROBLEM.......EXCESSIVE_RECEIVER_TEMPERATURE.BATTERY_BREAKDOWN.......721 future extensions //Probable causes for 2G & 3G wireless systems.......... 538 ....EXCESSIVE_TRANSMITTER_OUTPUT_POWER......FREQUENCY_REDEFINITION_FAILED........ 511 ....................LINE_INTERFACE_FAILURE.. 354 .............................. 505 ..

705 .KEY_EXPIRED....UNSPECIFIED_REASON.... 569 ... 565 .... 547 .........UNAUTHORISED_MAX-ACCESS_ATTEMPT.. 716 ........ 714 .. 718 ..DENIAL_OF_SERVICE. 574 ..... 708 . 564 .....INFORMATION_OUT_OF_SEQUENCE........... 567 .. // Values 553-560 correspond to duplicated probable causes 561 ..............BREACH_OF_CONFIDENTIALITY.RECUCED_LOGGING_CAPABILITY....... 713 .WATCH_DOG_TIMER_EXPIRED...........PROCEDURAL_ERROR........MESSAGE_NOT_INITIALIZED.....NON_REPUDIATION_FAILURE....SYSTEM_RESOURCES_OVERLOAD........REDUCED_EVENT_REPORTING.EXTERNAL_POWER_SUPPLY_FAILURE.ROUTING_FAILURE................Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ......OUT_OF_SERVICE............... 709 . 543 ... 550 ...................... 570 . 701 .........CONNECTION_ESTABLISHMENT_ERROR....VARIABLE_OUT_OF_RANGE. 548 ...................... 573 .................INFORMATION_MISSING...........COOLING_SYSTEM_FAILURE..... 551 ....INFORMATION_MODIFICATION_DETECTED... 545 ..... 572 .. 715 ....INVALID_MSU_RECEIVED.....AUTHENTICATION_FAILURE.......LAPD_LINK_PROTOCOL_FAILURE............... 566 .. 703 .. 571 ..LOCAL_ALARM_INDICATION.INVALID_MESSAGE_RECEIVED.............SYSTEM_CALL_UNSUCCESSFUL..................3100 security alarm causes............. 562 ... 704 ... 544 .......EXTERNAL_TRANSMISSION_DEVICE_FAILURE.. 1360 COM A-9 255-400-466 Issue 4 March 2015 ...........3100 values with an offset of 700... 563 ...... //Values below correspond to M.....BROADCAST_CHANNEL_FAILURE. 702 .TRANSMISSION_ERROR....EXTERNAL_EQUIPMENT_FAILURE... 549 ..... 568 .... // Value 710 corresponds to a duplicated probable cause 711 .REMOTE_ALARM_INDICATION... 717 .DELAYED_INFORMATION. 706 ...TIMEOUT_EXPIRED........MESSAGE_OUT_OF_SEQUENCE...... 712 ......... ..SS7_PROTOCOL_FAILURE.........DUPLICATE_INFORMATION.......UNEXPECTED_INFORMATION........OUT_OF_HOURS_ACTIVITY...........REDUCED_ALARM_REPORTING....... 707 ..................... 552 ...............CABLE_TAMPER............. 546 .... // Value 575 corresponds to a duplicated probable cause // Values 576-700 are reserved for potential future extensions // for 2G & 3G wireless systems //Probable causes originating from M..

............ // It is mainly probable causes for legacy alarms........................................................................................................... 2000 Module down 2001 Link error rate threshold crossed 2002 Chassis Minor Alarm 2003 Chassis Major Alarm 2004 Chassis Temperature Alarm 2100 Problem Outside Exchange 2101 Signalling Link Problem 2102 Clock Tone Problem 2103 Resource Problem 2104 Threshold Reached 2105 Trace Activation 2106 Trace Deactivation 2107 Trace Init Failure 2108 Unexpected Event 2109 Malicious Call 2110 Logging Failure 2111 Security Failure 2112 Customer Defined Alarm 2113 slFailure 2114 linkSet Failure 2115 routSet Unavailable 2116 Remote Powering High Current 2117 Remote Powering Low Current 2118 Unbalanced Load 2119 tALPowerProblem 2120 aMSR 2121 slip 2122 CRC Mismatch 2123 loss Of Frame X50 2124 AISM 2125 FERFM 2126 qInterface Loss Of Communication 2127 Loss Of Timing Sources 2128 User Channel LOS 2129 National Use LOS 2130 User Channel Slip 2131 National Use Slip 2132 Unequipped 2133 Frequency Offset 2134 Inside Failure 2135 Outside Failure 2136 Server Signal Failure 2137 pdh Failure ...............Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ............................................3100 future extensions // Hereafter..................................................................................................................... // Values 719-800 are reserved for potential M............... 1360 COM A-10 255-400-466 Issue 4 March 2015 ..................................................................... the list of the probable causes which are not compliant to 3GPP standard..................................................................................

..Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ............................ 1360 COM A-11 255-400-466 Issue 4 March 2015 .......................................................................................................................................................................................................................................................................... 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 rVGShortCircuitAlarm Internal Communication Problem rVGlowOutputVoltage Transmitter Degraded Channel Failure Auxiliary Unit Pb Auxiliary Unit Pb Deferred Replaceable Unit Unknown Loss Of Modulation Temperature Out Of Range Battery Protection Disabled Battery Door Open sfwr Unit Missing Resource Isolation Unknown Cause Unsupported Ne Version Alarms Flow Too Large Loss Of Cell Del Path AIS Path RDI OAM LNK SEG VP-LOC OAM LNK SEG VC-LOC OAM LNK E2E VP-LOC OAM LNK E2E VC-LOC OAM MATX SEG VP-LOC OAM MATX SEG VC-LOC OAM MATX E2E VP-LOC Section LOS OAM MATX E2E VC-LOC OAM VP-AIS Detected OAM VP-RDI Detected OAM VC-AIS Detected OAM VC-RDI Detected Line/MS AIS Line/MS RDI Section LOF Line AIS Loss Of Pointer Line RDI Signal Fail Label Mismatch Rising Alarm Falling Alarm Link Down Link Up cgprsCgAlarmCgDown cgprsCgAlarmTransFailure cgprsCgAlarmCapacityFull cgprsCgAlarmEchoFailure .................................................................................................................................................................

.................................................................................................................................................................................................................................................................... 1360 COM A-12 255-400-466 Issue 4 March 2015 ......................................................................................................... 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 cgprsCgAlarmCdrDiscard ggsn Service Down map Sgsn Down PCFS function ready PCFS function not ready UcdSnmpAgent Linux linkDown UcdSnmpAgent Linux linkUp fanTemperature Power Supply In Voltage Power Supply Out Voltage Card Voltage 50 Card Voltage 33 Card Voltage25 Card Voltage20 Card Voltage18 Card Voltage15 Cpu Temperature Cold Warm Auth Logical Up Logical Down Chassis Power Cycle Restart Chassis Command Restart Chassis Command Restart Clean Chassis Software Failure Restart Reset Nms Connection Disk Degraded Disk Failure Nms Process Start Nms Process Stop Card Missing Card Removed All Synch References Lost Loss Of Synch Revision/Feature Mismatch Card Dead Card Diagnostic Fault Card Overheated Processor Failure Major Startup DIAG Fail Criticl Startup DIAG Fail Major Backg DIAG Fail Criticl Backg DIAG Fail Major Directed DIAG Fail Criticl Directed DIAG Fail PCMCIA Recovered Error Spare Sectors Exhausted FlashDisk Capacity Too Low ....................................Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ........................................................

............................................................................................................... 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 NVM File Audit Problem DB Maintenance Required DB Corruption Detected NVM Maintenance Required NVM Corruption Detected Card Hard Reset Card Unreachable Time Distribution Failed Atmd-Fabric Diag Failure SEEP Missing Mac2 Address NVM Battery Low EAC LC LFI Fault EAC Fab LFI Fault EAC LC LII Fault EAC IOC LII Fault IOC Unreachable PCMCIA Failure EAC CTL LFI Fault Data Spool Enet Port Down Wrong Card In Slot Card Rev's Too Old Feature Mismatch FIC Revision Mismatch Card Variant Mismatch Module Mismatch IOC Revision Mismatch FI Link Cable Mismatch Application Mismatch NVM File Corrupt Not Talking To Mate CTL Activity Chg To Active Activity Chg To Inactive Actvty Chg Due To Demerits Mate Absent Not Talking To Mate Incompatible Hardware Mate Link Down Inactive Not Sync.................................................................................................................................................................... CSL Down Errored CSL Power Supply Failed Fan Failed Shelf Out Of Service Switch Core Fault Alarm Panel Failed Power Module Failed Sub-Shelf Missing Wrong Sub-Shelf In Bay Sub-Shelf Cable Problem .......................................Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB .................................... 1360 COM A-13 255-400-466 Issue 4 March 2015 ............................................................................................................

.....................................Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ............................ Problem ICON Lockout Enabled Minor Backg DIAG Fail Minor Directed DIAG Fail Minor Startup DIAG Fail Problem on Both Fabrics SCInternal Failure Shelf Fault Startup DIAG Fail Startup DIAG Warning Synch Source Disabled Synch Unit Range Warning BadLC BPlane Link Disabled No TCP/IP connection:0 mgwCardState mgwLinkState mgwPortState mgwCardTempState mgwPriSCMState mgwSecSCMState mgwConfigChange mgwReboot mgwBufferLow mgwBufferNormal mgwCPUHigh mgwCPUNormal ................................................................................................................................. H/W Detected FI Link Disabled FI Links down on X & Y I/O Compatibility Problem I/O F/W Compat........................................... Problem I/O S/W Compat.......... Problem I/O H/W Compat.......................... 1360 COM A-14 255-400-466 Issue 4 March 2015 ....................................................................................................... 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 Sub-Shelf Fault Fabric Switch To X Fabric Switch To Y Fan At Maximum Protection Lost APS-Switch Failure Backg DIAG Fail Background DIAG Warning Backplane Link Disabled Both Fabrics Unavailable Card Version Mismatch CSL Lockout Enabled Directed DIAG Fail Directed DIAG Warning EAC Diag Failure Equipment Failure External Alarm Inputs ON Fan: Min.....................................................................................

............ Possible values are: 1 .637.....................................1..................................................... 1360 COM A-15 255-400-466 Issue 4 March 2015 ......MINOR....1......6.........................3.. 4 ......................................WARNING...............................CRITICAL............3...1.MAJOR..........4...........1............CLEARED.....................1.....4... 2 ....................1..1................1........................................... 6 ..............8 ::= { alarmEntry 8 } perceived_severity OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the levels of severity for operator attention.1.INDETERMINATE....4................. 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 mgwPortStateList mgwPowerRailState mgwFanState mgwPhysPortState mgwClkRefState mgwCardFuncState mgwMIMState mgwActiveSCMState mgwStandbySCMState mgwSCMTakeover mgwActiveSFMState mgwStandbySFMState mgwSFMTakeover mgwActiveCIMState mgwStandbyCIMState mgwCIMTakeover mgwActivePIMState mgwStandbyPIMState mgwPIMTakeover mgwActiveMCMState mgwStandbyMCMState mgwMCMTakeover mgwSyncState mgwUpgradeState mgwAPSOk " -.....4.........1........... " -...............1....6....9 ::= { alarmEntry 9 } specific_problem OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete ............1...... 3 .... 5 ..637....Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB .......

.....1....... Possible values are: 0...... worse.................1......6....1...1.....................1......1.......4..4..1......." -........4.....4.....<high value>].....3.........6.. DESCRIPTION "This object provides further qualification on the alarm than probable_cause " -..................3....1....4..1.. .............1...LESSSEVERE 1..637.........13 ::= { alarmEntry 13 } trend_indication OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object indicates if some observerd condition is getting better.....637..6.......1.3..Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB .MORESEVERE" -.........12 ::= { alarmEntry 12 } back_up_object OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "String carrying of name of the back-up object.................1.................4...........3.........1...637......... 1360 COM A-16 255-400-466 Issue 4 March 2015 ........observedValue= <value>.armTime= <value>......1... or not changing...........1........... True means yes and False means no.....NOCHANGE 2.." -. where: attributeID indicates the monitored data........................1.637.1...................1....1............................1..............................6.................... observerdValue is the value of the monitored data....1....thresholdLevel=[Down|Up][<low value>..14 ::= { alarmEntry 14 } threshold_info OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object provides threshold information to this alarm......................10 ::= { alarmEntry 10 } backed_up_status OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object indicates if an object has a back up...............4. It takes the form of attributeID=<value>..4..1..1.....1...........

....3..............6.4.........1........ 1360 COM A-17 255-400-466 Issue 4 March 2015 ...1.......4.19 ::= { alarmEntry 19 } additional_information OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0...........637................1.. armTime indicates the time...1..........1..637..................................1.1.......4....4....1..21 ::= { alarmEntry 21 } sequence_number OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "Sequence Number is an INTEGER which identifies the sequence of traps for SNMP Manager to detect loss of the trap.1.............1.....1........1..........6..........637.....6....................1...................3.......1......1.....4.....1.....1...4.....15 ::= { alarmEntry 15 } proposed_repair_actions OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object indicates proposed repair actions for operators.....4................. thresholdLevel indicated the range of the threshold and the trend of the data: Down or Up.....6.3...........637.....1....1......1..........4.1...1. " -......1......255)) MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object provides additional information to this alarm.........637........................." -........3. or ...20 ::= { alarmEntry 20 } alarm_id OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "Alarm Id is a string which identifies uniquely the alarm in the alarm list...1.1.....1.....4.................." -...........Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ." -.....1..........1........................" -.............4.....3...1..............18 ::= { alarmEntry 18 } additional_text OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object provides additional information to this alarm..6.......1..

.........3.....4..1... identifies the sequence of alarms during synchronization........637.....6........1......................1........ACKNOWLEDGED 2 ...." -..........4............1. " -..........1......1..............4...........637....................1.1.....3......3.1........1.........1..........................4.....1..............1...1...........4........................4......6.....1..6..........1.........1.....25 ::= { alarmEntry 25 } clear_user_id OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "It carries the identity of the user who invokes the clear alarms operation from OMCCN....................23 ::= { alarmEntry 23 } ack_system_id OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the system(OMCCN)from which the alarm has been acknowledged the last time..1...1...........1.................1..........3.......UNACKNOWLEDGED" -....637.........1..22 ::= { alarmEntry 22 } ack_user_id OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the last user who has changed the acknowledgement state of the alarm in OMCCN" -................" -...4..... Possible values are: 1 ........Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB .........1........ 1360 COM A-18 255-400-466 Issue 4 March 2015 .637.......1................637.....1.26 ::= { alarmEntry 26 } clear_system_id OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "It carries the identity of the system .4......6..24 ::= { alarmEntry 24 } ack_state OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This Object identifies the acknowledgement state of a reported alarm...1....3..........6.....1..1....4.4...........1.1.

........uncompleted " -. backed_up_status.... event_time........3.1...1..1..........30 ::= { alarmEntry 30 } notifyNewAlarm NOTIFICATION-TYPE OBJECTS { trap_version............................4.....Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ...29 ::= { alarmEntry 29 } row_status OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "This object identifies the status of the synchronization: 1 .......1.1.1........ .......28 ::= { alarmEntry 28 } alarm_list_alignment_requirement OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS obsolete DESCRIPTION "It indicates if the AlarmList alignment is required.........1....1............... 1360 COM A-19 255-400-466 Issue 4 March 2015 .normal 2 ...................4....... 1 .................637...1........4.......6......1.637........1......1.........1....... in which uses invokes the clear alarms operation............." -..............1...............4.. Possible values are: 0 ...... managed_object_instance..1......637...........1. " -....... specific_problem......1..4....REQUIRED.6..... probable_cause..........1.3....637. event_type......NOTREQUIRED" -.1....1...........4........3........... trend_indication.......6............4........ system_dn........... back_up_object...1.................. trap_type... notification_id........1.............3.....1...... perceived_severity...............4....1...........27 ::= { alarmEntry 27 } reason OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS obsolete DESCRIPTION "It carries the reason why OMCCN has rebuilt the alarm list......................6....

..........1... ack_system_id....................." -...........4...1. probable_cause......... alarm_id.... event_time...........4........1....3.............4.....1.. 1360 COM A-20 255-400-466 Issue 4 March 2015 .....6. additional_information...................................0......... perceived_severity..... notification_id..............3..637................ where trap_type always is set with x1.....637.." -............. trap_type.................... event_time..... probable_cause.......... system_dn. proposed_repair_actions..................1................6....1..............1. .......2 ::= { alarmTraps 2 } notifyClearedAlarm NOTIFICATION-TYPE OBJECTS { trap_version.......................... sequence_number } STATUS current DESCRIPTION "This notification indicates that a new alarm occured in the NE and has been detected by OMC-CN.Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ........... alarm_id........ event_type..1 ::= { alarmTraps 1 } notifyAckStateChanged NOTIFICATION-TYPE OBJECTS { trap_version..................1.............0... notification_id.....1............. ack_state......... trap_type............ perceived_severity....... threshold_info..... event_type... managed_object_instance.............. system_dn.......... ack_user_id.......... additional_text.. sequence_number } STATUS current DESCRIPTION "This notification indicates that the Acknowledge state of an alarm has been changed by a user........... managed_object_instance............4.......

.....4................ trap_type.............. sequence_number } STATUS current DESCRIPTION . notification_id.... alarm_list_alignment_requirement.1........... managed_object_instance.... perceived_severity.....0........ probable_cause..6...............1. notification_id........637..........1........................4.........1.......................... event_time...3........1.................... managed_object_instance...4 ::= { alarmTraps 4 } notifyChangedAlarm NOTIFICATION-TYPE OBJECTS { trap_version.. clear_system_id..............................3...1.................. event_type.. clear_user_id... event_time.............................. sequence_number } STATUS current DESCRIPTION "This notification indicates that OMC CN is not sure about the integrity of its alarm list and have finished rebuilding its alarms list.......... event_type.....Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB ...." -...... sequence_number } STATUS current DESCRIPTION "This notification indicates that an alarm is cleared.637............1.........1.....................4......... system_dn.......4................................................................6..." -...... alarm_id..3 ::= { alarmTraps 3 } notifyAlarmListRebuilt NOTIFICATION-TYPE OBJECTS { trap_version........ trap_type. 1360 COM A-21 255-400-466 Issue 4 March 2015 ........0... alarm_id........................ system_dn......1..... reason....

.4. event_time. notification_id........................1....3...........4.....1. system_dn.5 ::= { alarmTraps 5 } notifyPotentialFaultyAlarmList NOTIFICATION-TYPE OBJECTS { trap_version..........1.......1...............7 ::= { alarmTraps 7 } notifyHeartBeat NOTIFICATION-TYPE OBJECTS { sequence_number } STATUS current DESCRIPTION "The heart-beat event is fired periodically to tell SNMP Managers the sequence number of the last trap............0...... reason..........6.............4...... trap_type............ "This notification indicates that the severity of an alarm has been changed by a user" -....4........1.." -..................................637................637...............1.....1..............6.3." -......1.......637.... sequence_number } STATUS current DESCRIPTION " This notification indicates that OMC CN is not sure about the integrity of its alarm list and is to rebuild its alarm list.....................................Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB .........0.......... 1360 COM A-22 255-400-466 Issue 4 March 2015 ..........1.........4.............6......1..............1... event_type....................0......... managed_object_instance.......1..3..8 ::= { alarmTraps 8 } END ................................1..........1..................................................4.1..

... 1360 COM B-1 255-400-466 Issue 4 March 2015 ........733 Purpose The 1360 COM serves as a mediation between the NE and the North Bound Interface (NBI).................. The SNMP traps received from SBI are: • • Converted into X......Appendix B: SNMP Traps and X............................................. B-1) indicates the mapping between the alarm as defined by X.....................733 alarms displayed in Fault management GUI Forwarded on SNMP NBI interface • Forwarded on 3GPP Corba NBI interface The Table B-1...................... Table B-1 Alarm mapping Field Name trap_version Significance and syntax 3GPP version used by 1360 COM set to "32.......................................... “Alarm mapping” (p................... This table is a complement to the MIB to give additional explanations.....733 Detailed format of SNMP NBI traps compared to X................................1" Delimiters N/A .......111 V6........733 and the trap sent on NBI...

...... [~] (tilde).................................................................................... For example....................................................](comma) between the two parts of the MOI The forbidden characters in NE friendly name are: ['] (simple quote).............................. [%] (percentage)................ [#] (pound).....................................733 .................... 3GPP MOI....... notification_id A circular counter set by the 1360 COM system_dn Derived from 3GPP system DN definition "SubNetwork=1......... ManagementNode=01.... Delimiters [.......................................................... [... [/] (slash)...... Its syntax is SubNetwork=1....................... [] (anti slash).......... Table B-1 Alarm mapping (continued) Field Name Significance and syntax managed_object_instance This is the MOI (Managed Object Instance) according to 3GPP format..................] (coma).... 1360 COM B-2 255-400-466 Issue 4 March 2015 ......................................... ManagedElement=<NE FriendlyName> where NE FriendlyName is the friendly name of the NE displayed in [Network Management] view of the 1360 COM...................SNMP Traps and X.................733 Detailed format of SNMP NBI traps compared to X..... IRPAgent=1" ......

..................... • Either built by the 1360 COM for non-X733 NE... RDN does not contain the NE friendly name.......................... Its syntax is free............ Its syntax is NE dependent. • Either built by the 1360 COM for non-X733 NE....... Any space characters in a X733 specific problem are replaced by ~ characters..............................................................................733 ................ X733-like Specific Problem is deduced from X733 Specific Problem..... Delimiters [::] (double colon)... Its syntax is free............. ................. between the two parts Its syntax is <RDN> :: <X733-like Specific Problem> RDN is the Relative Distinguished Name of the faulty object in the NE context............................................................................. Table B-1 Alarm mapping Field Name specific_problem (continued) Significance and syntax Is a 3GPP specific problem.......... not a X733 specific problem.733 Detailed format of SNMP NBI traps compared to X...................... because 3GPP TS 32......SNMP Traps and X..................111-3 forbids spaces in AlarmID containing the specific problem.. Its syntax is NE dependent.. 1360 COM B-3 255-400-466 Issue 4 March 2015 ........ RDN is: • Either taken as is from the NE trap for X733-NE.................................................................................................... FDN is the Fully Distinguished Name of the faulty object including the NE identification (a unique identification of the object).............. X733 Specific Problem is: • Either taken as is from the trap for X733-NE...............

........... Its syntax is then free.... ................. It is: [.........733 NE................................. 1360 COM B-4 255-400-466 Issue 4 March 2015 ...... additional_information Is the concatenation of individual X733 Additional information.733 .0........................................................70.......... Table B-1 Alarm mapping Field Name threshold_info (continued) Significance and syntax Is the X............... Its syntax is NE dependent Its syntax is NE-dependent.............................................](comma) between each individual addition info • Either taken as it is from the NE trap for X. An individual additional Info has the following syntax: <name>=<value> <name> and <value> are free text..0........SNMP Traps and X.... It is: • Either taken as is from the NE trap for X733-NE.thresholdLevel= [Down|Up][<low value>................0] thresholdLevel=Down[8....armTime=<value> where: • attributeID indicates the monitored data • observerdValue is the value of the monitored data • thresholdLevel indicated the range of the threshold and the trend of the data: Down or Up • armTime indicates the time Two examples for threshold levels are: thresholdLevel=Up[0...............................................observedValue= <value>............................<high value>].... [=](equal) inside each individual addition info • Either built by the 1360 COM Its syntax is NE-dependent....733 threshold info..................................................................... Its syntax is free..........................733 Detailed format of SNMP NBI traps compared to X..... Delimiters [........0] additional_text Is the X733 Additional text...9................... • Either built by the 1360 COM for non-X733 NE.......] (semi-colon) Its syntax is: attributeID= <value>....................

..................................... • 3GPP MOI • event type Step 1: Concatenation of 3GPP MOI...................... the AlarmID1 format is: • • The same format as previously indicated..................... event type.... between the 5 components: The alarmID is a string of a maximum of 200 characters....... an OMC-PS or a CMC.......................... AlarmID= <alarmID1>%<Checksum> or <truncated alarmID1>%<Checksum> NOTE: When the considered NE is not directly managed by the 1360 COM but is discovered from an OMC-CS.. OMC-PS or 1360 COM B-5 CMC...... notification Id and 3GPP specific problem if a Notification Id is present in the X733 alarm received on the interface between 1360 COM ............... Otherwise the Checksum is concatenated to the AlarmID1 and total length is < 200 characters...........................733 ........................................ if a Notification Id is not present in the X733 alarm received on the interface between 1360 COM and OMC-CS................................ [%](percentage)........ and 3GPP specific problem => alarmID1 • probable cause • 3GPP specific problem • checksum Step 2: Checksum computation on alarmID1 (length can be from 8 to 10 characters) Step 3: Appending alarmID1 to checksum. 255-400-466 Issue 4 March 2015 ...............................SNMP Traps and X.............. If the resulting length is > 200 characters........................ and OMC-CS....733 Detailed format of SNMP NBI traps compared to X..................................... the Alarm Id is truncated to have a maximum alarm id length equal to 200 characters..................... Table B-1 Alarm mapping Field Name alarm_id (continued) Significance and syntax Delimiters Is a string that uniquely identifies the alarm...................................................... probable cause...... OMC-PS or CMC The concatenation of the 3GPP MOI.....................................

..... it is absent from the alarm list sent to OSS on resynchronization..... since the key 1 is not given during resynchronization............................ After the upgrade of any 1360 COM release less than R6.5 to a release greater than R6....................1....... .................. Note: The AlarmId has to be considered as a global key to identify an alarm.................. An alarm already known by the OSS (Alarm 1 with key 1) that is still active after the 1360 COM upgrade is sent out by the 1360 COM with a different key value (Alarm 1 with key 1')......................................733 Detailed format of SNMP NBI traps compared to X....... OSS behavior on change of AlarmId during 1360 COM upgrade: The change in the algorithm to generate the value of alarm ID has no side effect on the OSS on top of SNMP NBI...... So alarm 1 with key 1 should be considered as cleared............................1 and 1360 COM 6............2: the AlarmId format has been modified to prevent from truncation in case AlarmId size would exceed 255 characters..2........................................................... It should not be used to extract any of the elementary information it is composed of.........................2...... Consequently only alarm1 with key 1' is kept by the OSS...... The corresponding alarm should be considered as cleared by the OSS....SNMP Traps and X.......733 .............2..................... 1360 COM B-6 255-400-466 Issue 4 March 2015 ............................1............................... since elementary information might be truncated and then invalid. Note: Change of alarm ID internal format between 1360 COM 6...................... When an alarm is cleared during 1360 COM upgrade..... the OSS performs an alarm resynchronization with the 1360 COM......2.......................5................................

...........................................................................................Glossary ..............................................................................................................................................................................................................................................................................Telecommunication standardization sector ................................................................................................................................................................................................................................................................... C COM Centralized Operations Manager ............................................................................................................................................................................ E ETSI European Telecommunications Standards Institute ........................................................................................... 1360 COM GL-1 255-400-466 Issue 4 March 2015 .................................................................................. I ITU-T International Telecommunication Union ............................. N NBI North Bound Interface ................................................................................................................................................

............................................................................................................................................................................................................ 1360 COM GL-2 255-400-466 Issue 4 March 2015 ...............................................................................................................................................................................Glossary ............................................................... ...............

...................................................... xii .... xi ....................Index A Audience............................... xii Conventions terminological.................................................................. C contact information how to comment................................................... 1360 COM IN-1 255-400-466 Issue 4 March 2015 ......................................... R Related documents.......................................................... ix ............ xi ............. P Purpose...................................................................

.. 1360 COM IN-2 255-400-466 Issue 4 March 2015 .............................................................................................................................................................. ................................................................................................................................................................................................................................................................................Index .........................