XYPLEX-HUB-MIB

All MIBs › XYPLEX-HUB-MIB

Category: Xylogics and Xyplex Terminal Servers

Description: Manages Xyplex wiring hub port status, segment configuration, and network utilization statistics.

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

XYPLEX-HUB-MIB is a Xyplex enterprise MIB for managing Xyplex wiring hubs, the shared-media Ethernet hub products Xyplex sold alongside its terminal servers. It exposes per-port status, network segment configuration, and utilization statistics for the hub. This MIB's main monitoring value is hardware status: administrators poll per-port link/partition status to detect a port that has been auto-partitioned due to excessive errors, and watch segment utilization statistics to see whether a shared segment is approaching saturation. It typically builds on the IETF Repeater/Hub MIB concepts (RFC 1516) in spirit, alongside Xyplex's own hub hardware objects. It is deployed on Xyplex wiring hubs in legacy shared-Ethernet LAN closets where hub port health and segment loading needed monitoring. Engineers can download the XYPLEX-HUB-MIB file directly to load it into their MIB browser.

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

Monitoring Examples

An administrator would poll each hub port's status object to check whether a port has been auto-partitioned (disabled) due to excessive collisions or jabber, then check the segment utilization statistic to see whether overall segment load is approaching capacity. A port stuck in a partitioned state would indicate a faulty NIC or cable on that port needing physical replacement. Because no sample objects were captured for this MIB, exact object names cannot be confirmed beyond what the short description indicates.

What Can Be Monitored

per-port link/partition status
segment configuration
network utilization statistics

Imported Objects

From RFC1155-SMI

Counter
enterprises

From RFC1158-MIB

DisplayString

From RFC1212-CONCISE-MIB

OBJECT-TYPE

From XYPLEX-SYSTEM-MIB

DateTime

OIDs

OID symbolic	OID numeric	Type	Access	Description
xyplex	1.3.6.1.4.1.33
hub	1.3.6.1.4.1.33.9
INT hubTwistedPairPortNumber	1.3.6.1.4.1.33.9.1	INTEGER	read-only	The number of twisted-pair hub ports. By convention, these are the lower numbered hub ports. Corresponds indirectly to the numbered, twisted-pair port numbers labeled 'Port' in the SHOW HUB SUMMARY display.
INT hubNonTwistedPairPortNumber	1.3.6.1.4.1.33.9.2	INTEGER	read-only	The number of non-twisted-pair hub ports. By convention, these are the higher numbered hub ports. Corresponds indirectly to the unnumbered, non-twisted-pair ports in the SHOW HUB SUMMARY display.
hubPortTable	1.3.6.1.4.1.33.9.3		not-accessible	A list of hub Ethernet port entries.
hubPortEntry	1.3.6.1.4.1.33.9.3.1		not-accessible	Hub parameter values for an Ethernet port.
INT hubPortIndex	1.3.6.1.4.1.33.9.3.1.1	INTEGER	read-only	An index value that uniquely identifies a port. The port identified by a particular value of this index is the same port as identified by portBasicID in hmBasicPortTable in the IEEE Hub MIB [11]. Corresponds directly to the numbered, twisted-pair port numbers labeled 'port' and indirectly to the unnumbered, non-twisted-pair ports in the SHOW HUB SUMMARY display.
STR hubPortName	1.3.6.1.4.1.33.9.3.1.2	DisplayString	read-write	An administratively assigned name for a twisted-pair port, typically with some local significance. Corresponds directly to PORT NAME and the value labeled 'Name' in the SHOW HUB SUMMARY display.
INT hubPortAutoPolarity	1.3.6.1.4.1.33.9.3.1.3	INTEGER	read-write	A control for automatic determination of twisted-pair port polarity. 'disabled' locks the port into positive polarity. 'enabled' allows the hub to sense polarity and adapt accordingly. Corresponds directly to PORT POLARITY and the value labeled 'Auto Polarity:' in the PORT display.
INT hubPortSensedPolarity	1.3.6.1.4.1.33.9.3.1.4	INTEGER	read-only	Polarity of a twisted-pair port. Corresponds directly to PORT POLARITY and the value labeled 'Polarity:' in the HUB SUMMARY display.
INT hubPortPulse	1.3.6.1.4.1.33.9.3.1.5	INTEGER	read-write	A control for periodic, automatic generation of a test pulse on a twisted-pair port. Corresponds directly to PORT TEST PULSE and the value labeled 'Test Pulse:' in the PORT display.
INT hubPortPulseStatus	1.3.6.1.4.1.33.9.3.1.6	INTEGER	read-only	Status of the last attempt to generate and detect a test pulse. Corresponds directly to the value labeled 'STATUS' and 'Test Pulse:' in the PORT display.
CTR hubPortMissedPulses	1.3.6.1.4.1.33.9.3.1.7	Counter	read-only	Number of times that a generated test pulse was not seen in return. Corresponds directly to the value labeled 'Test Pulse Lost:' in the PORT display.
CTR hubPortJabbers	1.3.6.1.4.1.33.9.3.1.8	Counter	read-only	Number of times that a received frame was terminated by the jabber timer. Corresponds directly to the value labeled 'Jabbers:' in the PORT display.
CTR hubPortBadPreambles	1.3.6.1.4.1.33.9.3.1.9	Counter	read-only	Number of times that two one bits (Start of Frame) did not follow an interpacket gap and alternating one and zero bits. Corresponds directly to the value labeled 'SOF Missing:' in the PORT display.
CTR hubPortBitRateErrors	1.3.6.1.4.1.33.9.3.1.10	Counter	read-only	Number of times that bits were received with improper timing. Corresponds directly to the value labeled 'Out of Spec. Bit Rate:' in the PORT display.
CTR hubPortLateCollisions	1.3.6.1.4.1.33.9.3.1.11	Counter	read-only	Number of times that a frame collision came after the allowed collision window. Corresponds directly to the value labeled 'Late Collisions:' in the PORT display.
CTR hubPortNormalCollisions	1.3.6.1.4.1.33.9.3.1.12	Counter	read-only	Number of times that a frame collision came within the allowed collision window. Corresponds directly to the value labeled 'Collisions:' in the PORT display.
INT hubPortZero	1.3.6.1.4.1.33.9.3.1.13	INTEGER	read-write	Control to zero counters kept for the port. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes all the system's counters to be zeroed. Corresponds to the ZERO PORT command.
TIK hubPortZeroTime	1.3.6.1.4.1.33.9.3.1.14	TimeTicks	read-only	The number of hundredths of a second since the most recent zeroing of the counters kept for the port, such as through execution of sysZeroAll or hubPortZero. Corresponds directly to the value labeled 'Since Zeroed:' in the PORT COUNTERS display.

RFC description

Xyplex (MRV Communications) enterprise SNMP MIB module for managing network hub devices and their operational parameters in network infrastructure.

Start monitoring Xyplex wiring hubs (per-port link/partition-status, segment-utilization 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.

Download XYPLEX-HUB-MIB

What Is XYPLEX-HUB-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description