ng_ne3s

Flexi Network Gateway Rel. 2.1 2.0, Operating Documentation, v2

NE3S Fault Management SNMP Solution Set

DN0933545 Issue 1-0

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2DN0933545 Issue 1-0


Id:0900d8058096713a

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013/8/21. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN0933545 Issue 1-03


Id:0900d8058096713a

Table of ContentsThis document has 54 pages.

1 Changes in NE3S Fault Management SNMP Solution Set . . . . . . . . . . . 5

2 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Fault management concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1 Implementation of fault management concepts in SNMP . . . . . . . . . . . . 7

4 Alarm-related attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.1 Event Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.2 Additional Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.3 Event Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.4 Acknowledgement related attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 SNMP MIB module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1 Mapping to SNMP MIB objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2 SNMP versions 1 and 2c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3 OID registration tree (SMIv2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.4 Common parameter module (SMIv2). . . . . . . . . . . . . . . . . . . . . . . . . . . 115.5 Fault management parameter module (SMIv2) . . . . . . . . . . . . . . . . . . . 235.6 Registration module (SMIv2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4DN0933545 Issue 1-0


Id:0900d8058096713a

List of TablesTable 1 Protocol specific implementation of the general fault management con-

cepts specified in [1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Table 2 Mapping to SNMP MIB objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 3 Terms and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

DN0933545 Issue 1-05

NE3S Fault Management SNMP Solution Set Changes in NE3S Fault Management SNMP SolutionSet

Id:0900d80580967135

1 Changes in NE3S Fault Management SNMP Solution SetIssue 1-0This is the first version of the document.

6DN0933545 Issue 1-0


Id:0900d80580967115

About this document

2 About this documentThe purpose of this document is to specify the fault management fragment of the Enhanced SNMP Solution Suite for Nokia Siemens Network NetActTM.

The SNMP alarm interface specified in standard RFC's captures only limited areas of network element (NE) functionality and the concepts applied in fault management in telecommunication networks are not considered widely. This leads to a mismatch in functionality when integrating SNMP managed devices with network management systems of a telecommunication network. The Enhanced SNMP Solution Suite aims to provide a comprehensive SNMP interface for telecommunication network management.

This interface is based on the 3GPP specification and represents an implementation of the SNMP solution set of the 3GPP Alarm Integration Reference Point.

The agent, which is the alarm reporting functionality in the network element, fulfils the specified requirements in order to be compliant with this specification.

This document provides the MIB specification as well as information of the underlying basic principles of fault management applicable for SNMP managed devices.

2.1 ScopeThis document covers fault management requirements.

DN0933545 Issue 1-07

NE3S Fault Management SNMP Solution Set Fault management concepts

Id:0900d80580967136

3 Fault management conceptsThe fault management concepts for this interface are defined in [1].

3.1 Implementation of fault management concepts in SNMPThis chapter outlines the protocol specific implementation of the general FM concepts specified in [1]. The table below contains a brief summary of the concept implementa-tion.

Feature in [1]. Implementation in SNMP solution set

Notifications The Notifications are implemented as SNMP Notifications (Traps).

alarmNew noiAlarmNew

alarmCleared noiAlarmCleared

alarmChanged noiAlarmChanged

Alarm Table The SNMP table noiAlarmTable represents the alarm table, containing the active alarms. The manager access this table via SNMP Get operations.

alarmListRebuildInitiated Implemented as SNMP Notifications (Traps): noiAlarmListRebuildInitiated

alarmListRebuild SNMP Notification noiAlarmListRebuild

Alarm Log The SNMP Table noiAlarmLogTable represents the alarm log, containing the data of the recently sent events.

The manager accesses this table with SNMP Get operations

Log full action Implemented as SNMP object noiAlarmLogFullAction.Invoking the opera-tion by setting an appropriate value to the MIB object

Alarm log control Implemented as SNMP object noiAlarmLogControl

Co-operative Acknowledgement The SNMP Table noiAlarmTable contains the information on acknowledge-ment. The manager acknowledges alarms with SNMP Set operations.

alarmAckStateChanged noiAlarmAckStateChanged

Table 1 Protocol specific implementation of the general fault management concepts specified in [1]

8DN0933545 Issue 1-0


Id:0900d80580967134

Alarm-related attributes

4 Alarm-related attributes The relevant attributes are specified in [1].

This chapter lists the SNMP specific deviations.

4.1 Event TimeThe event time is decoded according to the SNMP specification [3]

4.2 Additional TextAdditional Text allows passing additional information on the fault in human readable format. It is used to convey information that helps the operator to identify the cause of the fault. In case of NetAct, the content of this element is divided into two parts and shown in two text fields (max 160 characters).

Thus, the agent has two options to assign a value to this element:

• One text fieldThe agent provides one message in this element (no delimiter). The size must not exceed 255 characters.NE3S manager (NetAct) can divide the string into two parts at a fixed position (char-acter no. 160).

• Two text fieldsThe string passed in an alarm is divided into 2 logical fields, separated by a delimiter. Each field can be up to 160 characters and both must exceed 255 including the delimiter. The two logical fields are separated by the delimiter “horizontal tab” (ASCII character “ht”, (#x9), Dec 009 or Hex 09).NetAct scans the string for the first occurrence of “ht” and splits the string into two parts accordingly.Since the user typically pays more attention to the first part of a text message, the most important information for the end user is given in the first field.

Please note that other special characters (for example, cr, lf) are not allowed here, except for “space (sp)” and “horizontal tab (ht)”.

The clear alarm notification (noiAlarmCleared) can use a zero length character string to reduce the size of the transmitted message.

4.3 Event TypeAccording to 3GPP recommendations, unknown is represented with the value zero (0).

When implementing SNMPv1 / SMIv1, an enumeration must not start with the value zero(0). However, it is standard practice to allow zero valued enumerations for SNMPv1 also.

4.4 Acknowledgement related attributesPresuming that the agent does not support the concept of acknowledgement, these objects can be suppressed in the alarm table and the alarm log (not present in those tables at all). Further details on this can be found in the MIB specification.

DN0933545 Issue 1-09

NE3S Fault Management SNMP Solution Set Alarm-related attributes

Id:0900d80580967134

Presuming that the agent supports these objects in its MIB but not the co-operative acknowledgement (for example, roadmap issue), the agent assigns the following values for all entries in the alarm table and alarm log:

• Acknowledgement State = indeterminate (3) • Acknowledgement Time = "<empty string>" • Acknowledgement User Identification = "<empty string>".

10DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

5 SNMP MIB module

5.1 Mapping to SNMP MIB objects

Name in specification Textual convention or object type in MIB

AcknowledgementState TC NoiAcknowledgementState

Object noiAlarmAckState

noiAlarmLogEntryAckState

AcknowledgementTime TC NoiAcknowledgementTime

Object noiAlarmAckTime

noiAlarmLogEntryAckTime

AcknowledgementUserId TC NoiAcknowledgementUserId

Object noiAlarmAckUserId

noiAlarmLogEntryAckUserId

Additional Text TC NoiAdditionalText

Object noiAlarmAdditionalText

noiAlarmLogEntryAdditionalText

AlarmLog Object noiAlarmLogTable

Alarm Table Object NoiAlarmTable

Alarm Identifier TC NoiAlarmId

Object noiAlarmId

noiAlarmLogEntryAlarmId

Alarm Text TC NoiAlarmText

Object noiAlarmText

noiAlarmLogEntryAlarmText

Event Time TC NoiEeventTime

Object noiAlarmEventTime

noiAlarmLogEntryEventTime

Event Type TC NoiEventType

Object noiAlarmEventType

noiAlarmLogEntryEventType

Perceived Severity TC NoiPerceivedSeverity

Object noiAlarmPerceivedSeverity

noiAlarmLogEntryPerceivedSeverity

Table 2 Mapping to SNMP MIB objects

DN0933545 Issue 1-011

NE3S Fault Management SNMP Solution Set SNMP MIB module

Id:0900d80580967139

5.2 SNMP versions 1 and 2cNokia Siemens Networks has chosen to use SMIv2 syntax to specify the MIB. Nokia Siemens Networks recommends to implement agents based on SNMPv2c, using the SMIv2 protocol.

Nokia Siemens Networks NetAct (TM) supports SNMPV2c and SNMPv1. The agent can choose which SNMP version is used for implementation.

However, due to extended capabilities of the SMIv2 base types and keywords, devia-tions between the SMIv1 and SMIv2 Mobs can occur.

When implementing SNMP v1 protocol (and using SMIv1), the enumeration value zero (0) is not supported. However, as it is standard practice to allow zero valued enumera-tions, no changes have been made to the MIB specification when generating the SMIv1 MIB. The following objects are concerned:

• The enumeration indeterminate for perceived severity and the enumeration unknown for the event type. The usage of indeterminate or unknown is not recom-mended and therefore the deviation is negligible.

• The enumeration wrap for the log full action.

5.3 OID registration tree (SMIv2)Specified in [2]

5.4 Common parameter module (SMIv2)NOKIA-ENHANCED-SNMP-SOLUTION-SUITE-COMMON-DEFINITION DEFINITIONS ::= BEGIN

-- ===============================================================-- Copyright (C) Nokia Networks 2005-- ===============================================================------ Description: MIB file for the Nokia SNMP Solution Suite for-- 3GPP Alarm Integration Reference Point

Probable Cause TC NoiProbableCause

Object noiAlarmProbableCause

noiAlarmLogEntryProbableCause

Specific Problem TC NoiSpecificProblem

Object noiAlarmSpecificProblem

noiAlarmLogEntrySpecificProblem

System Distinguished Name TC NoiSystemDistinguishedName

Object noiAlarmSystemDN

noiAlarmLogEntrySystemDN

Name in specification Textual convention or object type in MIB

Table 2 Mapping to SNMP MIB objects (Cont.)

12DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

-- Purpose is to specify the Fault Management-- interface for Nokia NetAct.-- Further information can be found in the Interface-- specification -- Enhanced SNMP Solution Suite - Fault Management-- ---- Protocol: SNMPv2c MIB (Simple network management protocol,-- version 2c, Management Information Base )-- Format: SMIv2---- Version -- 0.9 : Initial Version-- 1.0 : Changes to Description clauses-- noiSnmpAlarmIrpCommon instead of nokiaSnmpAlarmIrpCommon-- 1.1. OID change, Open SNMP IF now Enhanced SNMP Solution-- Suite -- 1.2.3 : NoiNotificationType introduced-- Version synchronised with Interface specification-- 1.2.4 : NE3S OID Registration MIB File has been renamed,-- to avoid naming conflict with Nokia general OID -- registration MIB.-- 1.2.5 : noiOpenInterfaceModule imported from -- NOKIA-NE3S-REGISTRATION-MIB-- Previous Version wrong---- 1.2.6 : numbering of the elements in NoiNotificationType -- uses now same values as the corresponding Notifications-- i.e.-- noiAlarmChanged (5)-- noiAlarmChanged NOTIFICATION-TYPE ::= { noiAlarmNotification 5}-- 1.2.7 : NoiProbableCause now aligned with values used by 3GPP -- (i.e. same values as used in 3GPP Corba Solution Suite-- The value "Indeterminate (0)" as an extension to 3GPP kept-- NoiAdditionalText now up to 255 characters. -- Optional delimiter introduced to allow two logical fields-- inside -- Wording in Description Clauses modified-- 1.2.8 : Version change only, no changes to MIB-- 1.2.9 : NoiProbableCause - values updated. to comply to latest 3GPP Rel 4 specification---- ===============================================================-- Author : M.Grosse-Kreul et. al.-- Version : 1.2.9-- Last Update : 15.1.2005--================================================================

--======================================================================-- NAMING CONVENTION

DN0933545 Issue 1-013


Id:0900d80580967139

-- -- All Items (Module Indentity and Textual Convention)-- are prefixed with 'Noi' or 'noi'-- 'Noi' shall represent the abbreviation of Nokia Open Interface --======================================================================

IMPORTS Integer32, MODULE-IDENTITY FROM SNMPv2-SMI DisplayString, DateAndTime, TEXTUAL-CONVENTION FROM SNMPv2-TC noiOpenInterfaceModule FROM NOKIA-NE3S-REGISTRATION-MIB;

-- ======================================================================-- MODULE DEFINITION-- ======================================================================

noiSnmpAlarmIrpCommon MODULE-IDENTITY LAST-UPDATED "200501150000Z" ORGANIZATION "Nokia Networks" CONTACT-INFO "e-mail: [email protected]" DESCRIPTION "The definition of common parameters used for Nokia SNMP Solution Set of the 3GPP Alarm IRP also known as NE3S Interface." REVISION "200501150000Z" DESCRIPTION "Version 1.2.9"::= { noiOpenInterfaceModule 1 }

--======================================================================-- TEXTUAL CONVENTIONS-- -- Conventions are in alphabetical order--======================================================================

NoiAcknowledgementState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Identifies the state of the alarm in the alarm table. If the agent does not support the concept of acknowledgement, than the value 'indeterminate (3)' shall be used" SYNTAX INTEGER { acknowledged (1), unacknowledged (2),

14DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

indeterminate (3) }

NoiAcknowledgementTime ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The acknowledgement time is used to set the last time when the acknowledgement state of an alarm in the alarm table has been changed. If the agent does not support the concept of acknowledgement, than the acknowledgement time shall be empty (string length zero(0)) in the alarm table or alarm log." SYNTAX DateAndTime

NoiAcknowledgementUserId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The acknowledgement user id is used to identify the last user who has changed the acknowledgement state of an alarm in the alarm table. When no user information is conveyed, the value can be an empty string (i.e. length of the OCTET STRING shall be 0). The default value is also an empty string" SYNTAX DisplayString (SIZE (0..10))

NoiAdditionalText ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The additional text is used to pass additional information on the fault in the Network Element / EM in a human readable format. It shall be used to tranfer information that supports the operator in identifying the cause of the fault. When no information is carried, the value can be an empty string (i.e. length of the OCTET STRING shall be 0). It is recommended to use the additional text in alarm and changed alarm notification. An empty string shall be used only within clear alarm notification.

The agent has two different options in setting the value - One logical text message The agent provides one text message in this element (i.e. no delimeter). The size may not exceed 255 characters. NE3S manager (i.e. NetAct) can divide the string into two parts at a fixed position (e.g. character no. 160). - Two logical text fields The string passed in an alarm is be divided into 2 logical fields, separated by a delimiter. Each field can be up to

DN0933545 Issue 1-015


Id:0900d80580967139

160 characters and both must exceed 255 including the delimeter. The two logical fields are separated by the delimiter 'horizontal tab' (ASCII character 'ht' , Dec 009 or Hex 09) NetAct scans the string for the first occurrence of 'ht' and split the string into two parts accordingly. Since the user user typically pays more attention at the first part of a text message, the most important information for the end user shall be given in the first field." SYNTAX DisplayString

NoiAlarmId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The alarm identifier shall represent a sequence of positive integer numbers. Each alarm notification emitted by the agent shall have, at any given time, different alarm identifier. The alarm identifier shall increase with every alarm emitted by the agent and within the scope of this specification the value shall be incremented by one (1) whenever an alarm is inserted into the alarm table and an alarm notification is emitted by the agent. The correlation between the clear alarm and the related active alarms is performed in Nokia OSS by means of unambiguous identifiers, the alarm identifier. Therefore the alarm identifier of a clear alarm notification, alarm changed notification or acknowledgement notification must be equal to the alarm identifier of the correlated alarm notification. It is present in all fault management notifications. The initial value of the sequence is one (1). If the maximum value is reached, the sequence will be wrapped back to the initial value one (1). Within the context of this specification the assumption is that the agent assures in any case a sequence of the alarm identifier (e.g. after NE restart, restart of the agent or under similar conditions) Within the context of this specification the alarm identifier in an alarm notification can have the same value as the notification identifier." SYNTAX Integer32 (1..2147483647)

NoiAlarmLogControl ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Controls the behaviour of the log and allows the manager to defined the operation of the log: Values are logging(1) and flush (2) and suspend(3). The default value shall be logging which implies

16DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

normal operation of the log flush indicate a request to empty the current content of the log. Suspend indicate a request to suspended logging" SYNTAX INTEGER { logging (1), flush (2), suspend (3)}

NoiAlarmLogCount ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Contains the number of currently active alarms in the alarm Log." SYNTAX Integer32 (0..2147483647)

NoiAlarmTableCount ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Contains the number of currently active alarms in the alarm Table." SYNTAX Integer32 (0..2147483647)

NoiAlarmText ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Alarm text contains information on the fault situation in the NE in human readable format. A description of the cause of the fault shall be conveyed within the alarm text. The alarm text must be in capital letters. Alarm text shall not be empty, meaning a zero length string must not be used in alarm notifications. A clear alarm notification can use a zero length character string." SYNTAX DisplayString (SIZE (0..64))

NoiEventTime ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Time when the event has occurred. The event time is decoded according to RCF 1903" SYNTAX DateAndTime

NoiEventType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Event type as specified in ITU recommendations

DN0933545 Issue 1-017


Id:0900d80580967139

X.733. The value unknown (0) shall not be used." SYNTAX INTEGER { unknown(0), communicationsAlarm(2), environmentalAlarm(3), equipmentAlarm(4), processingErrorAlarm(10), qualityOfServiceAlarm(11)}

NoiLogFullAction ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Control the behaviour of the log when the log becomes full. Possible values are wrap (0) and halt (1). The default value must be wrap. The agent shall start operate the Log in wrap mode, unless the parameter is changed by the manager" SYNTAX INTEGER { wrap(0), halt(1)}

NoiNotificationId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The notification identifier is typically generated by the alarm system in the Network Element that detects the fault. The notification identifier shall represent a consecutive sequence of positive integer number, starting with the value one (1). The value zero(0) must not be used. The notification identifier in a fault management notification (alarm-, clear alarm notification, severity changed or acknowledgement notification) is used to detect if notification supposed to be received by the OS (manager) application have been lost. Therefore each alarm notification shall have, at any given time, different notification identifier. The notification identifier shall represent a consecutive sequence of positive integer numbers. Each notification emitted by the agent shall have, at any given time, different notification identifier and it shall be a consecutive sequence in any case. Within the scope of this interface the value is incremented by one (1) whenever a notification is emitted by the agent. It is present in all notification (e.g. alarm-, clear alarm notification, severity changed or acknowledgement notification)."

18DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

SYNTAX Integer32 (1..2147483647)

NoiNotificationType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Specifies the type of the notification. Used to determine the type of the engty in the alarm log. Mapping according to the following rules

noiAlarmNew(1) corresponds to noiAlarmNew NOTIFICATION-TYPE ::= { noiAlarmNotification 1 }

noiAlarmCleared (2) corresponds to noiAlarmCleared NOTIFICATION-TYPE ::= { noiAlarmNotification 2}

noiAlarmListRebuild (3) corresponds to noiAlarmListRebuild NOTIFICATION-TYPE ::= { noiAlarmNotification 3}

noiAlarmListRebuildInitiated (4) corresponds to noiAlarmListRebuildInitiated NOTIFICATION-TYPE ::= { noiAlarmNotification 4}

noiAlarmChanged (5) corresponds to noiAlarmChanged NOTIFICATION-TYPE ::={noiAlarmNotification 5}

noiAlarmAckStateChanged (6) corresponds to noiAlarmAckStateChanged NOTIFICATION-TYPE ::= { noiAlarmNotification 6} " SYNTAX INTEGER { noiAlarmNew(1), noiAlarmCleared (2), noiAlarmListRebuild (3), noiAlarmListRebuildInitiated (4), noiAlarmChanged (5), noiAlarmAckStateChanged (6) }

NoiPerceivedSeverity ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Perceived severity defines the severity level of the fault Possible values are specified in ITU An alarm notification must not use the value cleared. A clear alarm notification must use the value cleared. recommendation X.733. The value indeterminate(0) is not recommended to be used within the scope of this interface." SYNTAX INTEGER {

DN0933545 Issue 1-019


Id:0900d80580967139

critical(1), major(2), minor(3), warning(4), cleared(5), indeterminate(0)}

NoiProbableCause ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Probable cause is used to qualify the probable cause of the alarm in a Network Element. The and provides further information than the event type. Supported values are specified by 3GPP. Indeterminate is a NE3S extension and the agent shall assign this value indeterminate to indicate that the ProbableCause is not used." SYNTAX INTEGER { -- The following values are defined in 3GPP indeterminate(0), alarmIndicationSignal (1), callSetupFailure (2), degradedSignalM3100 (3), farEndReceiverFailure (4), framingErrorM3100 (5), lossOfFrame (6), lossOfPointer (7), lossOfSignal (8), payloadTypeMismatch (9), transmissionError (10), remoteAlarmInterface (11), excessiveBitErrorRate (12), pathTraceMismatch (13), unavailable (14), signalLabelMismatch (15), lossOfMultiFrame (16), communicationsReceiveFailure (17), communicationsTransmitFailure (18), modulationFailure (19), demodulationFailure (20), backPlaneFailure (51), dataSetProblem (52), equipmentIdentifierDuplication (53), externalDeviceProblem (54), lineCardProblem (55), multiplexerProblemM3100 (56), neIdentifierDuplication (57), powerProblemM3100 (58), processorProblemM3100 (59), protectionPathFailure (60),

20DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

receiverFailureM3100 (61), replaceableUnitMissing (62), replaceableUnitTypeMismatch (63), synchronisationSourceMismatch (64), terminalProblem (65), timingProblemM3100 (66), transmitterFailureM3100 (67), trunkCardProblem (68), replaceableUnitProblem (69), realTimeClockFailure(70), protectionMechanismFailure (81), protectionResourceFailure (82), airCompressorFailure (101), airConditioningFailure (102), airDryerFailure (103), batteryDischarging (104), batteryFailure (105), commericalPowerFailure (106), coolingFanFailure (107), engineFailure (108), fireDetectorFailure (109), fuseFailure (110), generatorFailure (111), lowBatteryThreshold (112), pumpFailureM3100 (113), rectifierFailure (114), rectifierHighVoltage (115), rectifierLowFVoltage (116), ventilationSystemFailure (117), enclosureDoorOpenM3100 (118), explosiveGas (119), fire (120), flood (121), highHumidity (122), highTemperature (123), highWind (124), iceBuildUp (125), intrusionDetection (126), lowFuel (127), lowHumidity (128), lowCablePressure (129), lowTemperature (130), lowWater (131), smoke (132), toxicGas (133), externalPointFailure (136), storageCapacityProblemM3100 (151), memoryMismatch (152), corruptDataM3100 (153), outOfCpuCycles (154), softwareEnvironmentProblem (155),

DN0933545 Issue 1-021


Id:0900d80580967139

softwareDownloadFailure (156), lossOfRealTime (157), reInitialized (158), excessiveErrorRate (203), adapterError (301), applicationSubsystemFailure (302), bandwidthReduction (303), communicationProtocolError (305), communicationSubsystemFailure (306), configurationOrCustomizingError (307), congestion (308), cpuCyclesLimitExceeded (310), dataSetOrModemError (311), dtedceInterfaceError (313), equipmentMalfunction (315), excessiveVibration (316), fileError (317), heatingOrVentilationOrCoolingSystemProblem (321), humidityUnacceptable (322), inputOutputDeviceError (323), inputdeviceError (324), lanError (325), leakDetection (326), localNodeTransmissionError (327), materialSupplyExhausted (330), outOfMemory (332), outputDeviceError (333), performanceDegraded (334), pressureUnacceptable (336), queueSizeExceeded (339), receiveFailure (340), remoteNodeTransmissionError (342), resourceAtOrNearingCapacity (343), responseTimeExcessive (344), retransmissionRateExcessive (345), softwareError (346), softwareProgramAbnormallyTerminated (347), softwareProgramError (348), temperatureUnacceptable (350), thresholdCrossed (351), toxicLeakDetected (353), transmitFailure (354), underlyingResourceUnavailable (356), versionMismatch (357), aBisToBtsInterfaceFailure (501), aBisToTrxInterfaceFailure (502), antennaProblem (503), batteryBreakdown (504), batteryChargingFault (505), clockSynchronisationProblem (506), combinerProblem (507),

22DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

diskProblem (508), excessiveReceiverTemperature (510), excessiveTransmitterOutputPower (511), excessiveTransmitterTemperature (512), frequencyHoppingDegraded (513), frequencyHoppingFailure (514), frequencyRedefinitionFailed (515), lineInterfaceFailure (516), linkFailure (517), lossOfSynchronisation (518), lostRedundancy (519), mainsBreakdownWithBatteryBackup (520), mainsBreakdownWithoutBatteryBackup (521), powerSupplyFailure (522), receiverAntennaFault (523), receiverMulticouplerFailure (525), reducedTransmitterOutputPower (526), signalQualityEvaluationFault (527), timeslotHardwareFailure (528), transceiverProblem (529), transcoderProblem (530), transcoderOrRateAdapterProblem (531), transmitterAntennaFailure (532), transmitterAntennaNotAdjusted (533), transmitterLowVoltageOrCurrent (535), transmitterOffFrequency (536), databaseInconsistency (537), fileSystemCallUnsuccessful (538), inputParameterOutOfRange (539), invalidParameter (540), invalidPointer (541), messageNotExpected (542), messageNotInitialised (543), messageOutOfSequence (544), systemCallUnsuccessful (545), timeoutExpired (546), variableOutOfRange (547), watchDogTimerExpired (548), coolingSystemFailure (549), externalEquipmentFailure (550), externalPowerSupplyFailure (551), externalTransmissionDeviceFailure (552), reducedAlarmReporting (561), reducedEventReporting (562), recucedLoggingCapability (563), systemResourcesOverload (564), broadcastChannelFailure (565), callEstablishmentError (566), invalidMessageReceived (567), invalidMsuReceived (568), lapdLinkProtocolFailure (569),

DN0933545 Issue 1-023


Id:0900d80580967139

localAlarmIndication (570), remoteAlarmIndication (571), routingFailure (572), ss7ProtocolFailure (573), transmissionFailure (574)}

NoiSpecificProblem ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The specific problem provides further qualification of the alarm than probable cause. It shall be used to classify the fault situation in the Network Element. Specific problem represents a fault specific integer value which shall be unique within the context of the Network Element. The Network Element shall not use the same specific problem for two distinct fault situations." SYNTAX Integer32 (1..99999)

NoiSystemDistinguishedName ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The System Distinguished Name (SDN) represents the system instance that detects the fault and generates the notification The SDN represents the unique Distinguished Name of the instance within the scope of the system or Network Element (sometimes referred to as Local Distinguished Name). The required format is according to Nokia recommendation for distinguished name, for example SMSC-South/LNK-1" SYNTAX DisplayString (SIZE (0..160))

END

5.5 Fault management parameter module (SMIv2)NOKIA-ENHANCED-SNMP-SOLUTION-SUITE-ALARM-IRP DEFINITIONS ::= BEGIN

-- ===============================================================-- Copyright (C) Nokia Networks 2005-- ===============================================================------ Description: MIB file for the Nokia SNMP solution set for-- 3GPP Alarm Integration Refernce Point-- Purpose is to specify the Fault Management

24DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

-- interface for Nokia NetAct.-- Further information can be found in the Interface-- specification -- NE3S interface - Fault Management-- Intranet: NET/IMN/OSS Web Pages---- -- Protocol: SNMPv2c MIB (Simple network management protocol,-- version 2c, Management Information Base )-- Format: SMIv2-- -- Version -- 0.9 : Initial Version-- 1.0 : Changes to Description clauses-- noiSnmpAlarmIrp instead of nokiaSnmpAlarmIrp-- OID's now in module NOKIA-OID-REGISTRATION-MIB-- 1.1. : OID changed, Open SNMP IF now Enhanced SNMP Solution-- Suite -- 1.2.3 : NoiNotificationType imported and used to determine the -- type of the entry in the alarm log-- Version of the MIB synchronised with Interface Spcification-- noiAlarmIrpVersion now 5 character-- 1.2.4 : NE3S OID Registration MIB File has been renamed,-- to avoid naming conflict with Nokia general OID -- registration MIB.-- 1.2.5 : noiOpenInterfaceModule imported from -- NOKIA-NE3S-REGISTRATION-MIB-- Previous Version wrong-- 1.2.6 : no changes in this MIB but due to changes in the -- NOKIA-ENHANCED-SNMP-SOLUTION-SUITE-COMMON-DEFINITION-- version numbering needs to be changed, as both MIB -- shall have same version---- 1.2.7 : Changes to Description clause-- Ordering of objects in alarm log changed to allow-- an implementation that does not use acknowledgement -- related objects in the alarm table and alarm log.-- 1.2.8 : Version change only, no changes to MIB-- 1.2.9 : No changes to MIB-- noiAlarmAckStateChanged can now take the value unacknowledged ---- ===============================================================-- Author : M.Grosse-Kreul et. all.-- Version : 1.2.9-- Last Update : 15.01.2005--================================================================

--======================================================================-- NAMING CONVENTION-- -- All Objects are prefixed with 'noi'

DN0933545 Issue 1-025


Id:0900d80580967139

-- noi shall represent the abbreviation -- Nokia Open Interface--======================================================================

IMPORTS OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE FROM SNMPv2-SMI

MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP FROM SNMPv2-CONF

NoiAcknowledgementState, NoiAcknowledgementTime, NoiAcknowledgementUserId, NoiAdditionalText, NoiAlarmId, NoiAlarmLogControl, NoiAlarmLogCount, NoiAlarmTableCount, NoiAlarmText, NoiSystemDistinguishedName, NoiEventTime, NoiEventType, NoiNotificationId, NoiNotificationType , NoiLogFullAction, NoiPerceivedSeverity, NoiProbableCause, NoiSpecificProblem FROM NOKIA-ENHANCED-SNMP-SOLUTION-SUITE-COMMON-DEFINITION

noiOpenInterfaceModule, noiFaultManagementVariable, noiAlarmNotification, noiAlarmTables, noiAlarmLog, noiFMCompliance FROM NOKIA-NE3S-REGISTRATION-MIB;

noiSnmpAlarmIrp MODULE-IDENTITY LAST-UPDATED "200501150000Z" ORGANIZATION "Nokia Networks" CONTACT-INFO "e-mail: [email protected]" DESCRIPTION "This SNMP MIB-module specifies the SNMP Solution Set of the 3GPP Alarm Integration Reference Point (IRP) also known as NE3S Interface. The purpose of this IRP is to define an interface though which a network element manager or a network element) can communicate alarm information for its managed objects to Nokia OS, NetAct. An alarm is a kind of object that represents an abnormal condition for a managed object. An alarm is active as long as the corresponding abnormal condition remains. The EMS or NE maintains an 'alarm table' and containing all currently active alarms for its managed objects. When an alarm is cleared and acknowledged, it is removed from the alarm table and no longer accessible. The 'Alarm Log' contains history information on the occurred fault situations and emitted alarms notifications." REVISION "200501150000Z" DESCRIPTION "Version 1.2.9"

26DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

::= { noiOpenInterfaceModule 2 }

--======================================================================-- IRP VERSION INFORMATION--======================================================================

noiAlarmIrpVersion OBJECT-TYPE SYNTAX OCTET STRING(SIZE(5)) MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the version of the Alarm IRP supported by the agent. The format is 'nn.m', where 'nn' is the main version number of the interface model and 'm' the release number within the main version. This version is 1.2.9" ::= { noiFaultManagementVariable 1 }

--======================================================================-- General Object Types----======================================================================noiAlarmLastSendNotificationId OBJECT-TYPE SYNTAX NoiNotificationId MAX-ACCESS read-only STATUS current DESCRIPTION "This object represent the notification identifier of last send notification ( noiAlarmNew, noiAlarmCleared, noiAlarmAckStateChanged or noiAlarmChanged) The agent shall store the notification identifier of the last send FM notification in this object immediately after sending the notification. The manager can retrieve the current value of this object to detect lost notifications. This mechanism can be used by the manager when no notification is received for a certain time (e.g. 30 minutes) to evaluate whether an alarm upload or a retrieval of alarms from the alarm log shall be performed"::= { noiFaultManagementVariable 2 }

--======================================================================-- ALARM TABLE-- -- The alarm table is an optional feature of the NE3S Interface

DN0933545 Issue 1-027


Id:0900d80580967139

-- and need to be supported only when fully compliance with the IRP-- specification is desired.-- -- If the Agent does not support the alarm table, the following-- objects will not implemented:-- noiAlarmTableCount-- noiAlarmTable-- noiAlarmEntry-- NoiAlarmEntry-- -- --======================================================================

noiAlarmTableCount OBJECT-TYPE SYNTAX NoiAlarmTableCount MAX-ACCESS read-only STATUS current DESCRIPTION "Contains the number or current active alarms accessible in the alarm table. When the alarm table is empty, the value of this object is zero (0)."::= { noiAlarmTables 1 }

noiAlarmTable OBJECT-TYPE SYNTAX SEQUENCE OF NoiAlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table with information about the alarms that are currently active in the Network Element and accessible for the manager. An Active alarm is characterised by a severity other than cleared. New Alarm When a new alarm is inserted into the alarm table, - acknowledgement user Id shall be an empty string - acknowledgement time shall be the event time, - acknowledgement state shall be set to 'unacknowledged' If the agent does not support the concept of acknowledgement, the value of acknowledgement state will be set to 'indeterminate'. The object noiAlarmLastSendNotificationId is updated according to the value of the notification identifier of the notication 'noiAlarmNew' A notification 'noiAlarmNew' is send by the agent.

Clear Alarm When an active alarm is cleared it will be removed

28DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

from the alarm table, if the acknowledgement state is 'acknowledged'. Otherwise, the alarm will remain in the alarm table and the severity and event time are updated according to the values in the notification 'noiAlarmCleared' If the agent does not support the concept of acknowledgement, than the alarm will be removed from the alarm table when it is cleared. The object noiAlarmLastSendNotificationId is updated according to the value of the notification identifier of the notification 'noiAlarmCleared' A notification 'noiAlarmCleared' is send by agent.

Changed Alarm When the severity of an active alarm is changed the severity of the alarm in the alarm table is changed accordingly. If the alarm has a different additional text than the value is changed in the alarm table also. The acknowledgement state will be set to unacknowledged implicitly. The acknowledgement user id will be set to default value, empty string, the acknowledgement time shall have same value as the event time. Although the value of the acknowledgement state is implicitly changed, the agent must not emit the 'noiAlarmAckStateChanged' notification. The event time of the alarm in the alarm table will be changed according to the value of the event. If the agent does not support the concept of acknowledgement than the value of acknowledgement state, -time and -user id remains unchanged. The alarm is not removed from the alarm table and a notification 'noiAlarmChanged' is send by agent. The object noiAlarmLastSendNotificationId is updated according to the value of the notification identifier of the notification 'noiAlarmChanged'

Acknowledged Alarm When the state of an alarm is changed the acknowledgement state of an alarm in the alarm table is changed accordingly. The acknowledgement used id will be set according to the user. The acknowledgement time is changed also. The event time of the alarm in the alarm table will be changed according to the value of the event. The alarm is removed from the alarm table, when it is already cleared e.g. severity of the alarm in the alarm

DN0933545 Issue 1-029


Id:0900d80580967139

table is 'cleared'. Otherwise, the alarm will remain in the alarm table.

The object noiAlarmLastSendNotificationId is updated according to the value of the notification identifier of the notification 'noiAlarmAckStateChanged' A notification 'noiAlarmAckStateChanged' is send by agent.

Presumed the agent does not support the Co-operative Acknowledgement, than the noiAlarmAckState, noiAlarmAckTime and noiAlarmAckUserId can be suppressed in the implementation of the alarm table."::= { noiAlarmTables 2 }

noiAlarmEntry OBJECT-TYPE SYNTAX NoiAlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "One entry in the alarm table holds one active alarm." INDEX { noiAlarmId }::= { noiAlarmTable 1 }

-- =============================================================================-- This is the definition to be used when implementing the Co-operative-- Acknowledgement. It is used when the full NE3S FM functionaliy is -- implemented (e.g. Element Manager)---- Presumed the agent does support the ack related objects in it's MIB but not -- yet the co-operative acknowledegement(e.g. roadmap issue) than the agent -- shall assign the follwing values for all entries in the alarm table:-- noiAlarmAckState = indeterminte (3), -- noiAlarmAckTime "<empty string>" and -- noiAlarmAckUserId = "<empty string>"---- =============================================================================

NoiAlarmEntry ::= SEQUENCE { noiAlarmId NoiAlarmId, noiAlarmSystemDN NoiSystemDistinguishedName, noiAlarmEventTime NoiEventTime, noiAlarmSpecificProblem NoiSpecificProblem, noiAlarmText NoiAlarmText, noiAlarmPerceivedSeverity NoiPerceivedSeverity, noiAlarmAdditionalText NoiAdditionalText, noiAlarmProbableCause NoiProbableCause, noiAlarmEventType NoiEventType, noiAlarmNotificationId NoiNotificationId,

30DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

noiAlarmAckState NoiAcknowledgementState, noiAlarmAckTime NoiAcknowledgementTime, noiAlarmAckUserId NoiAcknowledgementUserId}

-- =============================================================================-- This is the definition to be used when the Co-operative Ackowledgement-- is not implemented (e.g. Network Element)-- =============================================================================

--NoiAlarmEntry ::= SEQUENCE {-- noiAlarmId NoiAlarmId,-- noiAlarmSystemDN NoiSystemDistinguishedName,-- noiAlarmEventTime NoiEventTime,-- noiAlarmSpecificProblem NoiSpecificProblem,-- noiAlarmText NoiAlarmText,-- noiAlarmPerceivedSeverity NoiPerceivedSeverity,-- noiAlarmAdditionalText NoiAdditionalText,-- noiAlarmProbableCause NoiProbableCause,-- noiAlarmEventType NoiEventType,-- noiAlarmNotificationId NoiNotificationId--}

--======================================================================-- -- The following objects are used in alarm and clear alarm notification-- and in conjunction with the alarm table----======================================================================

noiAlarmId OBJECT-TYPE SYNTAX NoiAlarmId MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the alarm identifier of an alarm in the alarm table It uniquely identifies an entry in the alarm table. The alarmId object is read-only even though it is used as index in the alarm table"::= { noiAlarmEntry 1 }

noiAlarmSystemDN OBJECT-TYPE SYNTAX NoiSystemDistinguishedName MAX-ACCESS read-only STATUS current DESCRIPTION

DN0933545 Issue 1-031


Id:0900d80580967139

"This object represents the System Distinguished Name (SDN) of the managed object detecting the fault."::= { noiAlarmEntry 2}

noiAlarmEventTime OBJECT-TYPE SYNTAX NoiEventTime MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the event time, time of occurrence of the event in the Network Element."::= { noiAlarmEntry 3 }

noiAlarmSpecificProblem OBJECT-TYPE SYNTAX NoiSpecificProblem MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the specific problem assigned to the fault situation."::= { noiAlarmEntry 4 }

noiAlarmText OBJECT-TYPE SYNTAX NoiAlarmText MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the alarm text and contains basic information on the fault"::= { noiAlarmEntry 5 }

noiAlarmPerceivedSeverity OBJECT-TYPE SYNTAX NoiPerceivedSeverity MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the perceived severity of the fault."::= { noiAlarmEntry 6 }

noiAlarmAdditionalText OBJECT-TYPE SYNTAX NoiAdditionalText MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the additional text and provides

32DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

further qualification on the fault."::= { noiAlarmEntry 7 }

noiAlarmProbableCause OBJECT-TYPE SYNTAX NoiProbableCause MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the probable cause of the alarm"::= { noiAlarmEntry 8 }

noiAlarmEventType OBJECT-TYPE SYNTAX NoiEventType MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the event type"::= { noiAlarmEntry 9 }

noiAlarmNotificationId OBJECT-TYPE SYNTAX NoiNotificationId MAX-ACCESS read-only STATUS current DESCRIPTION "This object represent the notification identifier. It is a unique value for a notification."::= { noiAlarmEntry 10 }

noiAlarmAckState OBJECT-TYPE SYNTAX NoiAcknowledgementState MAX-ACCESS read-write STATUS current DESCRIPTION "This object represents the acknowledgement status of the of the alarm If the agent does not support the concept of acknowledgement, than the value 'indeterminate' shall be used"::= { noiAlarmEntry 11 }

noiAlarmAckTime OBJECT-TYPE SYNTAX NoiAcknowledgementTime MAX-ACCESS read-write STATUS current DESCRIPTION "This object represent the time of the last modification

DN0933545 Issue 1-033


Id:0900d80580967139

of the acknowledgement state of an alarm in the alarm table."::= { noiAlarmEntry 12 }

noiAlarmAckUserId OBJECT-TYPE SYNTAX NoiAcknowledgementUserId MAX-ACCESS read-write STATUS current DESCRIPTION "This object represent the user who made the last modification of the acknowledgement state of an alarm in the alarm table."::= { noiAlarmEntry 13 }

--======================================================================-- Mandatory ALARM RELATED NOTIFICATIONS-- -- The notification of the type "noiAlarmNew" shall be used in case of-- an alarm notification.---- The notification of the type "noiAlarmCleared" shall be used in case of-- a clear alarm notification.-- -- The notification of the type "noiAlarmListRebuild" shall be used after-- the rebuild of the agent's alarm table.-- --======================================================================

noiAlarmNew NOTIFICATION-TYPE OBJECTS { noiAlarmSystemDN, noiAlarmId, noiAlarmEventTime, noiAlarmSpecificProblem, noiAlarmText, noiAlarmPerceivedSeverity, noiAlarmAdditionalText, noiAlarmProbableCause, noiAlarmEventType, noiAlarmNotificationId} STATUS current DESCRIPTION "This notification is used when a fault situation occurs in the NE and the agent send the alarm notification to inform the OS about the fault.

The value 'cleared' for the noiAlarmPerceivedSeverity is not allowed for an alarm notification."::= { noiAlarmNotification 1 }

34DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

noiAlarmCleared NOTIFICATION-TYPE OBJECTS { noiAlarmSystemDN, noiAlarmId, noiAlarmEventTime, noiAlarmSpecificProblem, noiAlarmText, noiAlarmPerceivedSeverity, noiAlarmAdditionalText, noiAlarmProbableCause, noiAlarmEventType, noiAlarmNotificationId} STATUS current DESCRIPTION "This notification is used when an alarm is cleared. The only permitted value for the 'noiAlarmPerceivedSeverity' is 'cleared' The value of noiAlarmId must be equal to the value Of the noiAlarmId must of the correlated alarm notification. The noiAlarmSystemDN , noiAlarmSpecificProblem , noiAlarmProbableCause, noiAlarmEventType must be equal to the values of the correlated alarm. The agent might use empty string for noiAlarmText and NoiAlarmAdditionalText, otherwise the values must be equal to the values of the correlated alarm. The active alarm is cleared and removed from the alarm table, if the acknowledgement state is 'acknowledged'. otherwise, the alarm will remain in the alarm table. If the agent does not support the concept of acknowledgement, than the alarm will be removed from the alarm table when this notification is send by the agent"::= { noiAlarmNotification 2}

--======================================================================-- The concept of rebuilding the alarm table provides to altenative-- implementations, described in the Interface Specification---- The agent shall select one strategy for implementation of the rebuild-- process (3GPP compiant or the deiating impemetation). Depening on the -- selection, either the noiAlarmListRebuild noptification or-- noiAlarmListRebuildInitiated noification shall be implemented.--======================================================================

DN0933545 Issue 1-035


Id:0900d80580967139

-- The notification noiAlarmListRebuild shall be used when the 3GPP -- compliant implementation is chosen.

noiAlarmListRebuild NOTIFICATION-TYPE OBJECTS { noiAlarmSystemDN, noiAlarmEventTime, noiAlarmNotificationId} STATUS current DESCRIPTION "This notification is used when the alarm table in the agent has been rebuild. The notification will be emitted after a successful rebuild. On reception of this notification, the manager will synchronise the alarm table in the agent with it's internal alarm table by retrieving the content of the alarm table in the agent. While re-build the alarm table, the agent shall not emit notifications, when entering new alarms into the alarm table. The agent shall use the System DN of it's root instance in this notifications, or leave the element empty. The agent can decide to log this notification in the alarm log like any other notification. The objects, which are not used for this notification shall remain empty (strings) or use default value (0) for integer types."::= { noiAlarmNotification 3}

-- This notification is used in conjunction with the alternatve implementation-- of the alarm table rebuild, described in the Interface Specification.-- The agent must not implement this notification, when the -- noiAlarmListRebuild notification is supported.

noiAlarmListRebuildInitiated NOTIFICATION-TYPE OBJECTS { noiAlarmSystemDN, noiAlarmEventTime, noiAlarmNotificationId} STATUS current DESCRIPTION "This notification is used when the alarm table in the agent is about the be rebuild. The notification will be emitted prior to the rebuild, immediately after dropping the content of the alarm table. On reception of this notification, the manager shall clean the internal alarm table to be in snyc with the agent. The agent shall use the System DN of it's root instance

36DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

in this notifications, or leave the element empty. The agent can decide to log this notification in the alarm log like any other notification. The objects, which are not used for this notification shall remain empty (strings) or use default value (0) for integer types "::= { noiAlarmNotification 4}

--======================================================================-- This notification is an optional feature of the NE3S Interface -- and need to be supported only when fully compliance-- with the Nokia IRP specification is desired.-- --======================================================================noiAlarmChanged NOTIFICATION-TYPE OBJECTS { noiAlarmSystemDN, noiAlarmId, noiAlarmEventTime, noiAlarmSpecificProblem, noiAlarmText, noiAlarmPerceivedSeverity, noiAlarmAdditionalText, noiAlarmProbableCause, noiAlarmEventType, noiAlarmNotificationId} STATUS current DESCRIPTION "This notification is used when the severity of an alarm has changed. The value 'cleared' is not allowed in conjunction with this notification. The value of noiAlarmID must be equal to the value of the noiAlarmId of the correlated alarm notification. The noiAlarmSystemDN , noiAlarmSpecificProblem , NoiAlarmText, noiAlarmProbableCause, noiAlarmEventType must be equal to the values of the correlated alarm. The agent may use a different noiAlarmAdditionalText than the original alarm. The noiAlarmEventTime is naturally different from the original alarm"::= { noiAlarmNotification 5}

--======================================================================-- The concept of acknowledgement is an optional feature of the -- NE3S Interface and need to be supported only when fully compliance-- with the Nokia IRP specification is desired.--

DN0933545 Issue 1-037


Id:0900d80580967139

--======================================================================

noiAlarmAckStateChanged NOTIFICATION-TYPE OBJECTS { noiAlarmSystemDN, noiAlarmId, noiAlarmEventTime, noiAlarmSpecificProblem, noiAlarmText, noiAlarmPerceivedSeverity, noiAlarmAdditionalText, noiAlarmProbableCause, noiAlarmEventType, noiAlarmNotificationId, noiAlarmAckState, noiAlarmAckTime, noiAlarmAckUserId} STATUS current DESCRIPTION "This notification is used when the acknowledgement state of an alarm has changed. The value of - noiAlarmID must be equal to the value of the noiAlarmId of the acknowldged alarm - noiAlarmAckState must be acknowledged (1)

The alarm is removed from the alarm table when the alarm has been cleared before (e.g. severity of the alarm is 'cleared' and this notification has been send by the agent. If the alarm in the alarm table is not cleared, it remains in the table. Values of noiAlarmAckState , noiAlarmAckTime, noiAlarmAckUserId are updated. If the agent does not support the co-operative acknowledgement for alarms, than this notification shall not be supported."::= { noiAlarmNotification 6}

--======================================================================-- ALARM LOG-- -- The Alarm Log is an optional feature of the NE3S Interface and -- need to be supported only when fully compliance with the -- specification is desired.-- --======================================================================

noiAlarmLogFullAction OBJECT-TYPE

38DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

SYNTAX NoiLogFullAction MAX-ACCESS read-write STATUS current DESCRIPTION "Note that this object does not affect to the behaviour of alarm identifier, i.e. when log is in halt mode, alarm identifier continues to be incremented by 1 for each notification emitted by the NE." DEFVAL { wrap }::= { noiAlarmLog 1 }

noiAlarmLogControl OBJECT-TYPE SYNTAX NoiAlarmLogControl MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the activity of the log. Initially this object is set to logging (1) which indicate that the log functionality is operational and all emitted notifications are stored in the log table. This shall be the initial value after restart of the Network Element. When manager sets this object to flush(2), the NE shall empty the current log table. All entries in the alarm table at the time of setting this object are removed. After the completion of the flushing the agent shall set this object to logging(1) and start immediately logging all emitted notification (normal mode of operation) When the manager sets this object to suspend (3), the NE shall interrupt logging of emitted notifications. The manager has to explicitly activate logging for a suspended log by setting this object to logging (1)." DEFVAL { logging }::= { noiAlarmLog 2 }

noiAlarmLogCount OBJECT-TYPE SYNTAX NoiAlarmLogCount MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains the number of current records in the alarm Log. When the alarm log is empty , the value of this object is 0."::= { noiAlarmLog 3 }

noiAlarmLogMaxCount OBJECT-TYPE SYNTAX NoiAlarmLogCount MAX-ACCESS read-only

DN0933545 Issue 1-039


Id:0900d80580967139

STATUS current DESCRIPTION "This object contains the maximum number of records in the alarm Log. The value is implementation dependent."::= { noiAlarmLog 4}

noiAlarmLogTable OBJECT-TYPE SYNTAX SEQUENCE OF NoiAlarmLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Log with information about the alarms that are currently active in the Network Element. An Active alarm is characterised by a severity other than cleared. "::= { noiAlarmLog 5 }

noiAlarmLogEntry OBJECT-TYPE SYNTAX NoiAlarmLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "One entry in the alarm Log holds one current active alarm." INDEX { noiAlarmLogEntryNotificationId }::= { noiAlarmLogTable 1 }

-- =============================================================================-- This is the definition to be used when implementing the Co-operative-- Acknowledgement. It is used when the full NE3S FM functionaliy is -- implemented (e.g. Element Manager)---- Presumed the agent does have the ack related objects in it's MIB but not -- yet the co-operative acknowledegement(e.g. roadmap issue) than the agent -- shall assign the follwing values for all entries in the alarm log:-- noiAlarmLogEntryAckState = indeterminte (3), -- noiAlarmLogEntryAckTime "<empty string>" -- noiAlarmLogEnrtyAckUserId = "<empty string>"-- =============================================================================

NoiAlarmLogEntry ::= SEQUENCE { noiAlarmLogEntryNotificationId NoiNotificationId, noiAlarmLogEntryAlarmId NoiAlarmId, noiAlarmLogEntrySystemDN NoiSystemDistinguishedName, noiAlarmLogEntryEventTime NoiEventTime, noiAlarmLogEntrySpecificProblem NoiSpecificProblem,

40DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

noiAlarmLogEntryAlarmText NoiAlarmText, noiAlarmLogEntryPerceivedSeverity NoiPerceivedSeverity, noiAlarmLogEntryAdditionalText NoiAdditionalText, noiAlarmLogEntryProbableCause NoiProbableCause, noiAlarmLogEntryEventType NoiEventType, noiAlarmLogEntryNotificationType NoiNotificationType, noiAlarmLogEntryAckState NoiAcknowledgementState, noiAlarmLogEntryAckTime NoiAcknowledgementTime, noiAlarmLogEntryAckUserId NoiAcknowledgementUserId}

-- =============================================================================-- This is the definition to be used when the Co-operative Ackowledgement-- is not implemented (e.g. Network Element)-- =============================================================================

--NoiAlarmLogEntry ::= SEQUENCE {-- noiAlarmLogEntryNotificationId NoiNotificationId,-- noiAlarmLogEntryAlarmId NoiAlarmId,-- noiAlarmLogEntrySystemDN NoiSystemDistinguishedName,-- noiAlarmLogEntryEventTime NoiEventTime,-- noiAlarmLogEntrySpecificProblem NoiSpecificProblem,-- noiAlarmLogEntryAlarmText NoiAlarmText,-- noiAlarmLogEntryPerceivedSeverity NoiPerceivedSeverity,-- noiAlarmLogEntryAdditionalText NoiAdditionalText,-- noiAlarmLogEntryProbableCause NoiProbableCause,-- noiAlarmLogEntryEventType NoiEventType,-- noiAlarmLogEntryNotificationType NoiNotificationType--}

noiAlarmLogEntryNotificationId OBJECT-TYPE SYNTAX NoiNotificationId MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the notification identifier of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 1 }

noiAlarmLogEntryAlarmId OBJECT-TYPE SYNTAX NoiAlarmId MAX-ACCESS read-only STATUS current DESCRIPTION

DN0933545 Issue 1-041


Id:0900d80580967139

"This object represents the alarm identifier of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 2 }

noiAlarmLogEntrySystemDN OBJECT-TYPE SYNTAX NoiSystemDistinguishedName MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the System Distinguished name of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 3 }

noiAlarmLogEntryEventTime OBJECT-TYPE SYNTAX NoiEventTime MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the event time of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 4 }

noiAlarmLogEntrySpecificProblem OBJECT-TYPE SYNTAX NoiSpecificProblem MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the specific problem of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 5 }

