SIAE-ALARM-MIB

MIB Reference — IPNetwork Monitor

All MIBsSIAE-ALARM-MIB

Organization: SIAE MICROELETTRONICA spa

Last Updated: 2016-10-04

Category: Microwave Radio - SIAE MICROELETTRONICA

Description:

Manages SIAE MICROELETTRONICA microwave radio alarm definitions, active alarms, and notification state.

Imported Objects

From SIAE-TREE-MIB

siaeMibOBJECT-IDENTITY
siaeMicroelettronicaSpaMODULE-IDENTITY

From SIAE-USER-MIB

accessControlLoginIpAddressOBJECT-TYPE

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION

What Is SIAE-ALARM-MIB?

SIAE-ALARM-MIB is an alarm-management MIB from SIAE MICROELETTRONICA, an Italian microwave radio and transport-equipment vendor, that logs transitions of network-element (NE) alarms and maintains a table of currently active alarms. It exposes fault/alarm-oriented data: an alarm transition log and an active-alarm table reflecting outstanding fault conditions on the equipment. This is fundamentally a hardware/software fault-monitoring MIB rather than one covering interfaces or throughput -- it is the primary mechanism for detecting hardware faults, threshold crossings, and equipment failure conditions on SIAE microwave radios and transport nodes. It likely depends on SIAE's own equipment/system MIBs for the physical entity identifiers each alarm references, and its alarm model plausibly follows ITU-T alarm conventions common in telecom equipment. It is deployed on microwave radio links and transport network elements in telecom backhaul networks using SIAE equipment, and operators reading SIAE-ALARM-MIB SNMP responses rely primarily on the active-alarm table and its associated transition log for real-time fault status.

IPNetwork Monitor allows you to monitor SNMP objects defined in SIAE-ALARM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • active alarm list
  • alarm severity/type
  • alarm raise/clear transition history
  • equipment fault status

Supported Devices

  • SIAE Microelettronica microwave radio and transport equipment, entire product line (active alarm table/transition log)

Monitoring Examples

Based on the module description, an operator would poll the active-alarm table to see currently outstanding conditions -- such as loss of signal, high bit-error rate, or a power-supply fault -- on a SIAE microwave radio link, and consult the alarm log table to review the history of when each alarm was raised and cleared. A new row appearing in the active-alarm table typically flags a hardware degradation event, such as a transceiver or power fault, on the affected link. Because no sample_objects were provided, specific table and column names beyond what module_desc implies cannot be confirmed.

