1360 com snmp alarm fwd adm guide 255-400-466i4 644145.pdf

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 ............................................................................................................................................................................................. ixix

Changes to this document .......................................................................................................................................................... ixix

Reason for reissue ........................................................................................................................................................................ ixix

Content ............................................................................................................................................................................................... xx

Intended audience ......................................................................................................................................................................... xixi

Terminological conventions ...................................................................................................................................................... xixi

Conventions used .......................................................................................................................................................................... xixi

Related information .................................................................................................................................................................... xiixii

How to comment ......................................................................................................................................................................... xiixii

1 About alarm forwarding

Overview ...................................................................................................................................................................................... 1-11-1

Forwarding traps ....................................................................................................................................................................... 1-11-1

Forwarding changed alarm severity ................................................................................................................................... 1-31-3

Alarm resynchronization ........................................................................................................................................................ 1-61-6

Decreasing the probability of trap overflows ................................................................................................................. 1-61-6

2 Alarm resynchronization

Resynching Alarms .................................................................................................................................................................. 2-12-1

3 SNMPNITF configuration

SNMP North Bound Interface .............................................................................................................................................. 3-13-1

4 1360 COM MIB support for alarm forwarding

Supported MIBs ........................................................................................................................................................................ 4-14-1

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

1360 COM

255-400-466

Issue 4 March 2015

iii

5 Accessing the Network Element list

Access the Network Element list ........................................................................................................................................ 5-15-1

A Priority MIB

ALCATEL-OMCCN-ALARMFORWARDING-MIB ............................................................................................... A-1A-1

B SNMP Traps and X.733

Detailed format of SNMP NBI traps compared to X.733 ......................................................................................... B-1B-1

Glossary

Index

Contents

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

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

iv 1360 COM

255-400-466

Issue 4 March 2015

List of tables

1 Reason for revision ...................................................................................................................................................... ixix

2 Reason for revision ....................................................................................................................................................... xx



B-1 Alarm mapping .......................................................................................................................................................... B-1B-1

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

1360 COM

255-400-466

Issue 4 March 2015

v

List of tables

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

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

vi 1360 COM

255-400-466

Issue 4 March 2015

List of figures

1-1 Change alarm severity ............................................................................................................................................. 1-41-4

1-2 Changed alarm x2 ...................................................................................................................................................... 1-51-5

1-3 OSS filter example .................................................................................................................................................... 1-61-6

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

1360 COM

255-400-466

Issue 4 March 2015

vii

List of figures

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

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

viii 1360 COM

255-400-466

Issue 4 March 2015

About this documentAbout 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.

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.

Changes to this document

Starting with 1360 COM release 2.0, 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.x versions are included.

This document will be reissued with a new issue number when changes are made. This

document may be reissued concurrently with a software release or between releases for

updates or to fix bugs.

Reason for reissue

Issue 4

Table 1 Reason for revision

Chapter Description

1 A new section Decreasing the probability of trap overflows is

added.

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

1360 COM

255-400-466

Issue 4 March 2015

ix

Issue 3


Chapter Description

Appendix A Add new MIB including Reason and alarm_list_alignment_

requirement for OMC-19556.

Issue 2


Chapter Description

1 Starting with COM 3.1 Alarm forwarding preserves severity for

OMC-18895.

Trap types formerly not supported are now supported for

OMC-19556.

Appendix A Add new entries for AlarmEntry and update Changed Alarm

Trap for OMC-19556.

Issue 1


Chapter Description

All The supported release number style has been changed. The

document supports all previous releases and will only be

reissued for bug fixes and new content.

Content

Chapter Description

Chapter 1, “About alarm

forwarding”

About Alarm Forwarding

Chapter 2, “Alarm

resynchronization”

About Alarm Resynchronization

Chapter 3, “SNMPNITF

configuration”

About SNMPNITF Configuration

Chapter 4, “1360 COM

MIB support for alarm

forwarding”

About the MIB supported by 1360 COM for Alarm Forwarding

About this document

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

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

x 1360 COM

255-400-466

Issue 4 March 2015

Chapter Description

Chapter 5, “Accessing the

Network Element list”

How to obtain the list of the Network elements

Appendix A, “Priority

MIB”

ALCATEL-OMCCN- ALARMFORWARDING-MIB

Appendix B, “SNMP

Traps and X.733”

Conversion of SNMP SBI Traps to X.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.

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 Telecommunica-

tions Standards Institute (ETSI) standards.

• This document uses abbreviations developed from the English extended form when

available. Certain abbreviations may be French-based when no English extended form

exists.

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.

• Java is a trademark of Sun Microsystems, Inc.

• UNIX is a registered trademark of The Open Group.

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, keyboard keys, menus, menu

options, tab names

• text in [bold italics in square brackets]: window titles and dialog box names

About this document

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

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

1360 COM

255-400-466

Issue 4 March 2015

xi

• 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, 255-400-454,

How to comment

To comment on this document, go to the Online Comment Form (https://infoproducts.

alcatel-lucent.com/comments/) or email your comments to the Comments Hotline

([email protected]).

About this document

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

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

xii 1360 COM

255-400-466

Issue 4 March 2015

1 1About alarm forwarding

Overview

Purpose

The Alcatel-Lucent 1360 COM provides integrated management for the core network

NEs. In particular, 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.

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.

Overview

The 1360 COM forwards alarms managed by the 1360 COM as SNMP traps:

• For SNMP NEs, 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,

• For other NEs sending alarms natively, all alarms are forwarded as traps by the 1360

COM.

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

1360 COM

255-400-466

Issue 4 March 2015

1-1

1360 COM trap content is similar to the 3GPP definition of an alarm.

These trap types are:

• x1 - New Alarm Trap

• x2 - Changed Alarm Trap

• x3 - Acknowledge State Changed Trap

• x4 - Comment Added Trap (not supported)

• x5 - Cleared Alarm Trap

• x6 - Alarm List Rebuilt Trap (available only when optional 3GPP component is

running)

• x7 - 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. After the rebuild,

NotifyAlarmListRebuilt is triggered

• NotifyHeartBeat: triggered periodically by 1360 COM to notify NMS of the

sequence number of the last trap sent.

If 3GPP north interface is not installed as a package of 1360 COM, AlarmListRebuild(x6)

