NOKIA-ENHANCED-SNMP-SOLUTION-SUITE-COMMON-DEFINITION

File: NOKIA-ENHANCED-SNMP-SOLUTION-SUITE-COMMON-DEFINITION.mib (29249 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC NOKIA-NE3S-REGISTRATION-MIB

Imported symbols

Integer32 MODULE-IDENTITY DisplayString
DateAndTime TEXTUAL-CONVENTION noiOpenInterfaceModule

Defined Types

NoiAcknowledgementState  
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
TEXTUAL-CONVENTION    
  INTEGER acknowledged(1), unacknowledged(2), indeterminate(3)  

NoiAcknowledgementTime  
The acknowledgement time is used to set the last time when the acknowledgement state of an alarm in the alarm table has been changed.
TEXTUAL-CONVENTION    
  DateAndTime  

NoiAcknowledgementUserId  
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
TEXTUAL-CONVENTION    
  DisplayString Size(0..10)  

NoiAdditionalText  
The additional text is used to pass additional information on the fault causing the alarm in the Network Element in human readable format. It shall be used to convey 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). Nokia recommend to use the additional text in alarm and changed alarm notification. An empty string shall be used only within clear alarm notification.
TEXTUAL-CONVENTION    
  DisplayString Size(0..64)  

NoiAlarmId  
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.
TEXTUAL-CONVENTION    
  Integer32 1..2147483647  

NoiAlarmLogControl  
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 normal operation of the log flush indicate a request to empty the current content of the log. Suspend indicate a request to suspended logging
TEXTUAL-CONVENTION    
  INTEGER logging(1), flush(2), suspend(3)  

NoiAlarmLogCount  
Contains the number of currently active alarms in the alarm Log.
TEXTUAL-CONVENTION    
  Integer32 0..2147483647  

NoiAlarmTableCount  
Contains the number of currently active alarms in the alarm Table.
TEXTUAL-CONVENTION    
  Integer32 0..2147483647  

NoiAlarmText  
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.
TEXTUAL-CONVENTION    
  DisplayString Size(0..64)  

NoiEventTime  
Time when the event has occurred
TEXTUAL-CONVENTION    
  DateAndTime  

NoiEventType  
Event type as specified in ITU recommendations X.733. The value unknown (0) shall not be used.
TEXTUAL-CONVENTION    
  INTEGER unknown(0), communicationsAlarm(2), environmentalAlarm(3), equipmentAlarm(4), processingErrorAlarm(10), qualityOfServiceAlarm(11)  

NoiLogFullAction  
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
TEXTUAL-CONVENTION    
  INTEGER wrap(0), halt(1)  

NoiNotificationId  
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 fault management related notification (alarm -, clear alarm notification, severity changed - or acknowledgement notification) emitted by the agent shall have, at any given time, different notification identifier Within the context of this specification the assumption is that the agent assures in any case a consecutive sequence of the notification identifier (e.g. after NE restart, restart of the agent or under similar conditions) 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). Within the scope of this interface the notification identifier of an alarm notification can have the same value as the alarm identifier.
TEXTUAL-CONVENTION    
  Integer32 1..2147483647  

NoiNotificationType  
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}
TEXTUAL-CONVENTION    
  INTEGER noiAlarmNew(1), noiAlarmCleared(2), noiAlarmListRebuild(3), noiAlarmListRebuildInitiated(4), noiAlarmChanged(5), noiAlarmAckStateChanged(6)  

NoiPerceivedSeverity  
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.
TEXTUAL-CONVENTION    
  INTEGER critical(1), major(2), minor(3), warning(4), cleared(5), indeterminate(0)  

