NRC-HUB1-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsNRC-HUB1-MIB

Category: Legacy Hubs and Repeaters

Description: Manages NRC hub port status, link statistics, and repeater configuration for legacy NRC hub 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 NRC-HUB1-MIB?

NRC-HUB1-MIB is a legacy vendor MIB from NRC for managing NRC's Hub1-series Ethernet repeater/hub devices. It exposes port-level configuration such as auto-partition behavior, collision handling parameters (collision limit, out-of-window collision counting, loopback partition), carrier recovery timing, and repeater-specific settings like bridging mode and protocol filtering, plus console access configuration. As a legacy repeater MIB, its monitoring value lies in tracking port health at the Ethernet physical/MAC layer — auto-partition and collision-related counters and flags reveal whether a port has been electrically partitioned due to excessive collisions, a classic legacy-hub fault condition. It is a standalone enterprise MIB predating widespread reliance on standard Ethernet-like MIBs, though it parallels concepts later standardized in RFC 1516 (Ethernet-like repeater MIB). It is typically deployed in legacy 10BASE-T/coax Ethernet hub installations still in service in older network environments. Engineers can download the NRC-HUB1-MIB file directly to load it into their MIB browser.

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

  • NRC Hub1-series Ethernet hub/repeater (legacy)

Monitoring Examples

An administrator would poll hub1AutoPartition and hub1LoopbackPartition to check whether a port has been automatically disabled due to excessive errors, and review hub1CollisionLimit and hub1IncludeOutOfWinColl to understand the collision thresholds governing that behavior. The hub1CarrierRecoverTime object indicates how long the port takes to recover carrier sense after a fault, while hub1EventCounterFlags and hub1EventRecordFlags control which events are counted and logged for later review. A port repeatedly showing as auto-partitioned combined with a low hub1CollisionLimit setting would point to a persistent cabling or NIC fault on that segment.

What Can Be Monitored

  • port auto-partition status
  • collision limit and out-of-window collision handling
  • carrier recovery time
  • event counter/record flags
  • bridging mode and protocol filter configuration
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From RFC1213-MIB

DisplayString
OIDs

RFC description

Manages NRC hub port partitioning, collision handling, and loopback detection features.

Start monitoring NRC Hub1-series Ethernet hub/repeater (legacy) 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 NRC-HUB1-MIB