and PotentialFaultyAlarmList(x7) are generated because these two alarms are produced

by the 3GPP feature.

Comment Added Trap is not supported.

The traps and the fields of the traps are described in the MIB file.

Please refer to the Appendix A, “Priority MIB”.

The mapping between the X.733 attributes of an alarm (as seen in the 1360 COM fault

management GUI) and the trap fields is described in the Appendix B, “SNMP Traps and

X.733”.

About alarm forwarding Forwarding traps

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

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

1-2 1360 COM

255-400-466

Issue 4 March 2015

Forwarding changed alarm severity

Overview

Alarm severity change within the 1360 COM's Fault Management module (CFMA) has

been supported, but the change was internal to the COM only and did not propagate if the

alarm was forwarded.

Starting in COM 3.1, 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, or with that severity change

removed.

Change severity and forward

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

1 Open the Fault Management module.

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

2 From the menu bar, select Tools> Alarm Analysis> Exception.

The Analysis Filter — Exceptions window displays.

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

3 Click the Apply alarm exceptions checkbox.

Click the Change severity to checkbox.

Select the severity to change the alarm to from the pull down menu.

Click the Update additional text to be . . . checkbox and enter some text to identify the

changed alarm for future reference. Useful information includes former severity level and

the reason for change.

About alarm forwarding Forwarding changed alarm severity

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

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

1360 COM

255-400-466

Issue 4 March 2015

1-3

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

4 The changed alarm has a type name including x2, as shown in the figure.

Figure 1-1 Change alarm severity


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

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

1-4 1360 COM

255-400-466

Issue 4 March 2015

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

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

Figure 1-2 Changed alarm x2


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

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

1360 COM

255-400-466

Issue 4 March 2015

1-5

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.

Figure 1-3 OSS filter example


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

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

1-6 1360 COM

255-400-466

Issue 4 March 2015

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

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.

About alarm forwarding Decreasing the probability of trap overflows

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

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

1360 COM

255-400-466

Issue 4 March 2015

1-7

About alarm forwarding Decreasing the probability of trap overflows

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

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

1-8 1360 COM

255-400-466

Issue 4 March 2015

2 2Alarm resynchronization

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.

Note: Row status is used to detect whether the operation of get alarm table is

completed and successful.

If all row statuses are 1, the alarm table is retrieved successfully.

If one of the row statuses is 0 (typically the last row), something failed during the

operation. The result is incomplete and uncertain.

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

1360 COM

255-400-466

Issue 4 March 2015

2-1

Alarm resynchronization Resynching Alarms

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

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

2-2 1360 COM

255-400-466

Issue 4 March 2015

3 3SNMPNITF configuration

SNMP North Bound Interface

Overview

The SNMPNITF configuration is performed through the Platform Management

application.

In the [Platform Management] window, select the COM Configuration tab. The SNMP

North Bound Interface parameters are available under the COM Common configuration

folder -> SNMP North Bound Interface sub-folder.

For example, 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, refer to the Alcatel-Lucent 1360 COM,

Platform Management Operator Guide, 255-400-454, chapter 'SNMP North Bound

Interface'.

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

1360 COM

255-400-466

Issue 4 March 2015

3-1

SNMPNITF configuration SNMP North Bound Interface

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

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

3-2 1360 COM

255-400-466

Issue 4 March 2015

4 41360 COM MIB support for

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.

• Proprietary MIB: ALCATEL-OMCCN-ALARMFORWARDING-MIB. See the

Appendix A, “Priority MIB”.

It is accessible by sftp from the guest account "expftp" in /pub/omc/MIB (for example for

further use by a MIB browser).

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

1360 COM

255-400-466

Issue 4 March 2015

4-1

1360 COM MIB support for alarm forwarding Supported MIBs

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

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

4-2 1360 COM

255-400-466

Issue 4 March 2015

5 5Accessing the Network

Element list

Access the Network Element list

Overview

On the 1360 COM, the file /nedata/NetworkTopology contains the list of the NEs

supervised by the 1360 COM.

It is a csv file that provides information about the list of NEs in the 1360 COM. It is

updated every 2 minutes.

It contains a line per NE; each line contains attributes such as: Friendly Name, NE Type,

NE Release, Virtual group, Master friendly name, IP Address, Secondary IP Address,

Additional addresses, Applications, Geographical Site, Timezone, Hostname, SNMP port,

Supervision State, and Communication State

The process to get this file is described in the Alcatel-Lucent 1360 COM Network

Management Guide, 255-400-457, chapter 'Accessing the NetworkTopology file by

FTP/SFTP'.

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

1360 COM

255-400-466

Issue 4 March 2015

5-1

Accessing the Network Element list Access the Network Element list

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

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

5-2 1360 COM

255-400-466

Issue 4 March 2015

Appendix A: Priority MIB

ALCATEL-OMCCN-ALARMFORWARDING-MIB

Overview

ALCATEL-OMCCN-ALARMFORWARDING-MIB DEFINITIONS ::= BEGIN

-- 2006/12/05 Gu Xiangguo Add alarmTable/alarmEntry/AlarmEntry

definition

-- 2006/12/05 Gu Xiangguo Add trap_number

-- 2007/07/13 Song Song Change item "event_name" to "event_type" for

OCNA01FAG195094

-- 2009/02/04 Zhang Tingyu CR OCNA01CAG229337

-- 2009/04/09 Zhang Tingyu CR OCNA01CAG229337

-- 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

-- 2010/10/25 P. Giaume FR OCNA01FAG231829 : fix AlarmEntry.

-- 2011/10/13 P. Giaume OMC-8533 renaming.

-- 2013/18/13 V. 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;

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."

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

1360 COM

255-400-466

Issue 4 March 2015

A-1

-- 1.3.6.1.4.1.637.1.1.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."

INDEX {

sequence_number

}

-- 1.3.6.1.4.1.637.1.1.4.1

::= { alarmTable 1}

