HORIZON-EQUIPMENT-LOG-MIB

All MIBs › HORIZON-EQUIPMENT-LOG-MIB

Organization: DragonWave Inc.

Last Updated: 2009-01-21

Category: Alarm and Event Management, Domain: Fault Management, Telephony and VoIP

Description: Comverse Horizon equipment log MIB for recording equipment alarm and maintenance events on Horizon telecom systems.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is HORIZON-EQUIPMENT-LOG-MIB?

HORIZON-EQUIPMENT-LOG-MIB is a Comverse Horizon MIB that defines a notification-log mechanism and a current alarm list for equipment in Comverse's Horizon telecom messaging/voicemail platform. It exposes an event log table of variable bindings bounded by an entry limit and a last-entry pointer, alongside a maintained current-alarm list and the SNMP trap definitions raised when new events or alarms occur. This is directly a hardware/software fault and event-monitoring MIB: it lets an operator see exactly which equipment alarms are currently outstanding and review the historical sequence of logged equipment events such as faults, resets, or threshold crossings. It follows the general pattern of SNMP notification-log conventions (in the spirit of NOTIFICATION-LOG-MIB) adapted to Comverse's proprietary alarm model. It is deployed in Comverse Horizon telecom equipment where NOC systems need centralized fault and event tracking. Network engineers evaluating or troubleshooting this functionality can download the HORIZON-EQUIPMENT-LOG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HORIZON-EQUIPMENT-LOG-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.

Supported Devices

DragonWave Horizon-series microwave radio/backhaul equipment

Monitoring Examples

horizonEquipmentEventLogVariableTable holds the variable bindings of each logged event, bounded by horizonEquipmentEventLogEntryLimit and pointed to by horizonEquipmentEventLogLastEntry, which a management station polls to detect newly logged equipment events. horizonEquipmentAlarmList exposes the set of currently active alarms; a NOC dashboard checks this list to confirm whether a hardware alarm remains outstanding after a fault-clearing action. horizonEquipmentSnmpTrap defines the real-time notification sent when a new alarm or event is raised, complementing periodic polling of the log and alarm list.

What Can Be Monitored

current active alarm list
equipment event log entries
event log entry limit and last-entry pointer
real-time alarm/event traps

Imported Objects

From HORIZON-MIB

horizon

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DateAndTime
RowStatus
TEXTUAL-CONVENTION
TimeStamp

How to Use in IPNetwork Monitor

Example using horizonEquipmentAlarmActiveRowCounter OID:

