SNMPv2-M2M-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SNMPv2-M2M-MIB

Organization: IETF SNMPv2 Working Group

Last Updated: 1993-04-01

Category: SNMP Framework

Description: Defines managed objects for manager-to-manager communication, enabling coordination and distribution of network management functions across multiple management stations.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring SNMPv2-M2M-MIB with a free 30-day trial of IPNetwork Monitor.

What Is SNMPv2-M2M-MIB?

SNMPv2-M2M-MIB (the Manager-to-Manager MIB, part of early SNMPv2 framework proposals) defines objects that let one management station configure alarm-style monitoring in coordination with another manager, enabling distribution of network management functions across multiple management stations. It exposes an alarm table modeled closely on the RMON alarm group — sampled variables, sampling intervals, sample type, rising/falling thresholds, and startup behavior. It is used to build generic threshold-based alerting on arbitrary MIB variables coordinated between cooperating managers, effectively a performance/fault monitoring mechanism, rather than exposing hardware sensors directly. It closely parallels and depends conceptually on the RMON alarmTable/eventTable model (RFC 2819) for its alarm semantics. It would be deployed in distributed network management architectures where multiple manager stations share alarm-configuration responsibilities across a large network. Engineers implementing or auditing this functionality typically reference the SNMPv2-M2M-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in SNMPv2-M2M-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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • SNMP-managed network devices and management stations

Monitoring Examples

An admin would configure snmpAlarmTable/snmpAlarmEntry entries, setting snmpAlarmVariable to the OID being watched, snmpAlarmInterval and snmpAlarmSampleType to control sampling, and snmpAlarmRisingThreshold/snmpAlarmFallingThreshold to define alert boundaries; snmpAlarmValue reports the last sampled value. If snmpAlarmValue crosses snmpAlarmRisingThreshold, the associated snmpAlarmRisingEventIndex triggers an event, letting an admin build generic threshold-crossing alerts (e.g., on interface errors or utilization) without vendor-specific tooling.

What Can Be Monitored

  • sampled variable value
  • alarm sampling interval
  • rising/falling threshold crossing
  • startup alarm behavior
  • alarm table entry index
Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-PARTY-MIB

contextIdentityOBJECT-TYPE

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
snmpModules

From SNMPv2-TC

DisplayString
InstancePointer
RowStatus
TimeStamp

How to Use in IPNetwork Monitor

Example using snmpEventEvents OID:

Select a device implementing SNMPv2-M2M-MIB 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 snmpEventEvents into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of events caused by event generators associated with this snmpEvent entry. 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

RFC description

Machine-to-machine (M2M) management extensions for SNMPv2; defines objects for interagent communication and automated monitoring scenarios.

Start monitoring vendor-neutral, standards-based MIB, SNMP-managed network devices and management stations (Manager-to-Manager alarm coordination) 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 SNMPv2-M2M-MIB