noiAlarmLogEntryAlarmText OBJECT-TYPE SYNTAX NoiAlarmText MAX-ACCESS read-only STATUS current

42DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

DESCRIPTION "This object represents the alarm text of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 6 }

noiAlarmLogEntryPerceivedSeverity OBJECT-TYPE SYNTAX NoiPerceivedSeverity MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the perceived severity of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 7 }

noiAlarmLogEntryAdditionalText OBJECT-TYPE SYNTAX NoiAdditionalText MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the additional text of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 8 }

noiAlarmLogEntryProbableCause OBJECT-TYPE SYNTAX NoiProbableCause MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the probable cause of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 9 }

noiAlarmLogEntryEventType OBJECT-TYPE SYNTAX NoiEventType MAX-ACCESS read-only

DN0933545 Issue 1-043


Id:0900d80580967139

STATUS current DESCRIPTION "This object represents the event type of a logged notification The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 10 }

noiAlarmLogEntryAckState OBJECT-TYPE SYNTAX NoiAcknowledgementState MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the acknowledgement status of the of the logged alarm If the agent does not support the concept of acknowledgement, than the value indeterminate shall be used"::= { noiAlarmLogEntry 11 }

noiAlarmLogEntryAckTime OBJECT-TYPE SYNTAX NoiAcknowledgementTime MAX-ACCESS read-only STATUS current DESCRIPTION "This object represent the time of the last modification of the acknowledgement of a logged notification. The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 12 }

