All MIBs › NRC-HUB1-MIB
Category: Legacy Hubs and Repeaters
Description:
Manages NRC hub port status, link statistics, and repeater configuration for legacy NRC hub devices.
Imported Objects
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.
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
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.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| enterprises | 1.3.6.1.4.1 | |||
| nrc | 1.3.6.1.4.1.315 | |||
| hub1 | 1.3.6.1.4.1.315.1 | |||
| INT hub1AutoPartition | 1.3.6.1.4.1.315.1.1 | INTEGER | read-write | The value 'enabled' indicates that the HUB should auto partition ports. The value 'disabled' will disable this feature. |
| INT hub1ReconnectOnTransmission | 1.3.6.1.4.1.315.1.2 | INTEGER | read-write | The value 'enabled' indicates that the HUB will reconnect an auto partitioned port if the HUB receives a packet from a partitioned port. The value 'disabled' indicates that the HUB will reconnect a partitioned port if there is any traffic to or from the port. |
| INT hub1IncludeOutOfWinColl | 1.3.6.1.4.1.315.1.3 | INTEGER | read-write | A value of 'enabled' will cause Out Of Window Collisions to be counted along with In Window Collisions (as defined by IEEE 802.3) when determining if the collision count has exceeded hub1CollisionLimit and a port should be auto partitioned. A value of 'disabled' indicates that Out Of Window Collisions should NOT be counted when determining if the collision count has exceeded hub1CollisionLimit and a and a port should be auto partitioned. |
| INT hub1LoopbackPartition | 1.3.6.1.4.1.315.1.4 | INTEGER | read-write | A value of 'enabled' will cause the HUB to automatically partition a port where a lack of loopback from the transeiver is detected. A value of 'disabled' will disable this feature. Note: Setting this variable will only effect HUB operation when hub1PortType value equals 'thinNet-10Base2'. For all other hub1PortType values, a value of 'enabled' will have no effect. |
| INT hub1CollisionLimit | 1.3.6.1.4.1.315.1.5 | INTEGER | read-write | If consecutive collisions exceeding the value of this variable are detected on a port, the port will be auto partitioned 31 is the IEEE 802.3 consecutive collision limit. |
| INT hub1CarrierRecoverTime | 1.3.6.1.4.1.315.1.6 | INTEGER | read-write | Time to recover carrier. A value of 'short' will use 3 bit times (IEEE 802.3 specification). A value of 'long' will use 5 bit times. |
| OCT hub1EventCounterFlags | 1.3.6.1.4.1.315.1.7 | OCTET STRING | read-write | A bit mask indicating which error types will cause an increment in the hub1PortEventCount Counter. Each bit has the following significance where each bit is listed from most significant bit of the first octet, to least significant bit of the second octet. High (first) Octet bit 8 - not used - 7 - not used - 6 Out Of Window Collision Count Enable 5 Receive Collision Count Enable 4 Transmit Collision Count Enable 3 - not used - 2 - not used - 1 - not used - Low (second) Octet bit 8 Bad Link Count Enable 7 Partition Count Enable 6 Receive Count Enable 5 Pygmy Packet Enable 4 Non SFD Enable 3 Phase Lock Error Enable 2 Elasticity Buffer Error Enable 1 Jabber Enable When setting the value of this variable, the entire bit mask must be specified and the '-not used-' bits must not be set. |
| OCT hub1EventRecordFlags | 1.3.6.1.4.1.315.1.8 | OCTET STRING | read-write | A bit mask indicating which error types will cause corresponding bits in hub1PortEventRecordValue to be set when an error is detected. Each bit has the following significance where bits are listed from most significant bit to least significant bit. bit 8 Bad Link Enable 7 Partition Enable 6 Out Of Window Collision Enable 5 Pygmy Packet Enable 4 Non SFD Enable 3 Phase Lock Error Enable 2 Elasticity Buffer Error Enable 1 Jabber Enable When a particular bit is set, all ports will start to log the specified error in the hub1PortEventRecordValue column of the port's row of the hub1PortTable. For example, if bit 1 (Jabber Enable) is set, then for every port, a detected Jabber Error would cause bit 1 of hub1PortEventRecordValue to be set. When setting the value of this variable, the entire bit mask must be specified. When this mask is set, hub1PortRecordValue for all ports is cleared. |
| INT hub1BridgingMode | 1.3.6.1.4.1.315.1.9 | INTEGER | read-write | Operational mode of the bridge: bridging Packets are being selectively forwarded according to the internal dynamically built tables. bypass All packets are being repeated between the backbone and the repeater ports. The bridge logic is disabled. After setting this variable the HUB must be reset for the new value to take effect. NOTE: FOIRL Hubs can only have the value 'bypass' for this variable. Attempts to set this variable to 'bridging' on FOIRL hubs will be rejected. |
| INT hub1ProtocolFilterMode | 1.3.6.1.4.1.315.1.10 | INTEGER | read-write | Filtering Mode of the Hub: off The protocol filtering logic is disabled. filter The protocol filtering logic is enabled and packets with the protocol types indicated in hubFilterProtocols will not be forwarded by the bridge. pass The packet filtering logic is enabled and packets with the protocol types indicated in hubFilterProtocols will be the ONLY packets that the bridge will forward. |
| OCT hub1FilterProtocols | 1.3.6.1.4.1.315.1.11 | OCTET STRING | read-write | Protocol types to be filtered or passed by the bridging logic. This is a variable length array of between 0 and 16 2-byte entries, each entry containing the 2-byte protocol identifier as seen in the Ethernet header. Attempts to configure this variable with an OCTET STRING of odd length will be rejected. |
| INT hub1ConsoleBaudRate | 1.3.6.1.4.1.315.1.12 | INTEGER | read-write | The baud rate of the console port. Legal values are 9600, 4800, 2400, and 1200. |
| INT hub1Reset | 1.3.6.1.4.1.315.1.13 | INTEGER | read-write | Setting this object to 'reset' will cause the Hub1 to perform a hardware reset within approximately 5 seconds. Setting this object to 'no-reset will have no effect. The value 'no-reset will be returned whenever this object is retrieved. The primary purpose for including this variable in the Hub1 MIB is to allow SNMP managers to modify the operational mode of the Hub1. Changing the variable hub1BridgingMode has no effect on the Hub until the Hub is reset. |
| STR hub1SoftwareVersion | 1.3.6.1.4.1.315.1.14 | DisplayString | read-write | The version of software running on the Hub. On versions of the Hub that support dynamic download, this variable may be set to cause a new version of the software to be loaded the next time the Hub is reset (as in setting the variable hub1Reset or power cycling the unit). The version should be specified in the following format: 'MM.mm.rr' Where MM is the major number, mm is the minor number, and rr is the revision level (for example 2.0.16). On versions of the Hub that do not support dynamic download, setting this variable will result in an error. |
| hub1PortTable | 1.3.6.1.4.1.315.1.15 | not-accessible | A table of port specific information for the NRC HUB 1 product. This table supplements the Repeater MIB Ports Table. | |
| hub1PortEntry | 1.3.6.1.4.1.315.1.15.1 | not-accessible | A list of information for every port. | |
| INT hub1PortIndex | 1.3.6.1.4.1.315.1.15.1.1 | INTEGER | read-only | Port number that corresponds to the index value in the Repeater MIB variable rptrPortIndex. |
| INT hub1PortForceReconnect | 1.3.6.1.4.1.315.1.15.1.2 | INTEGER | read-write | Setting this variable to the value 'force- reconnect' will cause the port to be reconnected assuming that it is currently in the 'Partition' state. If the port is not in a 'Partition' state, setting variable to the value 'force-reconnect' will not have any effect. Setting this variable to anything other than 'force- reconnect will and an undefined effect. When retrieving this variable, the value 'idle' will always be returned. |
| INT hub1PortPartitionReason | 1.3.6.1.4.1.315.1.15.1.3 | INTEGER | read-only | Reason for port being in the partitioned state. If the port is currently not partitioned, this variable will have the value 'not-partitioned'. |
| INT hub1PortLinkState | 1.3.6.1.4.1.315.1.15.1.4 | INTEGER | read-only | This variable's meaning varies depending on the type of HUB: 10Base2 Not Applicable. A value of 'unknown' will always be returned. 10BaseT Link Test is being received ('up') or not being received ('down'). Fiber Light Monitoring (LMON) is being detected ('up') or not being detected ('down'). |
| INT hub1PortLinkEnable | 1.3.6.1.4.1.315.1.15.1.5 | INTEGER | read-write | Enabling this variable has the following effect depending on the type of HUB: 10Base2 No Effect 10BaseT Link Test Enabled Fiber LMON Test Enabled |
| INT hub1PortPolarityStatus | 1.3.6.1.4.1.315.1.15.1.6 | INTEGER | read-only | Current port Polarity status. NOTE: a value of 'ok' will always be returned for 10Base2 and FOIRL HUBs |
| STR hub1PortName | 1.3.6.1.4.1.315.1.15.1.7 | DisplayString | read-write | Administrator assigned ASCII port name. |
| INT hub1PortEventCount | 1.3.6.1.4.1.315.1.15.1.8 | INTEGER | read-only | Counter of all error events that were detected on this port and at the same time were marked for collection in the hub1EventCounterFlags variable. This is a 16 bit wrapping counter. |
| OCT hub1PortRecordValue | 1.3.6.1.4.1.315.1.15.1.9 | OCTET STRING | read-only | Bit Mask that has bits set for each error event that was detected on this port and at the same time was marked for collection in the hub1EventRecordFlags variable. Each bit has the following meaning, where the bits are listed from most significant to least significant: bit 8 Bad Link Count Error 7 Partition Count Error 6 Receive Count Error 5 Pygmy Packet Error 4 Non SFD Error 3 Phase Lock Error 2 Elasticity Buffer Error 1 Jabber Error Each read of this variable causes the variable to be cleared. |
| INT hub1PortType | 1.3.6.1.4.1.315.1.15.1.10 | INTEGER | read-only | The type of port |
| hub1IFTable | 1.3.6.1.4.1.315.1.16 | not-accessible | A table that contains HUB 1 specific supplements to the MIB-II interfaces table. | |
| hub1IFEntry | 1.3.6.1.4.1.315.1.16.1 | not-accessible | Entries in the HUB 1 supplement table. | |
| INT hub1IFIndex | 1.3.6.1.4.1.315.1.16.1.1 | INTEGER | read-only | Interface index that corresponds to ifIndex in the interfaces table from MIB II. |
| CTR hub1IFInAlignmentErrors | 1.3.6.1.4.1.315.1.16.1.2 | Counter | read-only | The number of alignment errors detected by this interface. |
| CTR hub1IFInCrcErrors | 1.3.6.1.4.1.315.1.16.1.3 | Counter | read-only | The number of CRC errors detected by this interface. |
| CTR hub1IFInCollisions | 1.3.6.1.4.1.315.1.16.1.4 | Counter | read-only | The number of collisions detected by this interface. |
| CTR hub1IFInMtuExceededDiscards | 1.3.6.1.4.1.315.1.16.1.5 | Counter | read-only | The number of frames discarded by this interface on receive due to an excessive size. |
| CTR hub1IFInShortErrors | 1.3.6.1.4.1.315.1.16.1.6 | Counter | read-only | The number of frames discarded by this interface because they were less than the Ethernet minumum frame size of 64 bytes. |
| CTR hub1IFInOverrunDiscards | 1.3.6.1.4.1.315.1.16.1.7 | Counter | read-only | The number of frames discarded by this interface due to a LAN Controller FIFO overflow on receive. |
| CTR hub1IFOutUnderruns | 1.3.6.1.4.1.315.1.16.1.8 | Counter | read-only | The number of frames which had to be retransmitted by this interface due to a LAN Controller FIFO underrun error on transmit. |
| CTR hub1IFOutLostCts | 1.3.6.1.4.1.315.1.16.1.9 | Counter | read-only | The number of times Carrier Transmit Sense (CTS) was lost on this interface during frame transmission. The hub will attempt to retransmit frames when transmission fails due to lost CTS. |
| CTR hub1IFOutLostCrs | 1.3.6.1.4.1.315.1.16.1.10 | Counter | read-only | The number of times Carrier Receive Sense (CRS) was lost on this interface during frame transmission. The hub will attempt to retransmit frames when transmission fails due to lost CRS. |
| CTR hub1IFOutMtuExceededDiscards | 1.3.6.1.4.1.315.1.16.1.11 | Counter | read-only | The number of frames discarded by this interface on transmit due to an excessive size. |
| CTR hub1IFOutCollisions | 1.3.6.1.4.1.315.1.16.1.12 | Counter | read-only | The number of collisions detected by this interface while attempting to transmit a packet. |
| OCT hub1IFChannelUtilization | 1.3.6.1.4.1.315.1.16.1.13 | OCTET STRING | read-only | Utilization statistics for the last 60 seconds of operation of the bridging logic associated with this interface. The OCTET STRING is a series of 45 16-bit words, each word representing the percentage utilization for a 1.33 second sample period. The first 16 bit word in this series represents the oldest sample. Percentages are calculated by passing each 16 bit sample through the following equation: ((Sample) * 100) / 0xffff to yield the percent channel utilization (a number ranging from 0 to 100). |
| INT hub1LastFailureReason | 1.3.6.1.4.1.315.1.17 | INTEGER | read-only | The last error that caused a Hub failure. A value of zero (0) indicates that there has not been a Hub failure since the novram was last erased. A non-zero value indicates the reason for the last Hub failure. A normal Hub reset or power cycle will not change the value of this variable (it will still indicate the reason for the last known failure. |
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.