REPEATER-MIB-2

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsREPEATER-MIB-2

Category: Legacy Hubs and Repeaters

Description: Provides updated IEEE 802.3 repeater management objects extending the original REPEATER-MIB.

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 REPEATER-MIB-2?

REPEATER-MIB-2 is an updated/extended version of the IEEE 802.3 REPEATER-MIB, used to manage multi-port Ethernet repeater (hub) devices, adding device identity and slot/port inventory objects beyond the original standard. It exposes device-level identity information (device type, name, IP address, MAC address), current date/time on the device, and slot/port capacity and usage counts, alongside packet counters. Its monitoring focus spans both hardware and basic operational status: tracking how many slots/ports are occupied versus total to catch module removal or port failures, and total packet counts for basic traffic-level health. It builds on and extends the original IEEE 802.3-based REPEATER-MIB standard rather than replacing it. It is typically deployed in legacy Ethernet hub/repeater hardware in older LAN wiring closets. Engineers implementing or auditing this functionality typically reference the REPEATER-MIB-2 RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in REPEATER-MIB-2. 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 (IEEE 802.3 repeater/hub), not tied to a specific manufacturer

Monitoring Examples

An operator would poll deviceOccupiedSlots against deviceSlots to detect whether a repeater module has been physically removed or has failed to be recognized by the chassis. Comparing devicePortsOn to deviceTotalPorts on a given unit (identified by deviceName/deviceIPAddress/mACAddress) reveals how many ports are currently active versus disabled or down. deviceTotalPkts gives a coarse traffic-volume counter useful for detecting a dead or saturated repeater segment.

What Can Be Monitored

  • slot/module occupancy
  • active vs. total ports
  • device identity (type/name/IP/MAC)
  • total packet count
  • current device date/time
Imported Objects

From IRM-OIDS

commonRev1OBJECT-IDENTITY
productOBJECT-IDENTITY
repeaterRev1OBJECT-IDENTITY
repeaterRev2OBJECT-IDENTITY
subSysMMACOBJECT-IDENTITY
sysChassisOBJECT-IDENTITY
sysRepeatersOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
NetworkAddress
OIDs

RFC description

Vendor-specific repeater MIB for Cabletron Systems' MMAC Intelligent Repeaters. Manages MMAC IRBM and IRM2 intelligent repeater modules, extending beyond standard RFC 2108 repeater management.

Start monitoring vendor-neutral, standards-based MIB (IEEE 802.3 repeater/hub), extended device identity/slot inventory 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 REPEATER-MIB-2