noiAlarmLogEntryAckUserId OBJECT-TYPE SYNTAX NoiAcknowledgementUserId MAX-ACCESS read-only STATUS current DESCRIPTION "This object represent the user who made the last modification of the acknowledgement state of logged notification. The value of this field shall equal to the value of correlated field in the alarm- or clear alarm notification."::= { noiAlarmLogEntry 13 }

noiAlarmLogEntryNotificationType OBJECT-TYPE SYNTAX NoiNotificationType

44DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the type of the logged notification"::= { noiAlarmLogEntry 14 }

-- ======================================================================-- Mapping between objects in alarm notifications and entries in alarm Log------ Object in Alarm notification | Object in Alarm Log-- and alarm table | -- -- noiAlarmId | noiAlarmLogEntryAlarmId-- noiAystemDN | noiAlarmLogEntrySystemDN-- noiEeventTime | noiAlarmLogEntryEventTime-- noiAlarmSpecificProblem | noiAlarmLogEntrySpecificProblem-- noiAlarmText | noiAlarmLogEntryAlarmText-- noiAlarmPerceivedSeverity | noiAlarmLogEntryPerceivedSeverity-- noiAlarmAdditionalText | noiAlarmLogEntryAdditionalText-- noiAlarmProbableCause | noiAlarmLogEntryProbableCause-- noiAlarmEventType | noiAlarmLogEntryEventType-- noiAlarmAckState | noiAlarmLogEntryAckState-- noiAlarmAckTime | noiAlarmLogEntryAckTime-- noiAlarmAckUserId | noiAlarmLogEntryAckUserId