AlarmEntry ::= SEQUENCE {

sequence_number INTEGER,

trap_version DisplayString,

trap_type DisplayString,

event_type DisplayString,

managed_object_instance DisplayString,

notification_id INTEGER,

event_time DisplayString,

system_dn DisplayString,

probable_cause INTEGER,

perceived_severity INTEGER,

specific_problem DisplayString,

backed_up_status DisplayString,

back_up_object DisplayString,

trend_indication INTEGER,

threshold_info DisplayString,

proposed_repair_actions DisplayString,

additional_text DisplayString,

additional_information OCTET STRING,

alarm_id DisplayString,

ack_user_id DisplayString,

ack_system_id DisplayString,

ack_state INTEGER,

clear_user_id DisplayString,

clear_system_id DisplayString,

reason DisplayString,

alarm_list_alignment_requirement INTEGER,

row_status INTEGER }

trap_version OBJECT-TYPE

SYNTAX DisplayString

MAX-ACCESS read-only

STATUS obsolete

DESCRIPTION

"It carries the format version of the trap."

Priority MIB ALCATEL-OMCCN-ALARMFORWARDING-MIB

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

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

A-2 1360 COM

255-400-466

Issue 4 March 2015

-- 1.3.6.1.4.1.637.1.1.4.1.1

::= { alarmEntry 1 }

trap_type OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object identifies one of the following trap types:

x1 - New Alarm Trap

x2 - Changed Alarm Trap

x3 - Ackowledge State Changed Trap

x4 - Comment Added Trap(not supported)

x5 - Cleared Alarm Trap

x6 - Alarm List Rebuilt Trap(available only when optional 3GPP

component is running)

x7 - Potential Faulty Alarm List Trap(available only when

optional 3GPP component is running)

"

-- 1.3.6.1.4.1.637.1.1.4.1.2


event_type OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object identifies one of the following alarm

types:

x1 - COMMUNICATIONS_ALARM

x2 - PROCESSING_ERROR_ALARM

x3 - ENVIRONMENTAL_ALARM

x4 - QUALITY_OF_SERVICE_ALARM

x5 - EQUIPMENT_ALARM

x6 - INTEGRITY_VIOLATION

x7 - OPERATIONAL_VIOLATION

x8 - PHYSICAL_VIOLATION

x9 - SECURITY_SERVICE_OR_MECHANISM_VIOLATION

x10 - TIME_DOMAIN_VIOLATION

"

-- 1.3.6.1.4.1.637.1.1.4.1.3


managed_object_instance OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object identifies the source of this alarm

notification."

-- 1.3.6.1.4.1.637.1.1.4.1.4


notification_id OBJECT-TYPE


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-3

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"This object identifies the notification that carries

the trap."

-- 1.3.6.1.4.1.637.1.1.4.1.5


event_time OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"The time refers to time in Greenwich Time Zone.

It also consists of a time displacement factor

in the form of minutes of displacement from

the Greenwich Meridian.

If the alarm is generated by OMC-CN, then the event time

is the OMC-CN time.

If the alarm is forwarded by OMC-CN from a NE, then the

event time

is the NE time.

"

-- 1.3.6.1.4.1.637.1.1.4.1.6


system_dn OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object identifies the IRPAgent (an entity in OMC-

CN related to the alarms).

It carries the distinguished name of the IRPAgent."

-- 1.3.6.1.4.1.637.1.1.4.1.7


probable_cause OBJECT-TYPE

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"This object identifies the probable cause of a

reported alarm.

// Probable causes originating from M.3100.

// Values below correspond to M.3100 values.

0 - INDETERMINATE;

1 - ALARM_INDICATION_SIGNAL;

2 - CALL_SETUP_FAILURE;

3 - DEGRADED_SIGNAL;

4 - FAR_END_RECEIVER_FAILURE;

5 - FRAMING_ERROR;


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

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

A-4 1360 COM

255-400-466

Issue 4 March 2015

6 - LOSS_OF_FRAME;

7 - LOSS_OF_POINTER;

8 - LOSS_OF_SIGNAL;

9 - PAYLOAD_TYPE_MISMATCH;

// Values 10 correspond to a duplicated probable cause

11 - REMOTE_ALARM_INTERFACE;

12 - EXCESSIVE_BIT_ERROR_RATE;

13 - PATH_TRACE_MISMATCH;

14 - UNAVAILABLE;

15 - SIGNAL_LABEL_MISMATCH;

16 - LOSS_OF_MULTI_FRAME;

17 - COMMUNICATIONS_RECEIVE_FAILURE;

18 - COMMUNICATIONS_TRANSMIT_FAILURE;

19 - MODULATION_FAILURE;

20 - DEMODULATION_FAILURE;

// Values 21-26 correspond to duplicated probable causes

// Values 27-50 are reserved for M.3100 potential future

extensions

51 - BACK_PLANE_FAILURE;

52 - DATA_SET_PROBLEM;

53 - EQUIPMENT_IDENTIFIER_DUPLICATION;

54 - EXTERNAL_IF_DEVICE_PROBLEM;

55 - LINE_CARD_PROBLEM;

56 - MULTIPLEXER_PROBLEM;

57 - NE_IDENTIFIER_DUPLICATION;

58 - POWER_PROBLEM;

59 - PROCESSOR_PROBLEM;

60 - PROTECTION_PATH_FAILURE;

61 - RECEIVER_FAILURE;

62 - REPLACEABLE_UNIT_MISSING;

63 - REPLACEABLE_UNIT_TYPE_MISMATCH;

64 - SYNCHRONIZATION_SOURCE_MISMATCH;

65 - TERMINAL_PROBLEM;

66 - TIMING_PROBLEM;

67 - TRANSMITTER_FAILURE;

68 - TRUNK_CARD_PROBLEM;

69 - REPLACEABLE_UNIT_PROBLEM;

70 - REAL_TIME_CLOCK_FAILURE;


81 - PROTECTION_MECHANISM_FAILURE;

82 - PROTECTING_RESOURCE_FAILURE;

// Values 83-100 are reserved for M.3100 potential future

extensions

101 - AIR_COMPRESSOR_FAILURE;

102 - AIR_CONDITIONING_FAILURE;

103 - AIR_DRYER_FAILURE;

104 - BATTERY_DISCHARGING;

105 - BATTERY_FAILURE;

106 - COMMERCIAL_POWER_FAILURE;


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-5

107 - COOLING_FAN_FAILURE;

108 - ENGINE_FAILURE;

109 - FIRE_DETECTOR_FAILURE;

