Hitachi Energy
ALARM MIB (RFC 3877)
The snmpnetworkagentmgrd will read the following tables from the device: alarm model table (.1.3.6.1.2.1.118.1.1.2), alarm active table (.1.3.6.1.2.1.118.1.2.2) and ITU alarm table (.1.3.6.1.2.1.121.1.1.1).The alarm clear table (.1.3.6.1.2.1.118.1.3.2) is not used. In addition, it will need references to the entity physical table to fill out FOXMAN-UN alarm record fields (e.g. location). The agent manager will interpret the following ALARM MIB traps: alarmActiveState (.1.3.6.1.2.1.118.0.2) and alarmClearState (.1.3.6.1.2.1.118.0.3). The complete table is read on NE creation, re-establishment of connection and force polling, above traps are being interpreted in between.
* 
Please note: 
The ARC MIB (RFC 3878) is not supported.
The following columns from the various tables are used in FOXMAN-UN:
 
Use of ALARM MIB table columns in FOXMAN-UN alarm records
SNMP ALARM MIB table
table column
FOXMAN-UN alarm record field
AlarmActiveTable
alarmResourceId
Address / SBU-Address / TP-Address / Location (mapped from entPhysicalTable analysis)
AlarmActiveTable
alarmActiveDateAndTime
AlarmOnTime
AlarmActiveTable
alarmActiveSpecificPointer
<Pointer into AlarmModelTable>
 
AlarmModelTable
alarmModelState
Severity
(only applied if ITUAlarmTable row is not available)
AlarmModelTable
alarmModelDescription
AlarmText
AlarmModelTable
alarmModelSpecificPointer
<Pointer into ITUAlarmTable>
 
ITUAlarmTable
ituAlarmPerceivedSeverity
Severity
(if ITUAlarmTable is not available alarmModelState will be taken)
ITUAlarmTable
ituAlarmEventType
Type
(if ITUAlarmModel is not available it need to be provided by a config file)
ITUAlarmTable
ituAlarmProbableCause
Cause
(if ITUAlarmModel is not available it need to be provided by a config file)
 
Other sources for content in FOXMAN-UN alarms records
FOXMAN-UN alarm record field
Source
AlarmId
From DB (NetworkMgr - Unique per NE)
NEId
From DB (SNMP Agent)
NEType
From DB (SNMP Agent)
LayerRate
Always set to “unknown”
AlarmOffTime
1. Time of AlarmClearState notification
2. Time of alarm resync detecting alarm being off
FailureId
A short string like “LOSS” instead of a longer text - provided by a configuration file
IsCleared
True if
1. Alarm is generated because of
AlarmClearState notification
2. Alarm resync detected alarm being off
IsTrafficAffected
Provided by a configuration file
 
Contents of AlarmActiveState and AlarmClearState notifications
Name
Contents
alarmActiveModelPointer
OID to the corresponding row in the alarmModelTable for this active alarm. This point not only to the alarm model being instantiated, but also to the specific alarm state that is active.
alarmActiveResourceId
OID identifying the resource under alarm.
For the FOXMAN-UN alarm configuration to work, a plain text file specifying the severity, alarm/event type and probable cause texts in the form of
...
critical equipment Unit Not Available major communication BER > 1E-3
...
must be provided. A more complete example can be provided on request.