NRC-HUB1-MIB: View SNMP OID List / Download MIB

The value 'enabled' indicates that the HUB should auto partition ports. The value 'disabled' will disable this feature. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'high': 63, 'low': 31.

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. Enumeration: 'short': 3, 'long': 5.

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.

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.

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. Enumeration: 'bridging': 1, 'bypass': 2.

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. Enumeration: 'filter': 2, 'off': 1, 'pass': 3.

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.

The baud rate of the console port. Legal values are 9600, 4800, 2400, and 1200.

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. Enumeration: 'reset': 2, 'no-reset': 1.

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.

A table of port specific information for the NRC HUB 1 product. This table supplements the Repeater MIB Ports Table.

A list of information for every port.

Port number that corresponds to the index value in the Repeater MIB variable rptrPortIndex.

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. Enumeration: 'idle': 1, 'force-reconnect': 2.

Reason for port being in the partitioned state. If the port is currently not partitioned, this variable will have the value 'not-partitioned'. Enumeration: 'consecutive-collision-limit': 3, 'data-loopback-failure': 5, 'excessive-len-of-collision-limit': 4, 'other': 2, 'process-forced-reconnection': 6, 'not-partitioned': 1.

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'). Enumeration: 'down': 3, 'unknown': 1, 'up': 2.

Enabling this variable has the following effect depending on the type of HUB: 10Base2 No Effect 10BaseT Link Test Enabled Fiber LMON Test Enabled Enumeration: 'disabled': 2, 'enabled': 1.

Current port Polarity status. NOTE: a value of 'ok' will always be returned for 10Base2 and FOIRL HUBs Enumeration: 'reversed': 2, 'ok': 1.

Administrator assigned ASCII port name.

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.

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.

The type of port Enumeration: 'thinNet-10Base2': 3, 'twistedPair-10BaseT': 2, 'other': 1, 'fiber-FOIRL': 4.

A table that contains HUB 1 specific supplements to the MIB-II interfaces table.

Entries in the HUB 1 supplement table.

Interface index that corresponds to ifIndex in the interfaces table from MIB II.

The number of alignment errors detected by this interface.

The number of CRC errors detected by this interface.

The number of collisions detected by this interface.

The number of frames discarded by this interface on receive due to an excessive size.

The number of frames discarded by this interface because they were less than the Ethernet minumum frame size of 64 bytes.

The number of frames discarded by this interface due to a LAN Controller FIFO overflow on receive.

The number of frames which had to be retransmitted by this interface due to a LAN Controller FIFO underrun error on transmit.

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.

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.

The number of frames discarded by this interface on transmit due to an excessive size.

The number of collisions detected by this interface while attempting to transmit a packet.

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).

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.