110 - FUSE_FAILURE;

111 - GENERATOR_FAILURE;

112 - LOW_BATTERY_THRESHOLD;

113 - PUMP_FAILURE;

114 - RECTIFIER_FAILURE;

115 - RECTIFIER_HIGH_VOLTAGE;

116 - RECTIFIER_LOW_F_VOLTAGE;

117 - VENTILATION_SYSTEM_FAILURE;

118 - ENCLOSURE_DOOR_OPEN;

119 - EXPLOSIVE_GAS;

120 - FIRE;

121 - FLOOD;

122 - HIGH_HUMIDITY;

123 - HIGH_TEMPERATURE;

124 - HIGH_WIND;

125 - ICE_BUILD_UP;

126 - INTRUSION_DETECTION;

127 - LOW_FUEL;

128 - LOW_HUMIDITY;

129 - LOW_CABLE_PRESSURE;

130 - LOW_TEMPERATURE;

131 - LOW_WATER;

132 - SMOKE;

133 - TOXIC_GAS;


136 - EXTERNAL_POINT_FAILURE;

// Values 137-150 are reserved for potential M.3100 future

extensions

151 - STORAGE_CAPACITY_PROBLEM;

152 - MEMORY_MISMATCH;

153 - CORRUPT_DATA;

154 - OUT_OF_CPU_CYCLES;

155 - SOFTWARE_ENVIRONMENT_PROBLEM;

156 - SOFTWARE_DOWNLOAD_FAILURE;

157 - LOSS_OF_REAL_TIME;

158 - REINITIALIZED;



extensions


203 - EXCESSIVE_ERROR_RATE;



extensions

//Probable causes originating from X.721.

//Values below correspond to X.721 values with an offset of 300.


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

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

A-6 1360 COM

255-400-466

Issue 4 March 2015

301 - ADAPTER_ERROR;

302 - APPLICATION_SUBSYSTEM_FAILURE;

303 - BANDWIDTH_REDUCED;

// Value 304 corresponds to a duplicated probable cause

305 - COMMUNICATIONS_PROTOCOL_ERROR;

306 - COMMUNICATIONS_SUBSYSTEM_FAILURE;

307 - CONFIGURATION_OR_CUSTOMIZATION_ERROR;

308 - CONGESTION;


310 - CPU_CYCLES_LIMIT_EXCEEDED;

311 - DATA_SET_OR_MODEM_ERROR;


313 - DTE_DCE_INTERFACE_ERROR;


315 - EQUIPMENT_MALFUNCTION;

316 - EXCESSIVE_VIBRATION;

317 - FILE_ERROR;


321 - HEATING_OR_VENTILATION_OR_COOLING_SYSTEM_PROBLEM;

322 - HUMIDITY_UNACCEPTABLE;

323 - INPUT_OUTPUT_DEVICE_ERROR;

324 - INPUT_DEVICE_ERROR;

325 - LAN_ERROR;

326 - LEAK_DETECTED;

327 - LOCAL_NODE_TRANSMISSION_ERROR;


330 - MATERIAL_SUPPLY_EXHAUSTED;


332 - OUT_OF_MEMORY;

333 - OUTPUT_DEVICE_ERROR;

334 - PERFORMANCE_DEGRADED;


336 - PRESSURE_UNACCEPTABLE;


339 - QUEUE_SIZE_EXCEEDED;

340 - RECEIVE_FAILURE;


342 - REMOTE_NODE_TRANSMISSION_ERROR;

343 - RESOURCE_AT_OR_NEARING_CAPACITY;

344 - RESPONSE_TIME_EXCESSIVE;

345 - RETRANSMISSION_RATE_EXCESSIVE;

346 - SOFTWARE_ERROR;

347 - SOFTWARE_PROGRAM_ABNORMALLY_TERMINATED;

348 - SOFTWARE_PROGRAM_ERROR;


350 - TEMPERATURE_UNACCEPTABLE;

351 - THRESHOLD_CROSSED;


353 - TOXIC_LEAK_DETECTED;


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-7

354 - TRANSMIT_FAILURE;


356 - UNDERLYING_RESOURCE_UNAVAILABLE;

357 - VERSION_MISMATCH;

// Values 358-500 are reserved for potential X.721 future

extensions

//Probable causes for 2G & 3G wireless systems.

501 - A_BIS_TO_BTS_INTERFACE_FAILURE;

502 - A_BIS_TO_TRX_INTERFACE_FAILURE;

503 - ANTENNA_PROBLEM;

504 - BATTERY_BREAKDOWN;

505 - BATTERY_CHARGING_FAULT;

506 - CLOCK_SYNCHRONIZATION_PROBLEM;

507 - COMBINER_PROBLEM;

508 - DISK_PROBLEM;


510 - EXCESSIVE_RECEIVER_TEMPERATURE;

511 - EXCESSIVE_TRANSMITTER_OUTPUT_POWER;

512 - EXCESSIVE_TRANSMITTER_TEMPERATURE;

513 - FREQUENCY_HOPPING_DEGRADED;

514 - FREQUENCY_HOPPING_FAILURE;

515 - FREQUENCY_REDEFINITION_FAILED;

516 - LINE_INTERFACE_FAILURE;

517 - LINK_FAILURE;

518 - LOSS_OF_SYNCHRONIZATION;

519 - LOST_REDUNDANCY;

520 - MAINS_BREAKDOWN_WITH_BATTERY_BACKUP;

521 - MAINS_BREAKDOWN_WITHOUT_BATTERY_BACKUP;

522 - POWER_SUPPLY_FAILURE;

523 - RECEIVER_ANTENNA_FAULT;


525 - RECEIVER_MULTICOUPLER_FAILURE;

526 - REDUCED_TRANSMITTER_OUTPUT_POWER;

527 - SIGNAL_QUALITY_EVALUATION_FAULT;

528 - TIMESLOT_HARDWARE_FAILURE;

529 - TRANSCEIVER_PROBLEM;

530 - TRANSCODER_PROBLEM;

531 - TRANSCODER_OR_RATE_ADAPTER_PROBLEM;

532 - TRANSMITTER_ANTENNA_FAILURE;

533 - TRANSMITTER_ANTENNA_NOT_ADJUSTED;


