MALLOC-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsMALLOC-MIB

Organization: IETF MALLOC Working Group

Last Updated: 2003-06-09

Category: Routing Protocols

Description: Defines managed objects for management and monitoring of Multicast Address Allocation (MALLOC) servers.

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

What Is MALLOC-MIB?

MALLOC-MIB is an IETF standards-track MIB (RFC 3559) for managing Multicast Address Allocation (MALLOC) servers, which implement the MADCAP protocol for dynamically allocating multicast group addresses within administrative scopes. It exposes a scope table describing configured multicast address scopes (address ranges, hop limits, source and server addresses) along with server capability information. This is primarily a configuration/service-status MIB: it lets an operator verify that multicast address scopes are correctly defined and that the allocation server is reachable and serving the expected address ranges, which is important for diagnosing multicast address allocation failures in MADCAP-enabled networks. It is explicitly built on and references the MADCAP protocol standard and general SNMP SMIv2 conventions as its dependency. It is deployed on multicast address allocation servers within enterprise or research networks running dynamic multicast applications. Engineers implementing or auditing this functionality typically reference the MALLOC-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in MALLOC-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
  • multicast address allocation (MADCAP) server

Monitoring Examples

An admin would poll mallocScopeTable/mallocScopeEntry to inspect mallocScopeFirstAddress, mallocScopeLastAddress, and mallocScopeHopLimit for a given scope, confirming the address range and TTL scoping match network policy. If mallocScopeStatus shows a scope as not active despite being expected, or mallocScopeServerAddress points to an unreachable server, that would explain client MADCAP allocation failures. mallocCapabilities would be checked to confirm which allocation features (e.g., mallocScopeDivisible) the server supports.

What Can Be Monitored

  • configured multicast scope address range
  • scope hop limit
  • scope operational status
  • allocation server address
  • scope divisibility capability
Imported Objects

From IANA-MALLOC-MIB

IANAmallocRangeSource
IANAscopeSource

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From IPMROUTE-STD-MIB

LanguageTag

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

RowStatus
StorageType
TruthValue

How to Use in IPNetwork Monitor

Example using madcapTotalErrors OID:

Select a device implementing MALLOC-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 madcapTotalErrors into the Find box to locate it in the OID tree, then select it and click OK. The total number of transactions for which the MADCAP server has detected an error of any type, regardless of whether the server ignored the request or generated a NAK. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Manages multicast address allocation including MADCAP client/server capabilities for IETF multicast address allocation.

Start monitoring Vendor-neutral IETF standard, RFC 3559 (multicast address allocation/MADCAP server) 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 MALLOC-MIB