XYPLEX-IEEE-HUB-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › XYPLEX-IEEE-HUB-MIB

Category: Xylogics and Xyplex Terminal Servers

Description: Manages Xyplex IEEE-compliant hub repeater port state, jabber lockup, and network management.

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 XYPLEX-IEEE-HUB-MIB?

XYPLEX-IEEE-HUB-MIB manages Xyplex IEEE 802.3-compliant Ethernet hubs/repeaters, focusing on per-port link state and the detection of abnormal conditions such as jabber lockup. It exposes categories of data covering repeater port operational state, jabber (excessive/continuous transmission) fault detection, and general network management parameters for the hub. Its monitoring value is centered on hardware fault detection: identifying ports stuck in a jabber-lockup condition or otherwise partitioned lets an administrator pinpoint a malfunctioning NIC or cable segment degrading the shared collision domain. It follows the IEEE 802.3 repeater management conventions, so it is conceptually aligned with (and likely layered over) standard 802.3 repeater MIB objects even though it is a Xyplex-specific extension. It was deployed in legacy shared-Ethernet hub environments where Xyplex hubs provided repeater connectivity for wiring closets, and network archivists can still download the XYPLEX-IEEE-HUB-MIB file to load it into a MIB browser for reference.

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

  • Xyplex IEEE 802.3 repeater/hub

Monitoring Examples

An administrator would poll per-port link/partition state to identify a port that has been automatically partitioned due to excessive collisions, then check the jabber lockup indicator for that port to confirm a faulty end-station NIC is jabbering (transmitting continuously) and disrupting the shared segment. Repeated jabber-lockup events on the same port would prompt physical replacement of the attached cable or device.

What Can Be Monitored

  • repeater port link status
  • port partition state
  • jabber lockup condition
  • network management trap/event generation
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
NetworkAddress
TimeTicks
enterprises

From SNMPv2-TC

DisplayString
OIDs

RFC description

IEEE 802 Ethernet hub monitoring for Xyplex hubs including basic, self-test, performance, and address tracking.

Start monitoring Xyplex repeaters/hubs 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 XYPLEX-IEEE-HUB-MIB