535 - TRANSMITTER_LOW_VOLTAGE_OR_CURRENT;

536 - TRANSMITTER_OFF_FREQUENCY;

537 - DATABASE_INCONSISTENCY;

538 - FILE_SYSTEM_CALL_UNSUCCESSFUL;

539 - INPUT_PARAMETER_OUT_OF_RANGE;

540 - INVALID_PARAMETER;

541 - INVALID_POINTER;

542 - MESSAGE_NOT_EXPECTED;


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

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

A-8 1360 COM

255-400-466

Issue 4 March 2015

543 - MESSAGE_NOT_INITIALIZED;

544 - MESSAGE_OUT_OF_SEQUENCE;

545 - SYSTEM_CALL_UNSUCCESSFUL;

546 - TIMEOUT_EXPIRED;

547 - VARIABLE_OUT_OF_RANGE;

548 - WATCH_DOG_TIMER_EXPIRED;

549 - COOLING_SYSTEM_FAILURE;

550 - EXTERNAL_EQUIPMENT_FAILURE;

551 - EXTERNAL_POWER_SUPPLY_FAILURE;

552 - EXTERNAL_TRANSMISSION_DEVICE_FAILURE;


561 - REDUCED_ALARM_REPORTING;

562 - REDUCED_EVENT_REPORTING;

563 - RECUCED_LOGGING_CAPABILITY;

564 - SYSTEM_RESOURCES_OVERLOAD;

565 - BROADCAST_CHANNEL_FAILURE;

566 - CONNECTION_ESTABLISHMENT_ERROR;

567 - INVALID_MESSAGE_RECEIVED;

568 - INVALID_MSU_RECEIVED;

569 - LAPD_LINK_PROTOCOL_FAILURE;

570 - LOCAL_ALARM_INDICATION;

571 - REMOTE_ALARM_INDICATION;

572 - ROUTING_FAILURE;

573 - SS7_PROTOCOL_FAILURE;

574 - TRANSMISSION_ERROR;


// Values 576-700 are reserved for potential future extensions

// for 2G & 3G wireless systems

//Probable causes originating from M.3100 security alarm causes.

//Values below correspond to M.3100 values with an offset of

700.

701 - AUTHENTICATION_FAILURE;

702 - BREACH_OF_CONFIDENTIALITY;

703 - CABLE_TAMPER;

704 - DELAYED_INFORMATION;

705 - DENIAL_OF_SERVICE;

706 - DUPLICATE_INFORMATION;

707 - INFORMATION_MISSING;

708 - INFORMATION_MODIFICATION_DETECTED;

709 - INFORMATION_OUT_OF_SEQUENCE;


711 - KEY_EXPIRED;

712 - NON_REPUDIATION_FAILURE;

713 - OUT_OF_HOURS_ACTIVITY;

714 - OUT_OF_SERVICE;

715 - PROCEDURAL_ERROR;

716 - UNAUTHORISED_MAX-ACCESS_ATTEMPT;

717 - UNEXPECTED_INFORMATION;

718 - UNSPECIFIED_REASON;


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-9


extensions

// Hereafter, the list of the probable causes which are not

compliant to 3GPP standard.

// 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


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

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

A-10 1360 COM

255-400-466

Issue 4 March 2015

2138 rVGShortCircuitAlarm

2139 Internal Communication Problem

2140 rVGlowOutputVoltage

2141 Transmitter Degraded

2142 Channel Failure

2143 Auxiliary Unit Pb

2144 Auxiliary Unit Pb Deferred

2145 Replaceable Unit Unknown

2146 Loss Of Modulation

2147 Temperature Out Of Range

2148 Battery Protection Disabled

2149 Battery Door Open

2150 sfwr Unit Missing

2151 Resource Isolation

2152 Unknown Cause

2153 Unsupported Ne Version

2154 Alarms Flow Too Large

2155 Loss Of Cell Del

2156 Path AIS

2157 Path RDI

2158 OAM LNK SEG VP-LOC

2159 OAM LNK SEG VC-LOC

2160 OAM LNK E2E VP-LOC

2161 OAM LNK E2E VC-LOC

2162 OAM MATX SEG VP-LOC

2163 OAM MATX SEG VC-LOC

2164 OAM MATX E2E VP-LOC

2165 Section LOS

2166 OAM MATX E2E VC-LOC

2167 OAM VP-AIS Detected

2168 OAM VP-RDI Detected

2169 OAM VC-AIS Detected

2170 OAM VC-RDI Detected

2171 Line/MS AIS

2172 Line/MS RDI

2173 Section LOF

2174 Line AIS

2175 Loss Of Pointer

2176 Line RDI

2177 Signal Fail

2178 Label Mismatch

2179 Rising Alarm

2180 Falling Alarm

2181 Link Down

2182 Link Up

2183 cgprsCgAlarmCgDown

2184 cgprsCgAlarmTransFailure

2185 cgprsCgAlarmCapacityFull

2186 cgprsCgAlarmEchoFailure


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-11

2187 cgprsCgAlarmCdrDiscard

2188 ggsn Service Down

2189 map Sgsn Down

2190 PCFS function ready

2191 PCFS function not ready

2192 UcdSnmpAgent Linux linkDown

2193 UcdSnmpAgent Linux linkUp

2194 fanTemperature

2195 Power Supply In Voltage

2196 Power Supply Out Voltage

2197 Card Voltage 50

2198 Card Voltage 33

2199 Card Voltage25

2200 Card Voltage20

2201 Card Voltage18

2202 Card Voltage15

2203 Cpu Temperature

2204 Cold

2205 Warm

2206 Auth

2207 Logical Up

2208 Logical Down

2209 Chassis Power Cycle Restart

2210 Chassis Command Restart

2211 Chassis Command Restart Clean

2212 Chassis Software Failure Restart

2213 Reset Nms Connection

2214 Disk Degraded

2215 Disk Failure

2216 Nms Process Start

2217 Nms Process Stop

2218 Card Missing

2219 Card Removed

2220 All Synch References Lost

2221 Loss Of Synch

2222 Revision/Feature Mismatch

2223 Card Dead

2224 Card Diagnostic Fault

2225 Card Overheated

2226 Processor Failure

2227 Major Startup DIAG Fail