OIDs
OID symbolicOID numericTypeAccessDescription
alarmTrap1.3.6.1.4.1.3373.1103.0
NTF alarmLogFTPStatusTrap1.3.6.1.4.1.3373.1103.0.401This event is generated when the status of FTP transfer is changed. The data passed with the event are: 1) alarmIpSnmpAgentAddress 2) alarmLogFTPStatus 3) accessControlLoginIpAddress
NTF alarmTrapObject1.3.6.1.4.1.3373.1103.0.3373This event is generated for every changed alarm status.
smalarm1.3.6.1.4.1.3373.1103.4Logger of the transitions of NE alarms and active alarm table.
INT alarmMibVersion1.3.6.1.4.1.3373.1103.4.1INTEGERread-onlyNumerical version of this module. The string version of this MIB have the following format: XX.YY.ZZ so, for example, the value 1 should be interpreted as 00.00.01 and the value 10001 should be interpreted as 01.00.01.
siaeNotificationEntry1.3.6.1.4.1.3373.1103.4.2
OID alarmObjectId1.3.6.1.4.1.3373.1103.4.2.1OBJECT IDENTIFIERaccessible-for-notifyOID of the status changed alarm
ALA alarmObjectVal1.3.6.1.4.1.3373.1103.4.2.2AlarmStatusaccessible-for-notifyINTEGER value of the status changed alarm
OCT alarmTrapDescription1.3.6.1.4.1.3373.1103.4.2.3OCTET STRINGaccessible-for-notifyOptional Description of the notification
U32 alarmTrapNumber1.3.6.1.4.1.3373.1103.4.2.4Unsigned32read-onlySequential number of trap sent from NE
IP alarmIpSnmpAgentAddress1.3.6.1.4.1.3373.1103.4.2.5IpAddressaccessible-for-notifyReflects the value of equipIpSnmpAgentAddress.
alarmLogTable1.3.6.1.4.1.3373.1103.4.3not-accessibleTable with Alarm records of the logger.
alarmLogRecord1.3.6.1.4.1.3373.1103.4.3.1not-accessibleAlarm record of the logger.
I32 alarmLogRecordId1.3.6.1.4.1.3373.1103.4.3.1.1Integer32read-onlyThis object is used as Index of alarmLogTable.
OID alarmLogObjectId1.3.6.1.4.1.3373.1103.4.3.1.2OBJECT IDENTIFIERread-onlyThe Object Identifier of the Managed Object with Alarms or Controls active (not cleared Alarm Status).
ALA alarmLogObjectVal1.3.6.1.4.1.3373.1103.4.3.1.3AlarmStatusread-onlyAlarm Status with associated severity.
ALA alarmLogObjectSev1.3.6.1.4.1.3373.1103.4.3.1.4AlarmSeverityCoderead-onlySeverity associated to the Alarm
STR alarmLogDescription1.3.6.1.4.1.3373.1103.4.3.1.5DisplayStringread-onlyASCII string used to describe the event.
U32 alarmLogEventTime1.3.6.1.4.1.3373.1103.4.3.1.6Unsigned32read-onlyThe time (in secs) when the event was registered in the Log since 01-Gen-1970.
INT alarmLogActionRequest1.3.6.1.4.1.3373.1103.4.4INTEGERread-writeThis object is used to delete or to read the LOG using Ftp (file transfer).
STR alarmLogFTPfile1.3.6.1.4.1.3373.1103.4.5DisplayStringread-writePath and file name used when the log is transferred using Ftp (action = read).
I32 alarmLogAlarmSeverityEnable1.3.6.1.4.1.3373.1103.4.6Integer32read-writeThis object enables the event record write in the log according to the severity: Bit0 = Status Bit1 = Warning Bit2 = Minor Bit3 = Major Bit4 = Critical.
INT alarmLogStartHourEnable1.3.6.1.4.1.3373.1103.4.7INTEGERread-writeThis object defines whit AlarmLogEndHourEnable the period during a day when the alarm records must be written in the log.
INT alarmLogEndHourEnable1.3.6.1.4.1.3373.1103.4.8INTEGERread-writeThis object defines whit AlarmLogStartHourEnable the period during a day when the alarm records must be written in the log.
U32 alarmLogStartTimeFilter1.3.6.1.4.1.3373.1103.4.9Unsigned32read-writeThe events with EventTime greater than this object are read/delete from the log. Null value means no filter.
U32 alarmLogEndTimeFilter1.3.6.1.4.1.3373.1103.4.10Unsigned32read-writeThe events with EventTime less than this object are read/delete from the log. Null value means no filter.
OID alarmLogManagedObjectFilter1.3.6.1.4.1.3373.1103.4.11OBJECT IDENTIFIERread-writeThe Object Identifier of the Managed Object that has to be read/delete from the log. Null value means no filter.
I32 alarmLogAlarmSeverityFilter1.3.6.1.4.1.3373.1103.4.12Integer32read-writeThis object defines the alarm severity of the records that must be read/delete from the log. Bit0 = Status Bit1 = Warning Bit2 = Minor Bit3 = Major Bit4 = Critical.
INT alarmLogFTPStatus1.3.6.1.4.1.3373.1103.4.14INTEGERread-onlyStatus of alarm logger Ftp transfer operation.
INT alarmLogFTPStatusTrapNotification1.3.6.1.4.1.3373.1103.4.15INTEGERread-writeEnables/disables the trap generation on FTP tranfer operation.
U32 alarmLogLastEventTime1.3.6.1.4.1.3373.1103.4.16Unsigned32read-onlyIt is the Event time of the last alarm inserted into the alarm log.
alarmActiveTable1.3.6.1.4.1.3373.1103.4.17not-accessibleTable with one record for each Alarms&Controls that is active in the NE.
alarmActiveRecord1.3.6.1.4.1.3373.1103.4.17.1not-accessibleAlarms&Controls record.
OID alarmActiveObjectId1.3.6.1.4.1.3373.1103.4.17.1.1OBJECT IDENTIFIERread-onlyThe Object Identifier of the Managed Object with Alarms or Controls active (not cleared Alarm Status).
ALA alarmActiveObjectVal1.3.6.1.4.1.3373.1103.4.17.1.2AlarmStatusread-onlyAlarm Status with associated severity.
STR alarmActiveDescription1.3.6.1.4.1.3373.1103.4.17.1.3DisplayStringread-onlyASCII string used to describe the event.
U32 alarmActiveEventTime1.3.6.1.4.1.3373.1103.4.17.1.4Unsigned32read-onlyThe time when the Alarm became active. In seconds since 01/01/70.
INT alarmActiveFloodingStatus1.3.6.1.4.1.3373.1103.4.17.1.5INTEGERread-onlyIndicates the 'flooding' status.
INT alarmSyntesysCritical1.3.6.1.4.1.3373.1103.4.18INTEGERread-onlyOR of all Critical Alarms.
INT alarmSyntesysCriticalSeverityCode1.3.6.1.4.1.3373.1103.4.19INTEGERread-writeDefines the severity associated to the alarmSyntesysCritical and enables/disables the trap generation on status change event.
INT alarmSyntesysMajor1.3.6.1.4.1.3373.1103.4.20INTEGERread-onlyOR of all Major Alarms.
INT alarmSyntesysMajorSeverityCode1.3.6.1.4.1.3373.1103.4.21INTEGERread-writeDefines the severity associated to alarmSyntesysMajor and enables/disables the trap generation on status change event.
INT alarmSyntesysMinor1.3.6.1.4.1.3373.1103.4.22INTEGERread-onlyOR of all Minor Alarms.
INT alarmSyntesysMinorSeverityCode1.3.6.1.4.1.3373.1103.4.23INTEGERread-writeDefines the severity associated to alarmSyntesysMinor and enables/disables the trap generation on status change event.
INT alarmSyntesysWarning1.3.6.1.4.1.3373.1103.4.24INTEGERread-onlyOR of all Warning Alarms.
INT alarmSyntesysWarningSeverityCode1.3.6.1.4.1.3373.1103.4.25INTEGERread-writeDefines the severity associated to alarmSyntesysStatus and enables/disables the trap generation on status change event.
INT alarmSyntesysStatus1.3.6.1.4.1.3373.1103.4.26INTEGERread-onlyOR of all Warning Alarms.
INT alarmSyntesysStatusSeverityCode1.3.6.1.4.1.3373.1103.4.27INTEGERread-writeDefines the severity associated to alarmSyntesysStatus and enables/disables the trap generation on status change event.
INT alarmAntiFlooding1.3.6.1.4.1.3373.1103.4.28INTEGERread-writeEnables or disables the alarm anti-flooding (filtering) algorithm. According to such algorithm if the number of event notifications that an alarm receives within a specified time period, namely the observation period, exceeds a given high threshold value, the alarm enters a 'flooding' state. Once an alarm has entered such flooding state, its status is forced to active, according to its related severity, and no further event notifications are processed (neither trapped nor logged). An alarm exits the flooding state when the number of event notifications, received within a subsequent observation period, drops below a given low thresold value. On exiting the flooding state, the trap and log status of an alarm get aligned to the last notified event.
INT alarmAntiFloodingWindow1.3.6.1.4.1.3373.1103.4.29INTEGERread-writeDefines the time duration in seconds of the observation period, during which the number of event notifications of any alarm is checked to determine the alarm flooding state.
INT alarmAntiFloodingHighWater1.3.6.1.4.1.3373.1103.4.30INTEGERread-writeDefines the threshold value of the number of event notifications, occurring during the observation period, beyond which an alarm enters the flooding state.
INT alarmAntiFloodingLowWater1.3.6.1.4.1.3373.1103.4.31INTEGERread-writeDefines the threshold value of the number of event notifications, occurring during the observation period, below which an alarm exits the flooding state. The value being assigned to this leaf must be strictly lower than the current value of leaf alarmAntiFloodingHighWater.
alarmItemTable1.3.6.1.4.1.3373.1103.4.32not-accessibleTable with record of available alarms in the NE. This table reports every created alarm in the NE.
alarmRecord1.3.6.1.4.1.3373.1103.4.32.1not-accessibleAlarm record.
OID alarmOid1.3.6.1.4.1.3373.1103.4.32.1.1OBJECT IDENTIFIERread-onlyThe Object Identifier of the Managed Object with Alarms or Controls active (not cleared Alarm Status).
STR alarmDescription1.3.6.1.4.1.3373.1103.4.32.1.2DisplayStringread-onlyASCII string used to describe the alarm.

FAQ

How does SIAE-ALARM-MIB help detect faults on a SIAE MICROELETTRONICA microwave radio link?
It maintains an active alarm table reflecting all currently outstanding fault conditions on the network element, alongside a log of alarm transitions -- making it the primary mechanism operators use to detect hardware faults and threshold-crossing conditions on SIAE microwave and transport equipment.

What's the difference between the active alarm table and the alarm transition log in SIAE-ALARM-MIB, and how would you use them together?
The active alarm table shows the real-time set of alarms currently outstanding on the equipment, while the transition log records the history of alarms being raised and cleared over time -- useful for diagnosing intermittent or recurring faults that aren't visible from the current-state table alone.

RFC description

SIAE Microelectronics vendor MIB for alarm management and fault reporting in network equipment.

Start monitoring SIAE Microelettronica microwave radio and transport equipment, entire product line (active alarm table/transition log) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SIAE-ALARM-MIB