All MIBs › AT-PIM-MIB
Organization: Allied Telesis, Inc
Last Updated: 2005-01-20
Category: Routing Protocols, Vendor: Allied Telesis
Description: Manages Protocol Independent Multicast (PIM) interface configuration, neighbor adjacencies, and multicast routing on Allied Telesis devices.
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 AT-PIM-MIB?
AT-PIM-MIB is an Allied Telesis enterprise module covering PIM (Protocol Independent Multicast, PIMv4) support on AT switches, handling multicast routing interface configuration and neighbor adjacency state. It exposes configuration-style data (PIM-enabled interfaces, multicast routing parameters) alongside fault/event objects such as pim4ErrorTrapType and the pim4Events trap group. For monitoring purposes it is primarily used to catch multicast routing faults and adjacency problems -- a PIM error trap can reveal misconfigured RP mappings, neighbor timeouts, or protocol errors that would otherwise silently degrade multicast delivery. It naturally depends on and complements the standard IP Multicast MIB (IGMP/PIM-STD-MIB) concepts and the underlying IF-MIB interface table for identifying affected interfaces. It is deployed on AT Layer 3 switches used in networks that carry IPTV, video conferencing, or other multicast traffic. Engineers can download the AT-PIM-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in AT-PIM-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
- Allied Telesis Layer 3 switches
Monitoring Examples
An operator would subscribe to pim4Events traps and inspect the pim4ErrorTrapType value to classify the nature of a PIM fault (such as a neighbor loss or hello timeout) on a given routed interface. A spike in PIM error traps on a core switch would flag a multicast routing instability that could be starving downstream multicast receivers of traffic. Polling would typically be paired with interface and neighbor-adjacency status to pinpoint which link is affected.
What Can Be Monitored
- PIM error trap type
- PIM event occurrences
- multicast neighbor adjacency faults
Imported Objects
From AT-SMI-MIB
| modules | OBJECT-IDENTITY |
From PIM-MIB
| pimInterfaceStatus | OBJECT-TYPE |
| pimNeighborIfIndex | OBJECT-TYPE |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString |
OIDs
RFC description
Allied Telesis vendor-private MIB for Protocol Independent Multicast (PIM) configuration and statistics.
Start monitoring Allied Telesis Layer 3 switches 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.