2228 Criticl Startup DIAG Fail

2229 Major Backg DIAG Fail

2230 Criticl Backg DIAG Fail

2231 Major Directed DIAG Fail

2232 Criticl Directed DIAG Fail

2233 PCMCIA Recovered Error

2234 Spare Sectors Exhausted

2235 FlashDisk Capacity Too Low


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

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

A-12 1360 COM

255-400-466

Issue 4 March 2015

2236 NVM File Audit Problem

2237 DB Maintenance Required

2238 DB Corruption Detected

2239 NVM Maintenance Required

2240 NVM Corruption Detected

2241 Card Hard Reset

2242 Card Unreachable

2243 Time Distribution Failed

2244 Atmd-Fabric Diag Failure

2245 SEEP Missing Mac2 Address

2246 NVM Battery Low

2247 EAC LC LFI Fault

2248 EAC Fab LFI Fault

2249 EAC LC LII Fault

2250 EAC IOC LII Fault

2251 IOC Unreachable

2252 PCMCIA Failure

2253 EAC CTL LFI Fault

2254 Data Spool Enet Port Down

2255 Wrong Card In Slot

2256 Card Rev's Too Old

2257 Feature Mismatch

2258 FIC Revision Mismatch

2259 Card Variant Mismatch

2260 Module Mismatch

2261 IOC Revision Mismatch

2262 FI Link Cable Mismatch

2263 Application Mismatch

2264 NVM File Corrupt

2265 Not Talking To Mate CTL

2266 Activity Chg To Active

2267 Activity Chg To Inactive

2268 Actvty Chg Due To Demerits

2269 Mate Absent

2270 Not Talking To Mate

2271 Incompatible Hardware

2272 Mate Link Down

2273 Inactive Not Sync.

2274 CSL Down

2275 Errored CSL

2276 Power Supply Failed

2277 Fan Failed

2278 Shelf Out Of Service

2279 Switch Core Fault

2280 Alarm Panel Failed

2281 Power Module Failed

2282 Sub-Shelf Missing

2283 Wrong Sub-Shelf In Bay

2284 Sub-Shelf Cable Problem


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-13

2285 Sub-Shelf Fault

2286 Fabric Switch To X

2287 Fabric Switch To Y

2288 Fan At Maximum

2289 Protection Lost

2290 APS-Switch Failure

2291 Backg DIAG Fail

2292 Background DIAG Warning

2293 Backplane Link Disabled

2294 Both Fabrics Unavailable

2295 Card Version Mismatch

2296 CSL Lockout Enabled

2297 Directed DIAG Fail

2298 Directed DIAG Warning

2299 EAC Diag Failure

2300 Equipment Failure

2301 External Alarm Inputs ON

2302 Fan: Min. H/W Detected

2303 FI Link Disabled

2304 FI Links down on X & Y

2305 I/O Compatibility Problem

2306 I/O F/W Compat. Problem

2307 I/O H/W Compat. Problem

2308 I/O S/W Compat. Problem

2309 ICON Lockout Enabled

2310 Minor Backg DIAG Fail

2311 Minor Directed DIAG Fail

2312 Minor Startup DIAG Fail

2313 Problem on Both Fabrics

2314 SCInternal Failure

2315 Shelf Fault

2316 Startup DIAG Fail

2317 Startup DIAG Warning

2318 Synch Source Disabled

2319 Synch Unit Range Warning

2320 BadLC BPlane Link Disabled

2321 No TCP/IP connection:0

3000 mgwCardState

3001 mgwLinkState

3002 mgwPortState

3003 mgwCardTempState

3004 mgwPriSCMState

3005 mgwSecSCMState

3006 mgwConfigChange

3007 mgwReboot

3008 mgwBufferLow

3009 mgwBufferNormal

3010 mgwCPUHigh

3011 mgwCPUNormal


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

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

A-14 1360 COM

255-400-466

Issue 4 March 2015

3012 mgwPortStateList

3013 mgwPowerRailState

3014 mgwFanState

3015 mgwPhysPortState

3016 mgwClkRefState

3017 mgwCardFuncState

3018 mgwMIMState

3019 mgwActiveSCMState

3020 mgwStandbySCMState

3021 mgwSCMTakeover

3022 mgwActiveSFMState

3023 mgwStandbySFMState

3024 mgwSFMTakeover

3025 mgwActiveCIMState

3026 mgwStandbyCIMState

3027 mgwCIMTakeover

3028 mgwActivePIMState

3029 mgwStandbyPIMState

3030 mgwPIMTakeover

3031 mgwActiveMCMState

3032 mgwStandbyMCMState

3033 mgwMCMTakeover

3034 mgwSyncState

3035 mgwUpgradeState

3036 mgwAPSOk

"

-- 1.3.6.1.4.1.637.1.1.4.1.8


perceived_severity OBJECT-TYPE

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"This object identifies the levels of severity for

operator attention.

Possible values are:

1 - INDETERMINATE;

2 - CRITICAL;

3 - MAJOR;

4 - MINOR;

5 - WARNING;

6 - CLEARED;

"

-- 1.3.6.1.4.1.637.1.1.4.1.9


specific_problem OBJECT-TYPE



STATUS obsolete


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-15

DESCRIPTION

"This object provides further qualification on the

alarm than

probable_cause "

-- 1.3.6.1.4.1.637.1.1.4.1.10


backed_up_status OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object indicates if an object has a back up.

True means yes and False means no."

-- 1.3.6.1.4.1.637.1.1.4.1.12


back_up_object OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"String carrying of name of the back-up object."

-- 1.3.6.1.4.1.637.1.1.4.1.13


trend_indication OBJECT-TYPE

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"This object indicates if some observerd condition is

getting

better, worse, or not changing.


0.LESSSEVERE

1.NOCHANGE

2.MORESEVERE"

-- 1.3.6.1.4.1.637.1.1.4.1.14


threshold_info OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object provides threshold information to this

alarm.

It takes the form of attributeID=<value>;observedValue=

<value>;thresholdLevel=[Down|Up][<low value>,<high value>];armTime=

<value>.

where:

attributeID indicates the monitored data;

observerdValue is the value of the monitored data;


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

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

A-16 1360 COM

255-400-466