--======================================================================-- COMPLIANCE STATEMENTS--======================================================================

noiAlarmIRPompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "This specifies the objects that are required to claim compliance to Nokia NE3S Interface." MODULE MANDATORY-GROUPS { noiAlarmAdministrationMandatoryGroup, noiAlarmNotificationMandatoryGroup}

GROUP noiAlarmNotificationOptionalGroup DESCRIPTION "This group is not required. A SNMP agent may support the concept of changing the severity of an alarm and emitting a noiAlarmChanged notification."

GROUP noiAlarmTableOptionalGroup

DN0933545 Issue 1-045


Id:0900d80580967139

DESCRIPTION "This group is not required. A SNMP agent may support the alarm Table and the related objects in the group. Nokia recommend to implement the alarm table feature"

GROUP noiAlarmTableRebuildOptionalGroup DESCRIPTION "This group is not required. A SNMP agent may support the concept of rebuilding the alarm Table an the notificaton specified for this group. This groups requires the implementation of the optional feature noiAlarmTableOptionalGroup. "

GROUP noiAlarmAcknwledgementOptionalGroup DESCRIPTION "This group is not required. A SNMP agent may support the acknowledgement concept, the related notification noiAlarmAckStateChanged and the SET operation on the alarm table. This groups requires the implementation of the optional feature noiAlarmTableOptionalGroup. "

