PIM-STD-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsPIM-STD-MIB

Organization: IETF Protocol Independent Multicast (PIM) Working Group

Last Updated: 2007-11-02

Category: Routing Protocols

Description: Provides managed objects for PIM protocols (PIM-SM, BIDIR-PIM, and PIM-DM) that work across IP versions, replacing the IPv4-only PIM-MIB.

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

What Is PIM-STD-MIB?

PIM-STD-MIB is a vendor-neutral IETF standards MIB (RFC 5060) defining managed objects for Protocol Independent Multicast routers, covering PIM-SM, BIDIR-PIM, and PIM-DM operation independent of the underlying IP version, superseding the older IPv4-only PIM-MIB. It exposes protocol configuration objects (keepalive period, register suppression time), multicast routing state counters for (*,G), (S,G), and (S,G,RPT) entries per router and per interface, and assert-related counters and interface identifiers. Its monitoring focus is on protocol/software operational health rather than physical hardware: counts like pimSGEntries and pimOutAsserts/pimInAsserts reveal whether multicast routing state is growing abnormally or whether interfaces are engaged in assert contention, and pimNotifications provide traps for significant PIM events. It is designed to be used alongside the IP Multicast MIB and IF-MIB, since PIM entries reference interface indexes and multicast group/source addresses defined in those standards; network engineers reviewing the PIM-STD-MIB MIB commonly cross-reference vendor implementation statements to confirm which of these PIM-SM, BIDIR-PIM, or PIM-DM objects a given router platform actually supports. It is deployed on any IP router running PIM for multicast routing, across enterprise, campus, and service-provider networks.

IPNetwork Monitor allows you to monitor SNMP objects defined in PIM-STD-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; applies to any IP router running PIM multicast routing

Monitoring Examples

An operator would poll pimSGEntries and pimStarGEntries to track the size of the multicast routing table and watch for unexpected growth indicating a misbehaving multicast source or receiver. Monitoring pimOutAsserts and pimInAsserts alongside pimLastAssertInterface reveals interfaces engaged in frequent PIM assert elections, often a sign of a redundant multicast forwarder misconfiguration on a shared LAN segment. A spike in pimSGRptEntries combined with a PIM notification could indicate SPT switchover thrashing in a BIDIR or SM domain.

What Can Be Monitored

  • multicast routing table size (*,G / S,G / S,G,RPT entries)
  • PIM keepalive and register-suppression timers
  • assert event counts (in/out)
  • last assert interface and group address
  • PIM protocol notifications
Imported Objects

From IANA-RTPROTO-MIB

IANAipRouteProtocol

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressPrefixLength
InetAddressType
InetVersion

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32
mib-2

From SNMPv2-TC

RowStatus
StorageType
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using pimNeighborUpTime OID:

Select a device implementing PIM-STD-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 pimNeighborUpTime 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, in TimeTicks, how long this PIM neighbor relationship has been up. 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 TimeTicks-type OID, Value bounds is the most useful condition here — trigger an alert if the uptime resets to a small value unexpectedly, which indicates the PIM adjacency to that neighbor was recently lost and re-established. Click Finish to create the monitor; you can adjust any parameter later.

See also: pimStarGIUpTime, pimStarGUpTime

OIDs

RFC description

Defines managed objects for managing PIM protocols (PIM-SM, BIDIR-PIM, and PIM-DM) independent of IP version, superseding the IPv4-only PIM-MIB.

Start monitoring vendor-neutral, standards-based MIB (PIM-SM/BIDIR-PIM/PIM-DM, RFC 5060) 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 PIM-STD-MIB