IPATM-IPMC-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › IPATM-IPMC-MIB

Organization: Internetworking Over NBMA (ion) Working Group

Last Updated: 1998-09-01

Category: ATM, Routing Protocols

Description: Defines managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM networks.

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

What Is IPATM-IPMC-MIB?

IPATM-IPMC-MIB is a vendor-neutral IETF standards MIB (RFC 2022) defining managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to resolve IP multicast group membership over ATM networks, a technique known as 'classical IP multicast over ATM.' It exposes configuration and state data about MARS clients, servers, and the VC/cluster relationships used to map IP multicast groups onto ATM virtual circuits. Its primary monitoring value is software/protocol status rather than physical hardware: whether MARS registration and resolution are functioning correctly, which underpins multicast delivery reliability over the ATM fabric. It is explicitly designed to be used together with the ATM-MIB (RFC 1695), MIB-II (RFC 1213), and optionally the IF-MIB (RFC 1573), so it cannot be interpreted in isolation. Deployment context is legacy ATM backbone networks carrying IP multicast traffic, an environment now largely superseded by IP-native multicast. Engineers can download the IPATM-IPMC-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in IPATM-IPMC-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
  • ATM-attached IP hosts and routers using classical IP multicast

Monitoring Examples

No sample object names were provided in the source extract for this module, so specific table or object identifiers cannot be grounded. Based on the module description, a realistic scenario would involve polling MARS client/server state objects to confirm multicast group-to-VC mappings are current, since a stale or failed MARS resolution would manifest as multicast traffic not reaching all cluster members. Without concrete object names, further detail would be speculative.

Imported Objects

From ATM-TC-MIB

AtmAddr

From IF-MIB

InterfaceIndex

From RFC1213-MIB

ipAdEntAddr
mib-2

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

RowStatus
TruthValue

How to Use in IPNetwork Monitor

Example using marsClientStatTxReqMsgs OID:

Select a device implementing IPATM-IPMC-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 marsClientStatTxReqMsgs 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. It reports the total number of MARS_REQUEST messages transmitted from a client. 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

Classical IP multicast address resolution server (MARS) management for ATM networks, RFC 2417 compliant.

Start monitoring Vendor-neutral IETF standard, RFC 2022 (ATM-attached IP hosts/routers, classical IP multicast) 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 IPATM-IPMC-MIB