GROUP noiAlarmLogOptionalGroup DESCRIPTION "This group is not required. A SNMP agent may support the alarm Log, and further related objects in the group."

::= { noiFMCompliance 1 }

--======================================================================-- GROUP DEFINITION--======================================================================

noiAlarmAdministrationMandatoryGroup OBJECT-GROUP OBJECTS { noiAlarmIrpVersion } STATUS current DESCRIPTION "A collection of objects that represents mandatory administrative attributes for the Alarm IRP." ::= { noiFMCompliance 2 }

noiAlarmNotificationMandatoryGroup NOTIFICATION-GROUP NOTIFICATIONS { noiAlarmNew,

46DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

noiAlarmCleared } STATUS current DESCRIPTION "A collection of mandatory alarm notifications." ::= { noiFMCompliance 4 }

noiAlarmNotificationOptionalGroup NOTIFICATION-GROUP NOTIFICATIONS { noiAlarmChanged } STATUS current DESCRIPTION "A collection of optional alarm related notifications." ::= { noiFMCompliance 5 }

noiAlarmTableOptionalGroup OBJECT-GROUP OBJECTS { noiAlarmTableCount, noiAlarmLastSendNotificationId, noiAlarmId, noiAlarmSystemDN, noiAlarmEventTime, noiAlarmSpecificProblem, noiAlarmText, noiAlarmPerceivedSeverity, noiAlarmAdditionalText, noiAlarmProbableCause, noiAlarmEventType, noiAlarmNotificationId, noiAlarmAckState, noiAlarmAckTime, noiAlarmAckUserId} STATUS current DESCRIPTION "A collection of objects that represents optional functionality to store active alarms in the alarm table." ::= { noiFMCompliance 6 }