Issue 4 March 2015

thresholdLevel indicated the range of the threshold and

the trend of the data: Down or Up;

armTime indicates the time.

"

-- 1.3.6.1.4.1.637.1.1.4.1.15


proposed_repair_actions OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object indicates proposed repair actions for

operators."

-- 1.3.6.1.4.1.637.1.1.4.1.18


additional_text OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object provides additional information to this

alarm."

-- 1.3.6.1.4.1.637.1.1.4.1.19


additional_information OBJECT-TYPE

SYNTAX OCTET STRING (SIZE (0..255))


STATUS obsolete

DESCRIPTION

"This object provides additional information to this

alarm."

-- 1.3.6.1.4.1.637.1.1.4.1.20


alarm_id OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"Alarm Id is a string which identifies uniquely the

alarm in the alarm list."

-- 1.3.6.1.4.1.637.1.1.4.1.21


sequence_number OBJECT-TYPE

SYNTAX INTEGER


STATUS current

DESCRIPTION

"Sequence Number is an INTEGER which identifies the sequence of traps

for

SNMP Manager to detect loss of the trap; or


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-17

identifies the sequence of alarms during synchronization."

-- 1.3.6.1.4.1.637.1.1.4.1.22


ack_user_id OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object identifies the last user who has changed

the acknowledgement state of the alarm in OMCCN"

-- 1.3.6.1.4.1.637.1.1.4.1.23


ack_system_id OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"This object identifies the system(OMCCN)from which the

alarm

has been acknowledged the last time."

-- 1.3.6.1.4.1.637.1.1.4.1.24


ack_state OBJECT-TYPE

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"This Object identifies the acknowledgement state of a

reported alarm.


1 - ACKNOWLEDGED

2 - UNACKNOWLEDGED"

-- 1.3.6.1.4.1.637.1.1.4.1.25


clear_user_id OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"It carries the identity of the user who invokes the

clear alarms operation from OMCCN. "

-- 1.3.6.1.4.1.637.1.1.4.1.26


clear_system_id OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"It carries the identity of the system


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

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

A-18 1360 COM

255-400-466

Issue 4 March 2015

in which uses invokes the clear alarms operation. "

-- 1.3.6.1.4.1.637.1.1.4.1.27


reason OBJECT-TYPE



STATUS obsolete

DESCRIPTION

"It carries the reason why OMCCN has rebuilt the alarm

list."

-- 1.3.6.1.4.1.637.1.1.4.1.28


alarm_list_alignment_requirement OBJECT-TYPE

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"It indicates if the AlarmList alignment is required.


0 - REQUIRED,

1 - NOTREQUIRED"

-- 1.3.6.1.4.1.637.1.1.4.1.29


row_status OBJECT-TYPE

SYNTAX INTEGER


STATUS obsolete

DESCRIPTION

"This object identifies the status of the synchronization:

1 - normal

2 - uncompleted

"

-- 1.3.6.1.4.1.637.1.1.4.1.30


notifyNewAlarm NOTIFICATION-TYPE

OBJECTS {

trap_version,

trap_type,

event_type,

managed_object_instance,

notification_id,

event_time,

system_dn,

probable_cause,

perceived_severity,

specific_problem,

backed_up_status,

back_up_object,

trend_indication,


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-19

threshold_info,

proposed_repair_actions,

additional_text,

additional_information,

alarm_id,

sequence_number

}

STATUS current

DESCRIPTION

"This notification indicates that a new alarm occured

in the NE

and has been detected by OMC-CN, where trap_type always

is set with x1."

-- 1.3.6.4.1.637.1.1.4.0.1

::= { alarmTraps 1 }

notifyAckStateChanged NOTIFICATION-TYPE

OBJECTS {

trap_version,

trap_type,

event_type,


notification_id,

event_time,

system_dn,

probable_cause,

perceived_severity,

alarm_id,

ack_user_id,

ack_system_id,

ack_state,

sequence_number

}

STATUS current

DESCRIPTION

"This notification indicates that the Acknowledge state

of an alarm has been changed by a user."

-- 1.3.6.1.4.1.637.1.1.4.0.2


notifyClearedAlarm NOTIFICATION-TYPE

OBJECTS {

trap_version,

trap_type,

event_type,


notification_id,

event_time,

system_dn,

probable_cause,

perceived_severity,


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

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

A-20 1360 COM

255-400-466

Issue 4 March 2015

alarm_id,

clear_user_id,

clear_system_id,

sequence_number

}

STATUS current

DESCRIPTION

"This notification indicates that an alarm is cleared."

-- 1.3.6.4.1.637.1.1.4.0.3


notifyAlarmListRebuilt NOTIFICATION-TYPE

