EQUIPMENT-COMMON-MIB

All MIBs › EQUIPMENT-COMMON-MIB

Organization: DragonWave Inc.

Last Updated: 2009-01-21

Category: Alarm and Event Management, Hardware and Environment, Vendor: DragonWave

Description: DragonWave Inc. equipment common MIB providing alarm notification log and active alarm list management objects.

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 EQUIPMENT-COMMON-MIB?

EQUIPMENT-COMMON-MIB is a DragonWave Inc. proprietary MIB (DragonWave makes microwave/wireless backhaul radio equipment) defining a common notification-log mechanism and active-alarm list used across DragonWave's equipment line. It exposes an event log table with per-entry index, timestamp (both elapsed and date/time forms), notification ID, and a variable-binding sub-table capturing the alarm's associated data. Its core monitoring purpose is fault/alarm status: tracking configuration changes and active alarms/faults on the radio equipment, including a log-entry limit and pointer to the last entry, so operators can retrieve recent fault history even between polling cycles. No explicit dependency on another standard MIB is stated, though it follows a common alarm-log pattern seen in other vendor fault-management MIBs. It is deployed on DragonWave microwave backhaul radios and related transport equipment in telecom/wireless-backhaul networks. Network engineers evaluating or troubleshooting this functionality can download the EQUIPMENT-COMMON-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in EQUIPMENT-COMMON-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 microwave backhaul radio equipment

Monitoring Examples

An operator would poll equipmentEventLogLastEntry and walk equipmentEventLogTable/equipmentEventLogEntry back from it to retrieve recent equipmentEventLogNotificationID events and their equipmentEventLogDateAndTime, revealing a recent fault or configuration change on the radio link. Correlating equipmentEventLogVariableTable/equipmentEventLogVariableEntry entries against a given equipmentEventLogIndex provides the specific variable bindings (e.g., affected interface or threshold value) tied to that alarm. equipmentEventLogEntryLimit indicates how much history is retained, which matters when planning polling frequency to avoid missing events.

What Can Be Monitored

active alarm/event log entries
event timestamp and notification ID
event log capacity/limit
variable bindings associated with each logged event
configuration change log

Imported Objects

From DWI-HARMONY-PRIVATE-MIB

equipmentCommon

OBJECT-IDENTITY

From SNMPv2-SMI

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

From SNMPv2-TC

DateAndTime
DisplayString
TEXTUAL-CONVENTION
TimeStamp

How to Use in IPNetwork Monitor

Example using equipmentAlarmActiveRowCounter OID:

Select a DragonWave microwave backhaul radio equipment (event log/active alarms) 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 equipmentAlarmActiveRowCounter 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
equipmentCommonObjects	1.3.6.1.4.1.7262.20.1
equipmentConfigLog	1.3.6.1.4.1.7262.20.1.1
U32 equipmentEventLogEntryLimit	1.3.6.1.4.1.7262.20.1.1.1	Unsigned32	read-only	The maximum number of notification entries that may be held in EventLogTable.
equipmentLog	1.3.6.1.4.1.7262.20.1.2
U32 equipmentEventLogLastEntry	1.3.6.1.4.1.7262.20.1.2.1	Unsigned32	read-only	The value of equipmentEventLogIndex at the time of the last creation of an entry in the equipmentEventLogTable.
equipmentEventLogTable	1.3.6.1.4.1.7262.20.1.2.2		not-accessible	A table of Notification log entries.
equipmentEventLogEntry	1.3.6.1.4.1.7262.20.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 equipmentEventLogEntryLimit.If adding an entry would exceed equipmentEventLogEntryLimit the oldest entry in that log SHOULD be removed to make room for the new one.
U32 equipmentEventLogIndex	1.3.6.1.4.1.7262.20.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 equipmentEventLogTime	1.3.6.1.4.1.7262.20.1.2.2.1.2	TimeStamp	read-only	The value of sysUpTime when the entry was placed in the log.
DAT equipmentEventLogDateAndTime	1.3.6.1.4.1.7262.20.1.2.2.1.3	DateAndTime	read-only	The local date and time when the entry was logged, useful when browsing the MIB.
OID equipmentEventLogNotificationID	1.3.6.1.4.1.7262.20.1.2.2.1.4	OBJECT IDENTIFIER	read-only	The NOTIFICATION-TYPE object identifier of the Notification that occurred.
U32 equipmentEventLogVariables	1.3.6.1.4.1.7262.20.1.2.2.1.5	Unsigned32	read-only	The number of variables in equipmentEventLogVariableTable for this logged notification.
equipmentEventLogVariableTable	1.3.6.1.4.1.7262.20.1.2.3		not-accessible	A table of variables to go with Notification log entries.
equipmentEventLogVariableEntry	1.3.6.1.4.1.7262.20.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 equipmentEventLogTable.
U32 equipmentEventLogVariableIndex	1.3.6.1.4.1.7262.20.1.2.3.1.1	Unsigned32	not-accessible	A monotonically increasing integer, starting at 1 for a given equipmentEventLogIndex, for indexing variables within the logged Event Notification.
OID equipmentEventLogVariableID	1.3.6.1.4.1.7262.20.1.2.3.1.2	OBJECT IDENTIFIER	read-only	The variable's object identifier.
INT equipmentEventLogVariableValueType	1.3.6.1.4.1.7262.20.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 equipmentEventLogVariableCounter32Val	1.3.6.1.4.1.7262.20.1.2.3.1.4	Counter32	read-only	The value when equipmentEventLogVariableValueType is 'counter32'.
U32 equipmentEventLogVariableUnsigned32Val	1.3.6.1.4.1.7262.20.1.2.3.1.5	Unsigned32	read-only	The value when equipmentEventLogVariableValueType is 'unsigned32'.
TIK equipmentEventLogVariableTimeTicksVal	1.3.6.1.4.1.7262.20.1.2.3.1.6	TimeTicks	read-only	The value when equipmentEventLogVariableValueType is 'timeTicks'.
I32 equipmentEventLogVariableInteger32Val	1.3.6.1.4.1.7262.20.1.2.3.1.7	Integer32	read-only	The value when equipmentEventLogVariableValueType is 'integer32'.
OCT equipmentEventLogVariableOctetStringVal	1.3.6.1.4.1.7262.20.1.2.3.1.8	OCTET STRING	read-only	The value when equipmentEventLogVariableValueType is 'octetString'.
IP equipmentEventLogVariableIpAddressVal	1.3.6.1.4.1.7262.20.1.2.3.1.9	IpAddress	read-only	The value when equipmentEventLogVariableValueType 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 equipmentEventLogVariableOctetStringVal column.
OID equipmentEventLogVariableOidVal	1.3.6.1.4.1.7262.20.1.2.3.1.10	OBJECT IDENTIFIER	read-only	The value when equipmentEventLogVariableValueType is 'objectId'.
C64 equipmentEventLogVariableCounter64Val	1.3.6.1.4.1.7262.20.1.2.3.1.11	Counter64	read-only	The value when equipmentEventLogVariableValueType is 'counter64'.
equipmentAlarmList	1.3.6.1.4.1.7262.20.1.3
TIK equipmentAlarmActiveLastChanged	1.3.6.1.4.1.7262.20.1.3.1	TimeTicks	read-only	The value of sysUpTime at the time of the last creation or deletion of an entry in the equipmentAlarmActiveTable. 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 equipmentAlarmActiveRowCounterEx	1.3.6.1.4.1.7262.20.1.3.2	Counter32	read-only	The number of active alarms row in the table.
equipmentAlarmActiveTable	1.3.6.1.4.1.7262.20.1.3.3		not-accessible	A table of Active Alarms entries.
equipmentAlarmActiveEntry	1.3.6.1.4.1.7262.20.1.3.3.1		not-accessible	Entries appear in this table when alarms are raised. They are removed when the alarm is cleared.
U32 equipmentAlarmActiveIndex	1.3.6.1.4.1.7262.20.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 equipmentAlarmActiveTime	1.3.6.1.4.1.7262.20.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 equipmentAlarmActiveDateAndTime	1.3.6.1.4.1.7262.20.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.
STR equipmentAlarmActiveName	1.3.6.1.4.1.7262.20.1.3.3.1.4	DisplayString	read-only	This object indicates the active alarm name.
I32 equipmentAlarmActiveID	1.3.6.1.4.1.7262.20.1.3.3.1.5	Integer32	read-only	This object indicates the active alarm ID which is the index to the alarm configuration table defined in product specific MIB.
U32 equipmentAlarmActiveInstance	1.3.6.1.4.1.7262.20.1.3.3.1.6	Unsigned32	read-only
OID equipmentAlarmActiveTrapOID	1.3.6.1.4.1.7262.20.1.3.3.1.7	OBJECT IDENTIFIER	read-only	The MIB object identifier of the alarm (contained in an Alarm Notification type object) that is occurring.
INT equipmentAlarmActiveSeverity	1.3.6.1.4.1.7262.20.1.3.3.1.8	INTEGER	read-only	This object indicates the active alarm severity.
STR equipmentAlarmActiveConditionId	1.3.6.1.4.1.7262.20.1.3.3.1.9	DisplayString	read-only
equipmentSnmpTrap	1.3.6.1.4.1.7262.20.1.4
C32 equipmentOutTrapsCounter	1.3.6.1.4.1.7262.20.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 equipmentLastOutTrapTimeStamp	1.3.6.1.4.1.7262.20.1.4.2	TimeStamp	read-only	The value of sysUpTime when the last trap was sent.
STR equipmentTrapInfo	1.3.6.1.4.1.7262.20.1.4.3	DisplayString	read-only	A string representing additional info that can be used as the varbind in trap.
equipmentPseudoEventsObjects	1.3.6.1.4.1.7262.20.2
OID equipmentConfChangeOid	1.3.6.1.4.1.7262.20.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 equipmentConfChangeMode	1.3.6.1.4.1.7262.20.2.2	EnableType	read-write	Enable/Disable of sending ConfChange Trap. STORAGE: permanent.
NTF equipmentConfChangeNotification	1.3.6.1.4.1.7262.20.2.3			Notification of configuration change.
equipmentMirrorObjects	1.3.6.1.4.1.7262.20.3
I32 equipmentMirrorFlag	1.3.6.1.4.1.7262.20.3.1	Integer32	read-only	Fixed to 1=mirror trap
NTF equipmentMirrorColdStart	1.3.6.1.4.1.7262.20.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.
equipmentCommonMib	1.3.6.1.4.1.7262.20.100			This MIB Module defines a notification log mechanism and a current alarm list.

RFC description

Common equipment management MIB defining generic objects for monitoring physical equipment, chassis, modules, and power supplies across network devices.

Start monitoring DragonWave microwave backhaul radio equipment (event log/active alarms) 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 EQUIPMENT-COMMON-MIB