noiAlarmTableRebuildOptionalGroup NOTIFICATION-GROUP NOTIFICATIONS {noiAlarmListRebuild , noiAlarmListRebuildInitiated } STATUS current DESCRIPTION "A collection of optional alarm notifications, to be used in conjunction with the concept of rebuilding the alarm table. Depening on the selected strategy, either the noiAlarmListRebuild noptification or noiAlarmListRebuildInitiated noification shall be implemented.."

DN0933545 Issue 1-047


Id:0900d80580967139

::= { noiFMCompliance 7 }

noiAlarmAcknwledgementOptionalGroup NOTIFICATION-GROUP NOTIFICATIONS { noiAlarmAckStateChanged } STATUS current DESCRIPTION "A collection of optional alarm related notifications." ::= { noiFMCompliance 8 }

noiAlarmLogOptionalGroup OBJECT-GROUP OBJECTS { noiAlarmLogFullAction, noiAlarmLogControl, noiAlarmLogCount, noiAlarmLogMaxCount, noiAlarmLogEntryAlarmId, noiAlarmLogEntrySystemDN, noiAlarmLogEntryEventTime, noiAlarmLogEntrySpecificProblem, noiAlarmLogEntryAlarmText, noiAlarmLogEntryPerceivedSeverity, noiAlarmLogEntryAdditionalText, noiAlarmLogEntryProbableCause, noiAlarmLogEntryEventType, noiAlarmLogEntryNotificationId, noiAlarmLogEntryAckState, noiAlarmLogEntryAckTime, noiAlarmLogEntryAckUserId, noiAlarmLogEntryNotificationType} STATUS current DESCRIPTION "A collection of objects that represents optional functionality to store a history of emitted notifications." ::= { noiFMCompliance 9 }