Select a DragonWave Horizon microwave radio (equipment alarm/event log) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type horizonEquipmentAlarmActiveRowCounter into the Find box to locate it in the OID tree, then select it and click OK. The number of active alarms row in the table. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
horizonEquipmentLogMib	1.3.6.1.4.1.7262.2.100			This MIB Module defines a notification log mechanism and a current alarm list.
horizonEquipmentLogMibObjects	1.3.6.1.4.1.7262.2.100.1
horizonEquipmentConfigLog	1.3.6.1.4.1.7262.2.100.1.1
U32 horizonEquipmentEventLogEntryLimit	1.3.6.1.4.1.7262.2.100.1.1.1	Unsigned32	read-only	The maximum number of notification entries that may be held in EventLogTable.
horizonEquipmentLog	1.3.6.1.4.1.7262.2.100.1.2
U32 horizonEquipmentEventLogLastEntry	1.3.6.1.4.1.7262.2.100.1.2.1	Unsigned32	read-only	The value of horizonEquipmentEventLogIndex at the time of the last creation of an entry in the horizonEquipmentEventLogTable.
horizonEquipmentEventLogTable	1.3.6.1.4.1.7262.2.100.1.2.2		not-accessible	A table of Notification log entries.
horizonEquipmentEventLogEntry	1.3.6.1.4.1.7262.2.100.1.2.2.1		not-accessible	A Notification log entry. Entries appear in this table when Notifications occur. They are removed to make way for new entries due to lack of resources or the values of horizonEquipmentEventLogEntryLimit.If adding an entry would exceed horizonEquipmentEventLogEntryLimit the oldest entry in that log SHOULD be removed to make room for the new one.
U32 horizonEquipmentEventLogIndex	1.3.6.1.4.1.7262.2.100.1.2.2.1.1	Unsigned32	not-accessible	A monotonically increasing integer for the sole purpose of indexing entries within the log. When it reaches the maximum value,the agent wraps the value back to 1. This number should correspond to the number of notifications sent by the agent.
TIM horizonEquipmentEventLogTime	1.3.6.1.4.1.7262.2.100.1.2.2.1.2	TimeStamp	read-only	The value of sysUpTime when the entry was placed in the log.
DAT horizonEquipmentEventLogDateAndTime	1.3.6.1.4.1.7262.2.100.1.2.2.1.3	DateAndTime	read-only	The local date and time when the entry was logged, useful when browsing the MIB.
OID horizonEquipmentEventLogNotificationID	1.3.6.1.4.1.7262.2.100.1.2.2.1.4	OBJECT IDENTIFIER	read-only	The NOTIFICATION-TYPE object identifier of the Notification that occurred.
U32 horizonEquipmentEventLogVariables	1.3.6.1.4.1.7262.2.100.1.2.2.1.5	Unsigned32	read-only	The number of variables in horizonEquipmentEventLogVariableTable for this logged notification.
horizonEquipmentEventLogVariableTable	1.3.6.1.4.1.7262.2.100.1.2.3		not-accessible	A table of variables to go with Notification log entries.
horizonEquipmentEventLogVariableEntry	1.3.6.1.4.1.7262.2.100.1.2.3.1		not-accessible	A Notification log entry variable. Entries appear in this table when there are variables in the varbind list of a Notification in horizonEquipmentEventLogTable.
U32 horizonEquipmentEventLogVariableIndex	1.3.6.1.4.1.7262.2.100.1.2.3.1.1	Unsigned32	not-accessible	A monotonically increasing integer, starting at 1 for a given horizonEquipmentEventLogIndex, for indexing variables within the logged Event Notification.
OID horizonEquipmentEventLogVariableID	1.3.6.1.4.1.7262.2.100.1.2.3.1.2	OBJECT IDENTIFIER	read-only	The variable's object identifier.
INT horizonEquipmentEventLogVariableValueType	1.3.6.1.4.1.7262.2.100.1.2.3.1.3	INTEGER	read-only	The type of the value. One and only one of the value objects that follow must be instantiated, based on this type.
C32 horizonEquipmentEventLogVariableCounter32Val	1.3.6.1.4.1.7262.2.100.1.2.3.1.4	Counter32	read-only	The value when horizonEquipmentEventLogVariableValueType is 'counter32'.
U32 horizonEquipmentEventLogVariableUnsigned32Val	1.3.6.1.4.1.7262.2.100.1.2.3.1.5	Unsigned32	read-only	The value when horizonEquipmentEventLogVariableValueType is 'unsigned32'.
TIK horizonEquipmentEventLogVariableTimeTicksVal	1.3.6.1.4.1.7262.2.100.1.2.3.1.6	TimeTicks	read-only	The value when horizonEquipmentEventLogVariableValueType is 'timeTicks'.
I32 horizonEquipmentEventLogVariableInteger32Val	1.3.6.1.4.1.7262.2.100.1.2.3.1.7	Integer32	read-only	The value when horizonEquipmentEventLogVariableValueType is 'integer32'.
OCT horizonEquipmentEventLogVariableOctetStringVal	1.3.6.1.4.1.7262.2.100.1.2.3.1.8	OCTET STRING	read-only	The value when horizonEquipmentEventLogVariableValueType is 'octetString'.
IP horizonEquipmentEventLogVariableIpAddressVal	1.3.6.1.4.1.7262.2.100.1.2.3.1.9	IpAddress	read-only	The value when horizonEquipmentEventLogVariableValueType is 'ipAddress'. Although this seems to be unfriendly for IPv6, we have to recognize that there are a number of older MIBs that do contain an IPv4 format address, known as IpAddress. IPv6 addresses are represented using TAddress or InetAddress, and so the underlying datatype is OCTET STRING, and their value would be stored in the horizonEquipmentEventLogVariableOctetStringVal column.
OID horizonEquipmentEventLogVariableOidVal	1.3.6.1.4.1.7262.2.100.1.2.3.1.10	OBJECT IDENTIFIER	read-only	The value when horizonEquipmentEventLogVariableValueType is 'objectId'.
C64 horizonEquipmentEventLogVariableCounter64Val	1.3.6.1.4.1.7262.2.100.1.2.3.1.11	Counter64	read-only	The value when horizonEquipmentEventLogVariableValueType is 'counter64'.
horizonEquipmentAlarmList	1.3.6.1.4.1.7262.2.100.1.3
TIK horizonEquipmentAlarmActiveLastChanged	1.3.6.1.4.1.7262.2.100.1.3.1	TimeTicks	read-only	The value of sysUpTime at the time of the last creation or deletion of an entry in the horizonEquipmentAlarmActiveTable. Useful in case of polling (no traps mechanism used). If the number of entries has been unchanged since the last re-initialization, then this object contains a zero value.
C32 horizonEquipmentAlarmActiveRowCounterEx	1.3.6.1.4.1.7262.2.100.1.3.2	Counter32	read-only	The number of active alarms row in the table.
horizonEquipmentAlarmActiveTable	1.3.6.1.4.1.7262.2.100.1.3.3		not-accessible	A table of Active Alarms entries.
horizonEquipmentAlarmActiveEntry	1.3.6.1.4.1.7262.2.100.1.3.3.1		not-accessible	Entries appear in this table when alarms are raised. They are removed when the alarm is cleared.
U32 horizonEquipmentAlarmActiveIndex	1.3.6.1.4.1.7262.2.100.1.3.3.1.1	Unsigned32	not-accessible	A strictly monotonically increasing integer which acts as the index of entries within the named alarm list. It wraps back to 1 after it reaches its maximum value.
TIM horizonEquipmentAlarmActiveTime	1.3.6.1.4.1.7262.2.100.1.3.3.1.2	TimeStamp	not-accessible	The value of sysUpTime when the entry was placed in the list. This object facilitates retrieving all instances of alarms that have been raised or have changed state since a given point in time.
DAT horizonEquipmentAlarmActiveDateAndTime	1.3.6.1.4.1.7262.2.100.1.3.3.1.3	DateAndTime	read-only	The local date and time when the error occurred. This object facilitates retrieving all instances of alarms that have been raised or have changed state since a given point in time. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
OID horizonEquipmentAlarmActiveSourceID	1.3.6.1.4.1.7262.2.100.1.3.3.1.4	OBJECT IDENTIFIER	read-only	The MIB object identifier of the alarm (contained in an Alarm Notification type object) that is occurring.
horizonEquipmentSnmpTrap	1.3.6.1.4.1.7262.2.100.1.4
C32 horizonEquipmentOutTrapsCounter	1.3.6.1.4.1.7262.2.100.1.4.1	Counter32	read-only	The counter of the output traps. It increases by one every time a new trap is sent to all the managers configured in the relevant table. In this way its value is the number of notification events occurred since the last agent reset and every manager that reads this value can understand whether some event has been lost or not. (Note that in general this counter differs from the RFC1213 snmpOutTraps, that counts the number of Trap PDUs sent). When the logging mechanism is enabled, it corresponds to the index in the eventlog table
TIM horizonEquipmentLastOutTrapTimeStamp	1.3.6.1.4.1.7262.2.100.1.4.2	TimeStamp	read-only	The value of sysUpTime when the last trap was sent.
horizonEquipmentTrapDestTable	1.3.6.1.4.1.7262.2.100.1.4.4		not-accessible	The trap destination table.
horizonEquipmentTrapDestEntry	1.3.6.1.4.1.7262.2.100.1.4.4.1		not-accessible	An entry in the table. The table is indexed by the Manager IP Address.
IP horizonEquipmentTrapDestAddress	1.3.6.1.4.1.7262.2.100.1.4.4.1.1	IpAddress	not-accessible	Manager IP address. STORAGE: volatile.
OCT horizonEquipmentTrapDestCommString	1.3.6.1.4.1.7262.2.100.1.4.4.1.2	OCTET STRING	read-create	Manager SNMP community string. STORAGE: volatile.
INT horizonEquipmentTrapDestUdpPort	1.3.6.1.4.1.7262.2.100.1.4.4.1.3	INTEGER	read-create	Destination UDP port. Default: 162. STORAGE: volatile.
INT horizonEquipmentTrapDestSnmpVer	1.3.6.1.4.1.7262.2.100.1.4.4.1.4	INTEGER	read-create	SMI version supported by the manager. STORAGE: volatile.
TIK horizonEquipmentTrapDestEraseTime	1.3.6.1.4.1.7262.2.100.1.4.4.1.5	TimeTicks	read-create	The time (in hundredths of a second) after which the relevant row in horizonEquipmentTrapDestTable is erased. 1440000 (i.e. 4 hours) is the maximum value for this parameter. STORAGE: volatile.
ROW horizonEquipmentTrapDestRowStatus	1.3.6.1.4.1.7262.2.100.1.4.4.1.6	RowStatus	read-create	The row status variable, used according to row creation and removal conventions.
horizonEquipmentPseudoEventsObjects	1.3.6.1.4.1.7262.2.100.2
OID horizonEquipmentConfChangeOid	1.3.6.1.4.1.7262.2.100.2.1	OBJECT IDENTIFIER	read-only	The OID of the last node changed. It is sent to the managers in order to notify a configuration change.
ENA horizonEquipmentConfChangeMode	1.3.6.1.4.1.7262.2.100.2.3	EnableType	read-write	Enable/Disable of sending ConfChange Trap. STORAGE: permanent.
NTF horizonEquipmentConfChangeNotification	1.3.6.1.4.1.7262.2.100.2.4			Notification of configuration change.
horizonEquipmentMirrorObjects	1.3.6.1.4.1.7262.2.100.3
INT horizonEquipmentMirrorFlag	1.3.6.1.4.1.7262.2.100.3.1	INTEGER	read-only	Fixed to 1=mirror trap
NTF horizonEquipmentMirrorColdStart	1.3.6.1.4.1.7262.2.100.3.2			A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.

RFC description

DragonWave Horizon equipment notification logging and alarm list management for wireless network devices.

Start monitoring DragonWave Horizon microwave radio (equipment alarm/event 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 HORIZON-EQUIPMENT-LOG-MIB