NoiProbableCause  
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 in ITU-T recommendations M.3100, X.733, X.736, ETSI technical specification GSM 12.11 and for UMTS, in Alarm IRP. The agent shall assign the value m3100Indeterminate to indicate that the ProbableCause is not used.
TEXTUAL-CONVENTION    
  INTEGER m3100Indeterminate(0), m3100AlarmIndicationSignal(1), m3100CallSetupFailure(2), m3100DegradedSignal(3), m3100FarEndReceiverFailure(4), m3100FramingError(5), m3100LossOfFrame(6), m3100LossOfPointer(7), m3100LossOfSignal(8), m3100PayloadTypeMismatch(9), m3100TransmissionError(10), m3100RemoteAlarmInterface(11), m3100ExcessiveBitErrorRate(12), m3100PathTraceMismatch(13), m3100Unavailable(14), m3100SignalLabelMismatch(15), m3100LossOfMultiFrame(16), m3100BackPlaneFailure(51), m3100DataSetProblem(52), m3100EquipmentIdentifierDuplication(53), m3100ExternalIfDeviceProblem(54), m3100LineCardProblem(55), m3100MultiplexerProblem(56), m3100NeIdentifierDuplication(57), m3100PowerProblem(58), m3100ProcessorProblem(59), m3100ProtectionPathFailure(60), m3100ReceiverFailure(61), m3100ReplaceableUnitMissing(62), m3100ReplaceableUnitTypeMismatch(63), m3100SynchronisationSourceMismatch(64), m3100TerminalProblem(65), m3100TimingProblem(66), m3100TransmitterFailure(67), m3100TrunkCardProblem(68), m3100ReplaceableUnitProblem(69), m3100AirCompressorFailure(101), m3100AirConditioningFailure(102), m3100AirDryerFailure(103), m3100BatteryDischarging(104), m3100BatteryFailure(105), m3100CommercialPowerFailure(106), m3100CoolingFanFailure(107), m3100EngineFailure(108), m3100FireDetectorFailure(109), m3100FuseFailure(110), m3100GeneratorFailure(111), m3100LowBatteryThreshold(112), m3100PumpFailure(113), m3100RectifierFailure(114), m3100RectifierHighVoltage(115), m3100RectifierLowVoltage(116), m3100VentilationSystemFailure(117), m3100EnclosureDoorOpen(118), m3100ExplosiveGas(119), m3100Fire(120), m3100Flood(121), m3100HighHumidity(122), m3100HighTemperature(123), m3100HighWind(124), m3100IceBuildUp(125), m3100LowFuel(127), m3100LowHumidity(128), m3100LowCablePressure(129), m3100LowTemperature(130), m3100LowWater(131), m3100Smoke(132), m3100ToxicGas(133), m3100StorageCapacityProblem(151), m3100MemoryMismatch(152), m3100CorruptData(153), m3100OutOfCPUCycles(154), m3100SoftwareEnvironmentProblem(155), m3100SoftwareDownloadFailure(156), x733AdapterError(1000001), x733ApplicationSubsystemFailure(1000002), x733BandwidthReduced(1000003), x733CommunicationsProtocolError(1000005), x733CommunicationsSubsystemFailure(1000006), x733ConfigurationOrCustomizationError(1000007), x733Congestion(1000008), x733CpuCyclesLimitExceeded(1000010), x733DataSetOrModemError(1000011), x733DTEDCEInterfaceError(1000013), x733EquipmentMalfunction(1000015), x733ExcessiveVibration(1000016), x733FileError(1000017), x733HeatingOrVentilationOrCoolingSystemProblem(1000021), x733HumidityUnacceptable(1000022), x733InputOutputDeviceError(1000023), x733InputDeviceError(1000024), x733LANError(1000025), x733LeakDetected(1000026), x733LocalNodeTransmissionError(1000027), x733MaterialSupplyExhausted(1000030), x733OutOfMemory(1000032), x733OuputDeviceError(1000033), x733PerformanceDegraded(1000034), x733PressureUnacceptable(1000036), x733QueueSizeExceeded(1000039), x733ReceiveFailure(1000040), x733RemoteNodeTransmissionError(1000042), x733ResourceAtOrNearingCapacity(1000043), x733ResponseTimeExcessive(1000044), x733RetransmissionRateExcessive(1000045), x733SoftwareError(1000046), x733SoftwareProgramAbnormallyTerminated(1000047), x733SoftwareProgramError(1000048), x733TemperatureUnacceptable(1000050), x733ThresholdCrossed(1000051), x733ToxicLeakDetected(1000053), x733TransmitFailure(1000054), x733UnderlyingResourceUnavailable(1000056), x733VersionMismatch(1000057), x736AuthenticationFailure(2000001), x736BreachOfConfidentiality(2000002), x736CableTamper(2000003), x736DelayedInformation(2000004), x736DenialOfService(2000005), x736DuplicateInformation(2000006), x736InformationMissing(2000007), x736InformationModificationDetected(2000008), x736InformationOutOfSequence(2000009), x736IntrusionDetection(2000010), x736KeyExpired(2000011), x736NonRepudiationFailure(2000012), x736OutOfHoursActivity(2000013), x736OutOfService(2000014), x736ProceduralError(2000015), x736UnauthorizedAccessAttempt(2000016), x736UnexpectedInformation(2000017), x736UnspecifiedReason(2000018), gsm1211AbisToBTSInterfaceFailure(3000001), gsm1211AbisToTRXInterfaceFailure(3000002), gsm1211AntennaProblem(3000003), gsm1211BatteryBreakdown(3000004), gsm1211BatteryChargingFault(3000005), gsm1211ClockSynchronisationProblem(30000056), gsm1211CombinerProblem(3000007), gsm1211DiskProblem(3000008), gsm1211ExcessiveReceiverTemperature(3000010), gsm1211ExcessiveTransmitterOutputPower(3000011), gsm1211ExcessiveTransmitterTemperature(3000012), gsm1211FrequencyHoppingDegraded(3000013), gsm1211FrequencyHoppingFailure(3000014), gsm1211FrequencyRedefinitionFailed(3000015), gsm1211LineInterfaceFailure(3000016), gsm1211LinkFailure(3000017), gsm1211LossOfSynchronisation(3000018), gsm1211LostRedundancy(3000019), gsm1211MainsBreakdownWithBatteryBackUp(3000020), gsm1211MainsBreakdownWithoutBatteryBackUp(3000021), gsm1211PowerSupplyFailure(3000022), gsm1211ReceiverAntennaFault(3000023), gsm1211ReceiverMulticouplerFailure(3000025), gsm1211ReducedTransmitterOutputPower(3000026), gsm1211SignalQualityEvaluationFault(3000027), gsm1211TimeslotHardwareFailure(3000028), gsm1211TransceiverProblem(3000029), gsm1211TranscoderProblem(3000030), gsm1211TranscoderOrRateAdapterProblem(3000031), gsm1211TransmitterAntennaFailure(3000032), gsm1211TransmitterAntennaNotAdjusted(3000033), gsm1211TransmitterLowVoltageOrCurrent(3000035), gsm1211TransmitterOffFrequency(3000036), gsm1211DatabaseInconsistency(3000037), gsm1211FileSystemCallUnsuccessful(3000038), gsm1211InputParameterOutOfRange(3000039), gsm1211InvalidParameter(3000040), gsm1211InvalidPointer(3000041), gsm1211MessageNotExpected(3000042), gsm1211MessageNotInitialised(3000043), gsm1211MessageOutOfSequence(3000044), gsm1211SystemCallUnsuccessful(3000045), gsm1211TimeoutExpired(3000046), gsm1211VariableOutOfRange(3000047), gsm1211WatchDogTimerExpired(3000048), gsm1211CoolingSystemFailure(3000049), gsm1211ExternalEquipmentFailure(3000050), gsm1211ExternalPowerSupplyFailure(3000051), gsm1211ExternalTransmissionDeviceFailure(3000052), gsm1211ReducedAlarmReporting(3000061), gsm1211ReducedEventReporting(3000062), gsm1211ReducedLoggingCapability(3000063), gsm1211SystemResourcesOverload(3000064), gsm1211BroadcastChannelFailure(3000065), gsm1211ConnectionEstablishmentError(3000066), gsm1211InvalidMessageReceived(3000067), gsm1211InvalidMSUReceived(3000068), gsm1211LAPDLinkProtocolFailure(3000069), gsm1211LocalAlarmIndication(3000070), gsm1211RemoteAlarmIndication(3000071), gsm1211RoutingFailure(3000072), gsm1211SS7ProtocolFailure(3000073), gsm1211TransmissionError(3000074)  

NoiSpecificProblem  
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.
TEXTUAL-CONVENTION    
  Integer32 1..99999  

NoiSystemDistinguishedName  
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-1/LNK-1
TEXTUAL-CONVENTION    
  DisplayString Size(0..160)  

Defined Values

noiSnmpAlarmIrpCommon 1.3.6.1.4.1.94.7.1.1.1
The definition of common parameters used for Nokia SNMP Solution Set of the 3GPP Alarm IRP also known as NE3S Interface.
MODULE-IDENTITY