5.6 Registration module (SMIv2)NOKIA-NE3S-REGISTRATION-MIB DEFINITIONS ::= BEGIN

-- ===============================================================-- Copyright (C) Nokia Networks 2004-- ===============================================================------ Description: MIB file for the Nokia OID registration tree-- used in conjunction with the -- Enhanced SNMP Solution Suite

48DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

-- -- Protocol: SNMPv2c MIB (Simple network management protocol,-- version 2c, Management Information Base )-- Format: SMIv2---- Version -- 1.0 : FM PM -- 1.3 : CM OID's added-- 1.3.1 : MIB File renamed, to avoid naming conflict with -- Nokia general OID registration MIB.-- OID for "nokia" and "nokiaSNMPInteface" now imported-- from general registration MIB, where the OIDis -- defined first -- 1.4 : Software Management OID added-- 1.5 : Generic Notification Service OID added-- 1.5.1. : GNSCompliance added-- 1.6 : Hardware Management OID added-- Comment on importing enterprise OID added -- -- ===============================================================-- Author : M.Grosse-Kreul et. all.-- Version : 1.6-- Last Update : 19.3.2004--================================================================

IMPORTS enterprises FROM RFC1155-SMI ;

-- NOTE -- RFC 1155 specifies the enterprise OID for SNMPV1. Typically the SNMP tools are capable of importing -- the enterprise OID via this definition file. -- -- RFC 1902 specifies the same OID for SNMPV2c. Semantically and syntactically both are the same. However -- in case the SNMP tools can not import the enterprise OID from RFC1155-SMI use the following instead -- enterprises -- FROM SNMPv2-SMI ; nokia OBJECT IDENTIFIER ::= { enterprises 94 } nokiaSnmpInterface OBJECT IDENTIFIER ::= { nokia 7 }

