SMONAMON-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsSMONAMON-MIB

Category: Ethernet and LAN Management, Network Performance Monitoring

Description: Provides SMON autonomous monitoring objects for triggered event collection and threshold-based traffic analysis.

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 SMONAMON-MIB?

SMONAMON-MIB is an Autonomous MONitoring (AMON) extension to the IETF SMON (Switch Monitoring, RFC 2613) framework, implemented on ATM-capable switches/probes to provide detailed cell-level traffic statistics per slot and port. It exposes per-slot and per-port ATM traffic counters broken out by service category, covering UBR, ABR, non-real-time and real-time VBR, CBR, PNNI, and signaling cells, plus error indicators like bad-HEC and dropped-cell counts. Its monitoring value is performance and fault visibility into the ATM switching fabric's traffic-handling behavior: an operator can see whether a slot is dropping cells or receiving malformed cells, and how traffic is distributed across QoS service categories, a strong signal of congestion or a misbehaving upstream device. It extends the base SMON MIB (RFC 2613) and, by association, RMON, applying autonomous threshold-triggered monitoring concepts to ATM cell statistics rather than Ethernet frames. It is deployed on ATM switches or probes in carrier or enterprise ATM backbones where cell-level, per-service-category traffic visibility is needed for capacity and fault management. Engineers can download the SMONAMON-MIB file directly to load it into their MIB browser.

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

  • ATM switch or probe implementing SMON/AMON extensions

Monitoring Examples

An operator would poll amonSlotStatsTable/amonSlotStatsEntry for a given slot's amonSlotBadHecCells and amonSlotDroppedCells to detect a card experiencing physical-layer errors or congestion, comparing amonSlotCbrCells against amonSlotUbrCells/amonSlotAbrCells to confirm real-time traffic is getting its expected share of bandwidth. A rising amonSlotDroppedCells count on one slot while others stay flat would point to a localized congestion or hardware problem on that card.

What Can Be Monitored

  • per-slot/port cell traffic by service category (CBR/VBR/ABR/UBR)
  • bad-HEC cell counts
  • dropped cell counts
  • PNNI and signaling cell counts
Imported Objects

From APPLIC-MIB

smonOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From RFC1213-MIB

ifIndex
OIDs

RFC description

Monitors ATM switch traffic statistics across slots, ports, and host stations for Lucent Cajun switches.

Start monitoring ATM switch or probe implementing SMON/AMON extensions (per-slot/port ATM cell traffic statistics) 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 SMONAMON-MIB