OBJECTS {

trap_version,

trap_type,

event_type,


notification_id,

event_time,

system_dn,

reason,

alarm_list_alignment_requirement,

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."

-- 1.3.6.1.4.1.637.1.1.4.0.4


notifyChangedAlarm NOTIFICATION-TYPE

OBJECTS {

trap_version,

trap_type,

event_type,


notification_id,

event_time,

system_dn,

probable_cause,

perceived_severity,

alarm_id,

sequence_number

}

STATUS current

DESCRIPTION


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

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

1360 COM

255-400-466

Issue 4 March 2015

A-21

"This notification indicates that the severity of an

alarm

has been changed by a user"

-- 1.3.6.1.4.1.637.1.1.4.0.5


notifyPotentialFaultyAlarmList NOTIFICATION-TYPE

OBJECTS {

trap_version,

trap_type,

event_type,


notification_id,

event_time,

system_dn,

reason,

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."

-- 1.3.6.1.4.1.637.1.1.4.0.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."

-- 1.3.6.1.4.1.637.1.1.4.0.8


END


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

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

A-22 1360 COM

255-400-466

Issue 4 March 2015

Appendix B: SNMP Traps and

X.733

Detailed format of SNMP NBI traps compared to X.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.733 alarms displayed in Fault management GUI

• Forwarded on SNMP NBI interface

• Forwarded on 3GPP Corba NBI interface

The Table B-1, “Alarm mapping” (p. B-1) indicates the mapping between the alarm as

defined by X.733 and the trap sent on NBI. This table is a complement to the MIB to give

additional explanations.

Table B-1 Alarm mapping

Field Name Significance and syntax Delimiters

trap_version 3GPP version used by 1360 COM

set to "32.111 V6.1"

N/A

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

1360 COM

255-400-466

Issue 4 March 2015

B-1

Table B-1 Alarm mapping (continued)


managed_object_instance This is the MOI (Managed Object

Instance) according to 3GPP format.

For example, 3GPP MOI.

Its syntax is SubNetwork=1,

ManagedElement=<NE

FriendlyName>

where NE FriendlyName is the

friendly name of the NE displayed in

[Network Management] view of the

1360 COM.

[,](comma) between the

two parts of the MOI

The forbidden characters

in NE friendly name are:

['] (simple quote),

[,] (coma),

[%] (percentage),

[/] (slash),

[] (anti slash),

[#] (pound),

[~] (tilde).

notification_id A circular counter set by the 1360

COM

system_dn Derived from 3GPP system DN

definition "SubNetwork=1,

ManagementNode=01, IRPAgent=1"

SNMP Traps and X.733 Detailed format of SNMP NBI traps compared to X.733

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

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

B-2 1360 COM

255-400-466

Issue 4 March 2015



specific_problem Is a 3GPP specific problem, not a

X733 specific problem.

Its syntax is <RDN> :: <X733-like

Specific Problem>

RDN is the Relative Distinguished

Name of the faulty object in the NE

context. RDN does not contain the

NE friendly name.

FDN is the Fully Distinguished

Name of the faulty object including

the NE identification (a unique

identification of the object).

RDN is:

• Either taken as is from the NE

trap for X733-NE. Its syntax is

free.

• Either built by the 1360 COM

for non-X733 NE. Its syntax is

NE dependent.

X733 Specific Problem is:

• Either taken as is from the trap

for X733-NE. Its syntax is free.



NE dependent.

X733-like Specific Problem is

deduced from X733 Specific

Problem. Any space characters in a

X733 specific problem are replaced

by ~ characters, because 3GPP TS

32.111-3 forbids spaces in AlarmID

containing the specific problem.

[::] (double colon),

between the two parts


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

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

1360 COM

255-400-466

Issue 4 March 2015

B-3



threshold_info Is the X.733 threshold info.

Its syntax is: attributeID=

<value>;observedValue=

<value>;thresholdLevel=

[Down|Up][<low value>,<high

value>];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.0,70.0]

thresholdLevel=Down[8.0,9.0]

[;] (semi-colon)

additional_text Is the X733 Additional text. It is:

• Either taken as is from the NE

trap for X733-NE. Its syntax is

then free.



NE dependent

Its syntax is NE-dependent.

additional_information Is the concatenation of individual

X733 Additional information. It is:

• Either taken as it is from the NE

trap for X.733 NE. Its syntax is

free.


Its syntax is NE-dependent.

An individual additional Info has the

following syntax:

<name>=<value>

<name> and <value> are free text.

[,](comma) between each

individual addition info

[=](equal) inside each

individual addition info


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

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

B-4 1360 COM

255-400-466

Issue 4 March 2015



alarm_id Is a string that uniquely identifies the

alarm.

The alarmID is a string of a

maximum of 200 characters.

Step 1: Concatenation of 3GPP

MOI, event type, probable cause,

and 3GPP specific problem =>

alarmID1

Step 2: Checksum computation on

alarmID1 (length can be from 8 to

10 characters)

Step 3: Appending alarmID1 to

checksum. If the resulting length is >

200 characters, the Alarm Id is

truncated to have a maximum alarm

id length equal to 200 characters.

Otherwise the Checksum is

concatenated to the AlarmID1 and

total length is < 200 characters.

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,

an OMC-PS or a CMC, the

AlarmID1 format is:

• The same format as previously

indicated, if a Notification Id is

not present in the X733 alarm

received on the interface

between 1360 COM and

OMC-CS, OMC-PS or CMC

• The concatenation of the 3GPP

MOI, notification Id and 3GPP

specific problem if a

Notification Id is present in the

X733 alarm received on the

interface between 1360 COM

and OMC-CS, OMC-PS or

CMC.

[%](percentage), between

the 5 components:

• 3GPP MOI

• event type

• probable cause

• 3GPP specific

problem

• checksum


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

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

1360 COM

255-400-466

Issue 4 March 2015

B-5

Note: Change of alarm ID internal format between 1360 COM 6.2.1 and 1360 COM

6.2.2: the AlarmId format has been modified to prevent from truncation in case

AlarmId size would exceed 255 characters.

Note: The AlarmId has to be considered as a global key to identify an alarm.

It should not be used to extract any of the elementary information it is composed of,

since elementary information might be truncated and then invalid.

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.

After the upgrade of any 1360 COM release less than R6.2.1.5 to a release greater than

R6.2.1.5, the OSS performs an alarm resynchronization with the 1360 COM.

When an alarm is cleared during 1360 COM upgrade, it is absent from the alarm list sent

to OSS on resynchronization,. The corresponding alarm should be considered as cleared

by the OSS.

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'). So alarm 1 with key 1 should be considered as cleared, since the key 1 is not

given during resynchronization. Consequently only alarm1 with key 1' is kept by the

OSS.


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

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

B-6 1360 COM

255-400-466

Issue 4 March 2015

Glossary

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

C COM

Centralized Operations Manager

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

E ETSI

European Telecommunications Standards Institute

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

I ITU-T

International Telecommunication Union - Telecommunication standardization sector

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

N NBI

North Bound Interface

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

1360 COM

255-400-466

Issue 4 March 2015

GL-1

Glossary

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

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

GL-2 1360 COM

255-400-466

Issue 4 March 2015

Index

A Audience, xi

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

C contact information

how to comment, xii

Conventions

terminological, xi

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

P Purpose, ix

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

R Related documents, xii

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

1360 COM

255-400-466

Issue 4 March 2015

IN-1

Index

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

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

IN-2 1360 COM

255-400-466

Issue 4 March 2015

1360 com snmp alarm fwd adm guide 255-400-466i4 644145.pdf

Documents

alcatellucent logo

trademarks of alcatel

alarm forwardingoverview

alarm severity

title page1360 comsnmp

forwarding traps

xixirelated information

administrator guide255