--====================================================================== -- -- Topmost Object Identifier for Fault Management in the -- Enhanced SNMP Solution Suite -- -- OID for Fault Management branch of the Enhanced SNMP Solution Suite

DN0933545 Issue 1-049


Id:0900d80580967139

-- ===================================================================== noiFaultManagement OBJECT IDENTIFIER ::= { nokiaSnmpInterface 1 }

-- --------------------------------------------------------------------- -- OID for Interface Modules used within NEe3S -- --------------------------------------------------------------------- noiOpenInterfaceModule OBJECT IDENTIFIER ::= { noiFaultManagement 1 }

-- ===================================================================== -- OID for Fault Management Objects of the Enhanced SNMP Solution Suite -- =====================================================================

-- --------------------------------------------------------------------- -- OID for Common Variables used within SNMP based Fault Management -- --------------------------------------------------------------------- noiFaultManagementVariable OBJECT IDENTIFIER ::= { noiFaultManagement 2}

-- --------------------------------------------------------------------- -- OID for Notification in SNMP based Fault Management -- --------------------------------------------------------------------- noiAlarmNotificationDef OBJECT IDENTIFIER ::= { noiFaultManagement 3 } noiAlarmNotification OBJECT IDENTIFIER ::= { noiAlarmNotificationDef 0 }

-- --------------------------------------------------------------------- -- OID for alarm table in SNMP based Fault Management -- --------------------------------------------------------------------- noiAlarmTables OBJECT IDENTIFIER ::= { noiFaultManagement 4 }

-- --------------------------------------------------------------------- -- OID for Alarm Log in SNMP based Fault Management -- --------------------------------------------------------------------- noiAlarmLog OBJECT IDENTIFIER ::= { noiFaultManagement 5 }

-- --------------------------------------------------------------------- -- OID for Compliance Statement Fault Management -- --------------------------------------------------------------------- noiFMCompliance OBJECT IDENTIFIER ::= { noiFaultManagement 6 }

--=================================================================== -- -- Topmost Object Identifier for Configuration Management in the -- Enhanced SNMP Solution Suite -- -- OID for Basic ConfigurationManagement Management branch of the

50DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

-- Enhanced SNMP Solution Suite -- ================================================================== noiConfigurationManagement OBJECT IDENTIFIER ::= { nokiaSnmpInterface 2 }

-- --------------------------------------------------------------------- -- OID for Common Variables used within SNMP based Configuration Management -- --------------------------------------------------------------------- noiConfigurationManagementVariable OBJECT IDENTIFIER ::= { noiConfigurationManagement 2}

-- --------------------------------------------------------------------- -- OID for Notification in SNMP based ConfigurationManagement Management -- ---------------------------------------------------------------------

noiConfigurationManagementNotificationDef OBJECT IDENTIFIER ::= { noiConfigurationManagement 3 } noiConfigurationManagementNotification OBJECT IDENTIFIER ::= { noiConfigurationManagementNotificationDef 0 } noiConfigurationManagementCompliance OBJECT IDENTIFIER ::= { noiConfigurationManagement 4 }

--====================================================================== -- -- Topmost Object Identifier for Performance Management -- -- OID for Performance Management branch of the Enhanced SNMP Solution Suite -- ===================================================================== noiPerformanceManagement OBJECT IDENTIFIER ::= { nokiaSnmpInterface 3 }

-- --------------------------------------------------------------------- -- OID for Common Variables used within SNMP based Performance Management -- --------------------------------------------------------------------- noiPmVariable OBJECT IDENTIFIER ::= { noiPerformanceManagement 2}

-- --------------------------------------------------------------------- -- OID for Notification in SNMP based Performance Management -- --------------------------------------------------------------------- noiPmNotificationDef OBJECT IDENTIFIER ::= { noiPerformanceManagement 3 } noiPmNotification OBJECT IDENTIFIER ::= { noiPmNotificationDef 0 }

-- ---------------------------------------------------------------------

DN0933545 Issue 1-051


Id:0900d80580967139

-- OID for tables in SNMP based Performance Management -- --------------------------------------------------------------------- noiPmTable OBJECT IDENTIFIER ::= { noiPerformanceManagement 4 }

-- --------------------------------------------------------------------- -- OID for Compliance Statement Performance Management -- --------------------------------------------------------------------- noiPmCompliance OBJECT IDENTIFIER ::= { noiPerformanceManagement 6 }

--====================================================================== -- -- Topmost Object Identifier for Software Management -- -- OID for Software Management branch of the Enhanced SNMP Solution Suite -- ===================================================================== noiSoftwareManagement OBJECT IDENTIFIER ::= { nokiaSnmpInterface 4 }

-- --------------------------------------------------------------------- -- OID for Common Variables used within SNMP based Software Management -- --------------------------------------------------------------------- noiSWMVariable OBJECT IDENTIFIER ::= { noiSoftwareManagement 2}

-- --------------------------------------------------------------------- -- OID for Notification in SNMP based Software Management -- --------------------------------------------------------------------- noiSWMNotificationDef OBJECT IDENTIFIER ::= { noiSoftwareManagement 3 } noiSWMNotification OBJECT IDENTIFIER ::= { noiSWMNotificationDef 0 }

-- --------------------------------------------------------------------- -- OID for Compliance Statement Software Management -- --------------------------------------------------------------------- noiSWMCompliance OBJECT IDENTIFIER ::= { noiSoftwareManagement 6 }

--====================================================================== -- -- Topmost Object Identifier for Generic Notification Service -- -- ===================================================================== noiNotificationService OBJECT IDENTIFIER ::= { nokiaSnmpInterface 5 }

52DN0933545 Issue 1-0


Id:0900d80580967139

SNMP MIB module

-- --------------------------------------------------------------------- -- OID for Common Variables used within the Generic Notification Service -- --------------------------------------------------------------------- noiGNSVariable OBJECT IDENTIFIER ::= { noiNotificationService 2}

-- --------------------------------------------------------------------- -- OID for Notification in SNMP based Notification Service -- --------------------------------------------------------------------- noiGNSNotificationDef OBJECT IDENTIFIER ::= { noiNotificationService 3 } noiGNSNotification OBJECT IDENTIFIER ::= { noiGNSNotificationDef 0 }

-- --------------------------------------------------------------------- -- OID for Log in SNMP based Notification Service -- --------------------------------------------------------------------- noiGNSLog OBJECT IDENTIFIER ::= { noiNotificationService 4 }

-- --------------------------------------------------------------------- -- OID for Compliance Statement in the Notification Service -- --------------------------------------------------------------------- noiGNSCompliance OBJECT IDENTIFIER ::= { noiNotificationService 5 }

--====================================================================== -- -- Topmost Object Identifier for Hardware Management -- -- OID for Hardware Management branch of the Enhanced SNMP Solution Suite -- ===================================================================== noiHardwareManagement OBJECT IDENTIFIER ::= { nokiaSnmpInterface 6 }

-- --------------------------------------------------------------------- -- OID for Common Variables used within SNMP based Hardware Management -- --------------------------------------------------------------------- noiHWMVariable OBJECT IDENTIFIER ::= { noiHardwareManagement 2}

-- --------------------------------------------------------------------- -- OID for Notification in SNMP based Hardware Management -- --------------------------------------------------------------------- noiHWMNotificationDef OBJECT IDENTIFIER ::= { noiHardwareManagement 3 } noiHWMNotification OBJECT IDENTIFIER ::= { noiHWMNotificationDef 0 }

-- --------------------------------------------------------------------- -- OID for Compliance Statement Software Management -- --------------------------------------------------------------------- noiHWMCompliance OBJECT IDENTIFIER ::= { noiHardwareManagement 6 }

DN0933545 Issue 1-053

NE3S Fault Management SNMP Solution Set References

Id:0900d80580967138

6 References1. NE3S Common Fault Management Concepts2. Nokia OSS, Enhanced SNMP Solution Suite – Object Identifier Version 1.3.13. Textual Conventions for Version 2 of the Simple Network Management Protocol

(SNMPv2), http://www.ietf.org

http://www.ietf.org

54DN0933545 Issue 1-0


Id:0900d80580967137

Glossary

7 Glossary

Term Definition

EM Element manager

NE Network element

NM Network manager, like Nokia Siemens Networks NetAct

NW Network

OS Operations system

RNM Reliable notification mechanism

SNMP Simple Network Management Protocol

TMN Telecommunications management network

Table 3 Terms and definitions

ng_ne3s

Documents

Transcript of ng_ne3s