LBHUB-REPEATER-MIB

MIB Reference — IPNetwork Monitor

All MIBsLBHUB-REPEATER-MIB

Category: Network Management

Description:

Monitors repeater port statistics on LANBuilder network hub modules.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
NetworkAddress
TimeTicks
enterprises
mgmt

From RFC1213-MIB

DisplayString
PhysAddress

What Is LBHUB-REPEATER-MIB?

LBHUB-REPEATER-MIB is a 3Com proprietary SNMP module for LANBuilder network hub repeater modules, marked experimental, that models each hub as a group of shared-media repeater ports following IEEE 802.3 repeater management conventions. It exposes per-group repeater capacity, operational status, health text, and a table of repeater groups with descriptions and object identifiers, along with reset and diagnostic (non-disruptive test) controls. It is centered on monitoring hardware status: rptrOperSTATUS and rptrGroupOperSTATUS reveal whether a repeater group is functioning, rptrHealthText gives a human-readable health summary, and rptrTotalPartitionedPorts flags ports auto-partitioned off due to excessive collisions or faults. This MIB parallels the structure of the standard IETF REPEATER-MIB (RFC 1516/2108) though implemented as a 3Com-specific variant. It was typically deployed in legacy enterprise Ethernet hub/repeater closets for shared-media health monitoring. Engineers can download the LBHUB-REPEATER-MIB file directly to load it into their MIB browser.

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

  • repeater group operational status
  • partitioned port count
  • hub health status text
  • repeater group capacity
  • diagnostic test results

Supported Devices

  • 3Com LANBuilder network hub/repeater module

Monitoring Examples

An administrator polls rptrGroupTable/rptrGroupEntry (indexed by rptrGroupIndex) to check rptrGroupOperSTATUS and rptrGroupDescr for each repeater group in the hub. A nonzero rptrTotalPartitionedPorts alongside degraded rptrHealthText would indicate ports being auto-partitioned due to jabber or excessive collisions. rptrOperSTATUS at the hub level confirms overall repeater operation, and rptrNonDisruptTest could be invoked to run built-in diagnostics without interrupting traffic. rptrReset provides a remote recovery action if a group is reported as failed.

OIDs
OID symbolicOID numericTypeAccessDescription
mib_21.3.6.1.2.1
system1.3.6.1.2.1.1
interfaces1.3.6.1.2.1.2
at1.3.6.1.2.1.3
ip1.3.6.1.2.1.4
icmp1.3.6.1.2.1.5
tcp1.3.6.1.2.1.6
udp1.3.6.1.2.1.7
egp1.3.6.1.2.1.8
transmission1.3.6.1.2.1.10
snmp1.3.6.1.2.1.11
dot1dBridge1.3.6.1.2.1.17
snmpDot3RptrMgt1.3.6.1.2.1.22
rptrBasicPackage1.3.6.1.2.1.22.1
rptrRptrInfo1.3.6.1.2.1.22.1.1
INT rptrGroupCapacity1.3.6.1.2.1.22.1.1.1INTEGERread-onlyThe rptrGroupCapacity is the number of groups that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range from 1 to rptrGroupCapacity. Some groups may not be present in the repeater, in which case the actual number of groups present will be less than rptrGroupCapacity. The number of groups present will never be greater than rptrGroupCapacity. Note: In practice, this will generally be the number of field-replaceable units (i.e., modules, cards, or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to numbers marked on the physical enclosure.
INT rptrOperSTATUS1.3.6.1.2.1.22.1.1.2INTEGERread-onlyThe rptrOperSTATUS object indicates the operational state of the repeater. The rptrHealthText object may be consulted for more specific information about the state of the repeater's health. In the case of multiple kinds of failures (e.g., repeater failure and port failure), the value of this attribute shall reflect the highest priority failure in the following order, listed highest priority first: rptrFailure(3) groupFailure(4) portFailure(5) generalFailure(6).
STR rptrHealthText1.3.6.1.2.1.22.1.1.3DisplayStringread-onlyThe health text object is a text string that provides information relevant to the operational state of the repeater. Agents may use this string to provide detailed information on current failures, including how they were detected, and/or instructions for problem resolution. The contents are agent-specific.
INT rptrReset1.3.6.1.2.1.22.1.1.4INTEGERread-writeSetting this object to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std]. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. After receiving a request to set this variable to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. This action does not reset the management counters defined in this document nor does it affect the portAdminSTATUS parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including rptrOperSTATUS and rptrHealthText), and send a rptrHealth trap.
INT rptrNonDisruptTest1.3.6.1.2.1.22.1.1.5INTEGERread-writeSetting this object to selfTest(2) causes the repeater to perform a agent-specific, non- disruptive self-test that has the following characteristics: a) The nature of the tests is not specified. b) The test does not change the state of the repeater or management information about the repeater. c) The test does not inject packets onto any segment. d) The test does not prevent the relay of any packets. e) The test does not interfere with management functions. After performing this test, the agent will update the repeater health information (including rptrOperSTATUS and rptrHealthText) and send a rptrHealth trap. Note that this definition allows returning an 'okay' result after doing a trivial test. Setting this object to noSelfTest(1) has no effect. The agent will always return the value noSelfTest(1) when this object is read.
GAU rptrTotalPartitionedPorts1.3.6.1.2.1.22.1.1.6Gaugeread-onlyThis object returns the total number of ports in the repeater whose current state meets all three of the following criteria: rptrPortOperSTATUS does not have the value notPresent(3), rptrPortAdminSTATUS is enabled(1), and rptrPortAutoPartitionState is autoPartitioned(2).
rptrGroupInfo1.3.6.1.2.1.22.1.2
rptrGroupTable1.3.6.1.2.1.22.1.2.1not-accessibleTable of descriptive and STATUS information about the groups of ports.
rptrGroupEntry1.3.6.1.2.1.22.1.2.1.1not-accessibleAn entry in the table, containing information about a single group of ports.
INT rptrGroupIndex1.3.6.1.2.1.22.1.2.1.1.1INTEGERread-onlyThis object identifies the group within the repeater for which this entry contains information. This value is never greater than rptrGroupCapacity.
STR rptrGroupDescr1.3.6.1.2.1.22.1.2.1.1.2DisplayStringread-onlyA textual description of the group. This value should include the full name and version identification of the group's hardware type and indicate how the group is differentiated from other types of groups in the repeater. Plug-in Module, Rev A' or 'Barney Rubble 10BASE-T 4-port SIMM socket Version 2.1' are examples of valid group descriptions. It is mandatory that this only contain printable ASCII characters.
OID rptrGroupObjectID1.3.6.1.2.1.22.1.2.1.1.3OBJECT IDENTIFIERread-onlyThe vendor's authoritative identification of the group. This value may be allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of group is being managed. For example, this object could take the value 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, and had assigned the identifier 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 6-Port FOIRL Plug-in Module.'
INT rptrGroupOperSTATUS1.3.6.1.2.1.22.1.2.1.1.4INTEGERread-onlyAn object that indicates the operational STATUS of the group. A STATUS of notPresent(4) indicates that the group is temporarily or permanently physically and/or logically not a part of the repeater. It is an implementation-specific matter as to whether the agent effectively removes notPresent entries from the table. A STATUS of operational(2) indicates that the group is functioning, and a STATUS of malfunctioning(3) indicates that the group is malfunctioning in some way.
TIK rptrGroupLastOperSTATUSChange1.3.6.1.2.1.22.1.2.1.1.5TimeTicksread-onlyAn object that contains the value of sysUpTime at the time that the value of the rptrGroupOperSTATUS object for this group last changed. A value of zero indicates that the group's operational STATUS has not changed since the agent last restarted.
INT rptrGroupPortCapacity1.3.6.1.2.1.22.1.2.1.1.6INTEGERread-onlyThe rptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-1024. Within each group, the ports are uniquely numbered in the range from 1 to rptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.
rptrPortInfo1.3.6.1.2.1.22.1.3
rptrPortTable1.3.6.1.2.1.22.1.3.1not-accessibleTable of descriptive and STATUS information about the ports.
rptrPortEntry1.3.6.1.2.1.22.1.3.1.1not-accessibleAn entry in the table, containing information about a single port.
INT rptrPortGroupIndex1.3.6.1.2.1.22.1.3.1.1.1INTEGERread-onlyThis object identifies the group containing the port for which this entry contains information.
INT rptrPortIndex1.3.6.1.2.1.22.1.3.1.1.2INTEGERread-onlyThis object identifies the port within the group for which this entry contains information. This value can never be greater than rptrGroupPortCapacity for the associated group.
INT rptrPortAdminSTATUS1.3.6.1.2.1.22.1.3.1.1.3INTEGERread-writeSetting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin STATUS takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. (In effect, when a port is disabled, the value of rptrPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the rptrPortAutoPartitionState becomes notAutoPartitioned(1), regardless of its pre-disabling state.)
INT rptrPortAutoPartitionState1.3.6.1.2.1.22.1.3.1.1.4INTEGERread-onlyThe autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here.
INT rptrPortOperSTATUS1.3.6.1.2.1.22.1.3.1.1.5INTEGERread-onlyThis object indicates the port's operational STATUS. The notPresent(3) status indicates the port is physically removed (note this may or may not be possible depending on the type of port.) The operational(1) STATUS indicates that the port is enabled (see rptrPortAdminSTATUS) and working, even though it might be auto-partitioned (see rptrPortAutoPartitionState). If this object has the value operational(1) and rptrPortAdminSTATUS is set to disabled(2), it is expected that this object's value will soon change to notOperational(2).
rptrMonitorPackage1.3.6.1.2.1.22.2
rptrMonitorRptrInfo1.3.6.1.2.1.22.2.1
CTR rptrMonitorTransmitCollisions1.3.6.1.2.1.22.2.1.1Counterread-onlyThis counter is incremented every time the repeater state machine enters the TRANSMIT COLLISION state from any state other than ONE PORT LEFT (Ref: Fig 9-2, IEEE 802.3 Std). The approximate minimum time for rollover of this counter is 16 hours.
rptrMonitorGroupInfo1.3.6.1.2.1.22.2.2
rptrMonitorGroupTable1.3.6.1.2.1.22.2.2.1not-accessibleTable of performance and error statistics for the groups.
rptrMonitorGroupEntry1.3.6.1.2.1.22.2.2.1.1not-accessibleAn entry in the table, containing total performance and error statistics for a single group. Regular retrieval of the information in this table provides a means of tracking the performance and health of the networked devices attached to this group's ports. The counters in this table are redundant in the sense that they are the summations of information already available through other objects. However, these sums provide a considerable optimization of network management traffic over the otherwise necessary retrieval of the individual counters included in each sum.
INT rptrMonitorGroupIndex1.3.6.1.2.1.22.2.2.1.1.1INTEGERread-onlyThis object identifies the group within the repeater for which this entry contains information.
CTR rptrMonitorGroupTotalFrames1.3.6.1.2.1.22.2.2.1.1.2Counterread-onlyThe total number of frames of valid frame length that have been received on the ports in this group and for which the FCSError and CollisionEvent signals were not asserted. This counter is the summation of the values of the rptrMonitorPortReadableFrames counters for all of the ports in the group. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.
CTR rptrMonitorGroupTotalOctets1.3.6.1.2.1.22.2.2.1.1.3Counterread-onlyThe total number of octets contained in the valid frames that have been received on the ports in this group. This counter is the summation of the values of the rptrMonitorPortReadableOctets counters for all of the ports in the group. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.
CTR rptrMonitorGroupTotalErrors1.3.6.1.2.1.22.2.2.1.1.4Counterread-onlyThe total number of errors which have occurred on all of the ports in this group. This counter is the summation of the values of the rptrMonitorPortTotalErrors counters for all of the ports in the group.
rptrMonitorPortInfo1.3.6.1.2.1.22.2.3
rptrMonitorPortTable1.3.6.1.2.1.22.2.3.1not-accessibleTable of performance and error statistics for the ports.
rptrMonitorPortEntry1.3.6.1.2.1.22.2.3.1.1not-accessibleAn entry in the table, containing performance and error statistics for a single port.
INT rptrMonitorPortGroupIndex1.3.6.1.2.1.22.2.3.1.1.1INTEGERread-onlyThis object identifies the group containing the port for which this entry contains information.
INT rptrMonitorPortIndex1.3.6.1.2.1.22.2.3.1.1.2INTEGERread-onlyThis object identifies the port within the group for which this entry contains information.
CTR rptrMonitorPortReadableFrames1.3.6.1.2.1.22.2.3.1.1.3Counterread-onlyThis object is the number of frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1) and for which the FCSError and CollisionEvent signals are not asserted. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.
CTR rptrMonitorPortReadableOctets1.3.6.1.2.1.22.2.3.1.1.4Counterread-onlyThis object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame (i.e., including FCS octets but excluding framing bits and dribble bits). This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.
CTR rptrMonitorPortFCSErrors1.3.6.1.2.1.22.2.3.1.1.5Counterread-onlyThis counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError and CollisionEvent signals deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). The approximate minimum time for rollover of this counter is 80 hours.
CTR rptrMonitorPortAlignmentErrors1.3.6.1.2.1.22.2.3.1.1.6Counterread-onlyThis counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If rptrMonitorPortAlignmentErrors is incremented then the rptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. The approximate minimum time for rollover of this counter is 80 hours.
CTR rptrMonitorPortFrameTooLongs1.3.6.1.2.1.22.2.3.1.1.7Counterread-onlyThis counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). If rptrMonitorPortFrameTooLongs is incremented then neither the rptrMonitorPortAlignmentErrors nor the rptrMonitorPortFCSErrors counter shall be incremented for the frame. The approximate minimum time for rollover of this counter is 61 days.
CTR rptrMonitorPortShortEvents1.3.6.1.2.1.22.2.3.1.1.8Counterread-onlyThis counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Note: shortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network. Implementors may wish to consider selecting the ShortEventMaxTime towards the lower end of the allowed tolerance range to accommodate bit losses suffered through physical channel devices not budgeted for within this standard. The approximate minimum time for rollover of this counter is 16 hours.
CTR rptrMonitorPortRunts1.3.6.1.2.1.22.2.3.1.1.9Counterread-onlyThis counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than ValidPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times. An event whose length is greater than 74 bit times but less than 82 bit times shall increment either the shortEvents counter or the runts counter but not both. A CarrierEvent greater than or equal to 552 bit times but less than 565 bit times may or may not be counted as a runt. ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of collision fragments may exceed ValidPacketMinTime. The approximate minimum time for rollover of this counter is 16 hours.
CTR rptrMonitorPortCollisions1.3.6.1.2.1.22.2.3.1.1.10Counterread-onlyThis counter is incremented by one for any CarrierEvent signal on any port for which the CollisionEvent signal on this port is also asserted. The approximate minimum time for rollover of this counter is 16 hours.
CTR rptrMonitorPortLateEvents1.3.6.1.2.1.22.2.3.1.1.11Counterread-onlyThis counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variable transitions to the value SQE (Ref: 9.6.6.2, IEEE 802.3 Std) while the ActivityDuration is greater than the LateEventThreshold. Such a CarrierEvent is counted twice, as both a collision and as a lateEvent. The LateEventThreshold is greater than 480 bit times and less than 565 bit times. LateEventThreshold has tolerances included to permit an implementation to build a single threshold to serve as both the LateEventThreshold and ValidPacketMinTime threshold. The approximate minimum time for rollover of this counter is 81 hours.
CTR rptrMonitorPortVeryLongEvents1.3.6.1.2.1.22.2.3.1.1.12Counterread-onlyThis counter is incremented by one for each CarrierEvent on this port whose ActivityDuration is greater than the MAU Jabber Lockup Protection timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). Other counters may be incremented as appropriate.
CTR rptrMonitorPortDataRateMismatches1.3.6.1.2.1.22.2.3.1.1.13Counterread-onlyThis counter is incremented by one for each frame received on this port that meets all of the following conditions: a) The CollisionEvent signal is not asserted. b) The ActivityDuration is greater than ValidPacketMinTime. c) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing. When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.
CTR rptrMonitorPortAutoPartitions1.3.6.1.2.1.22.2.3.1.1.14Counterread-onlyThis counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause port partitioning are specified in the partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here.
CTR rptrMonitorPortTotalErrors1.3.6.1.2.1.22.2.3.1.1.15Counterread-onlyThe total number of errors which have occurred on this port. This counter is the summation of the values of other error counters (for the same port), namely: rptrMonitorPortFCSErrors, rptrMonitorPortAlignmentErrors, rptrMonitorPortFrameTooLongs, rptrMonitorPortShortEvents, rptrMonitorPortLateEvents, rptrMonitorPortVeryLongEvents, and rptrMonitorPortDataRateMismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.
rptrAddrTrackPackage1.3.6.1.2.1.22.3
rptrAddrTrackRptrInfo1.3.6.1.2.1.22.3.1
rptrAddrTrackGroupInfo1.3.6.1.2.1.22.3.2
rptrAddrTrackPortInfo1.3.6.1.2.1.22.3.3
rptrAddrTrackTable1.3.6.1.2.1.22.3.3.1not-accessibleTable of address mapping information about the ports.
rptrAddrTrackEntry1.3.6.1.2.1.22.3.3.1.1not-accessibleAn entry in the table, containing address mapping information about a single port.
INT rptrAddrTrackGroupIndex1.3.6.1.2.1.22.3.3.1.1.1INTEGERread-onlyThis object identifies the group containing the port for which this entry contains information.
INT rptrAddrTrackPortIndex1.3.6.1.2.1.22.3.3.1.1.2INTEGERread-onlyThis object identifies the port within the group for which this entry contains information.
MAC rptrAddrTrackLastSourceAddress1.3.6.1.2.1.22.3.3.1.1.3MacAddressread-onlyThis object is the SourceAddress of the last readable frame (i.e., counted by rptrMonitorPortReadableFrames) received by this port. This object has been deprecated because its value is undefined when no frames have been observed on this port. The replacement object is rptrAddrTrackNewLastSrcAddress.
CTR rptrAddrTrackSourceAddrChanges1.3.6.1.2.1.22.3.3.1.1.4Counterread-onlyThis counter is incremented by one for each time that the rptrAddrTrackLastSourceAddress attribute for this port has changed. This may indicate whether a link is connected to a single DTE or another multi-user segment. The approximate minimum time for rollover of this counter is 81 hours.
OCT rptrAddrTrackNewLastSrcAddress1.3.6.1.2.1.22.3.3.1.1.5OCTET STRINGread-onlyThis object is the SourceAddress of the last readable frame (i.e., counted by rptrMonitorPortReadableFrames) received by this port. If no frames have been received by this port since the agent began monitoring the port activity, the agent shall return a string of length zero.
snmpDot3MauMgt1.3.6.1.2.1.26
dot3RpMauBasicGroup1.3.6.1.2.1.26.1
rpMauTable1.3.6.1.2.1.26.1.1not-accessibleTable of descriptive and status information about the MAU(s) attached to the ports of a repeater.
rpMauEntry1.3.6.1.2.1.26.1.1.1not-accessibleAn entry in the table, containing information about a single MAU.
INT rpMauGroupIndex1.3.6.1.2.1.26.1.1.1.1INTEGERread-onlyThis variable uniquely identifies the repeater group containing the port to which the MAU described by this entry is connected.
INT rpMauPortIndex1.3.6.1.2.1.26.1.1.1.2INTEGERread-onlyThis variable uniquely identifies the repeater port within group rpMauGroupIndex to which the MAU described by this entry is connected.
INT rpMauIndex1.3.6.1.2.1.26.1.1.1.3INTEGERread-onlyThis variable uniquely identifies the MAU connected to port rpMauPortIndex within group rpMauGroupIndex that is described by this entry.
OID rpMauType1.3.6.1.2.1.26.1.1.1.4OBJECT IDENTIFIERread-onlyThis object identifies the 10 Mb/s baseband MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value.
INT rpMauStatus1.3.6.1.2.1.26.1.1.1.5INTEGERread-writeThe current state of the MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAU state. Some agents may not support setting the value of this object to some of the enumerated values. The value other(1) is returned if the MAU is in a state other than one of the states 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. A MAU in the operational(3) state is fully functional, operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI and the media transmitter to idle. Standby(4) mode only applies to link type MAUs. The state of rpMauMediaAvailable is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter as though it were powered down. The MAU may return other(1) value for the mauJabber and rpMauMediaAvailable objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power- on cycle of at least one-half second would. The agent is not required to return the value reset (6). Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state.
INT rpMauMediaAvailable1.3.6.1.2.1.26.1.1.1.6INTEGERread-onlyIf the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link test fail state/low light function. For an AUI or a coax (including broadband) MAU this indicates whether or not loopback is detected on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. The value other(1) is returned if the mediaAvailable state is not one of 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback will be tested on each transmission during which no collision is detected. If DI is receiving input when DO returns to IDL after a transmission and there has been no collision during the transmission then loopback will be detected. The value of this attribute will only change during non-collided transmissions for AUI, coax, and 10BASE-FP MAUs. The value available(3) indicates that the link, light, or loopback is normal. The value notAvailable(4) indicates link loss, low light, or no loopback. The value remoteFault(5) indicates that a fault has been detected at the remote end of the link. The value invalidSignal(6) indicates that an invalid signal has been received from the other end of the link. Both remoteFault(5) and invalidSignal(6) apply only to MAUs of type 10BASE-FB.
CTR rpMauMediaAvailableStateExits1.3.6.1.2.1.26.1.1.1.7Counterread-onlyA count of the number of times that rpMauMediaAvailable for this MAU instance leaves the state available(3).
INT rpMauJabberState1.3.6.1.2.1.26.1.1.1.8INTEGERread-onlyThe value other(1) is returned if the jabber state is not 2, 3, or 4. The agent must always return other(1) for MAU type dot3MauTypeAUI. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. If the MAU is not jabbering the agent returns noJabber(3). This is the 'normal' state. If the MAU is in jabber state the agent returns the jabbering(4) value.
CTR rpMauJabberingStateEnters1.3.6.1.2.1.26.1.1.1.9Counterread-onlyA count of the number of times that rpMauJabberState for this MAU instance enters the state jabbering(4). For a MAU of type dot3MauTypeAUI, this counter will always indicate zero.
dot3IfMauBasicGroup1.3.6.1.2.1.26.2
dot3BroadMauBasicGroup1.3.6.1.2.1.26.3
dot3MauType1.3.6.1.2.1.26.4
dot3MauTypeAUI1.3.6.1.2.1.26.4.1
dot3MauType10Base51.3.6.1.2.1.26.4.2
dot3MauTypeFoirl1.3.6.1.2.1.26.4.3
dot3MauType10Base21.3.6.1.2.1.26.4.4
dot3MauType10BaseT1.3.6.1.2.1.26.4.5
dot3MauType10BaseFP1.3.6.1.2.1.26.4.6
dot3MauType10BaseFB1.3.6.1.2.1.26.4.7
dot3MauType10BaseFL1.3.6.1.2.1.26.4.8
dot3MauType10Broad361.3.6.1.2.1.26.4.9
a3Com1.3.6.1.4.1.43
products1.3.6.1.4.1.43.1
terminalServer1.3.6.1.4.1.43.1.1
dedicatedBridgeServer1.3.6.1.4.1.43.1.2
dedicatedRouteServer1.3.6.1.4.1.43.1.3
brouter1.3.6.1.4.1.43.1.4
genericMSWorkstation1.3.6.1.4.1.43.1.5
genericMSServer1.3.6.1.4.1.43.1.6
genericUnixServer1.3.6.1.4.1.43.1.7
hub1.3.6.1.4.1.43.1.8
linkBuilder3GH1.3.6.1.4.1.43.1.8.1
linkBuilder10BTi1.3.6.1.4.1.43.1.8.2
linkBuilderECS1.3.6.1.4.1.43.1.8.3
linkBuilderMSH1.3.6.1.4.1.43.1.8.4
linkBuilderFMS1.3.6.1.4.1.43.1.8.5
linkBuilderFDDIwg1.3.6.1.4.1.43.1.8.6
linkBuilderFMSII1.3.6.1.4.1.43.1.8.7
linkSwitchFMS1.3.6.1.4.1.43.1.8.8
linkSwitchMSH1.3.6.1.4.1.43.1.8.9
linkBuilderFMSLBridge1.3.6.1.4.1.43.1.8.10
cards1.3.6.1.4.1.43.1.9
linkBuilder3GH_cards1.3.6.1.4.1.43.1.9.1
linkBuilder10BTi_cards1.3.6.1.4.1.43.1.9.2
linkBuilder10BTi_cards_utp1.3.6.1.4.1.43.1.9.2.1
linkBuilder10BT_cards_utp1.3.6.1.4.1.43.1.9.2.2
linkBuilderECS_cards1.3.6.1.4.1.43.1.9.3
linkBuilderMSH_cards1.3.6.1.4.1.43.1.9.4
linkBuilderFMS_cards1.3.6.1.4.1.43.1.9.5
linkBuilderFMS_cards_utp1.3.6.1.4.1.43.1.9.5.1
linkBuilderFMS_cards_coax1.3.6.1.4.1.43.1.9.5.2
linkBuilderFMS_cards_fiber1.3.6.1.4.1.43.1.9.5.3
linkBuilderFMS_cards_12fiber1.3.6.1.4.1.43.1.9.5.4
linkBuilderFMS_cards_24utp1.3.6.1.4.1.43.1.9.5.5
linkBuilderFMSII_cards1.3.6.1.4.1.43.1.9.6
linkBuilderFMSII_cards_12tp_rj451.3.6.1.4.1.43.1.9.6.1
linkBuilderFMSII_cards_10coax_bnc1.3.6.1.4.1.43.1.9.6.2
linkBuilderFMSII_cards_6fiber_st1.3.6.1.4.1.43.1.9.6.3
linkBuilderFMSII_cards_12fiber_st1.3.6.1.4.1.43.1.9.6.4
linkBuilderFMSII_cards_24tp_rj451.3.6.1.4.1.43.1.9.6.5
linkBuilderFMSII_cards_24tp_telco1.3.6.1.4.1.43.1.9.6.6
chipsets1.3.6.1.4.1.43.1.10
amp_mib1.3.6.1.4.1.43.3
genericTrap1.3.6.1.4.1.43.4
viewBuilderApps1.3.6.1.4.1.43.5
specificTrap1.3.6.1.4.1.43.6
linkBuilder3GH_mib1.3.6.1.4.1.43.7
linkBuilder10BTi_mib1.3.6.1.4.1.43.8
linkBuilderECS_mib1.3.6.1.4.1.43.9
generic1.3.6.1.4.1.43.10
genExperimental1.3.6.1.4.1.43.10.1
testData1.3.6.1.4.1.43.10.1.1
ifExtensions1.3.6.1.4.1.43.10.1.2
setup1.3.6.1.4.1.43.10.2
sysLoader1.3.6.1.4.1.43.10.3
security1.3.6.1.4.1.43.10.4
gauges1.3.6.1.4.1.43.10.5
asciiAgent1.3.6.1.4.1.43.10.6
serialIf1.3.6.1.4.1.43.10.7
repeaterMgmt1.3.6.1.4.1.43.10.8
endStation1.3.6.1.4.1.43.10.9
localSnmp1.3.6.1.4.1.43.10.10
manager1.3.6.1.4.1.43.10.11
unusedGeneric121.3.6.1.4.1.43.10.12
chassis1.3.6.1.4.1.43.10.14
mrmResilience1.3.6.1.4.1.43.10.15
tokenRing1.3.6.1.4.1.43.10.16
multiRepeater1.3.6.1.4.1.43.10.17
bridgeMgmt1.3.6.1.4.1.43.10.18
fault1.3.6.1.4.1.43.10.19
poll1.3.6.1.4.1.43.10.20
powerSupply1.3.6.1.4.1.43.10.21
netBuilder_mib1.3.6.1.4.1.43.11
lBridgeECS_mib1.3.6.1.4.1.43.12
deskMan_mib1.3.6.1.4.1.43.13
linkBuilderMSH_mib1.3.6.1.4.1.43.14
linkBuilderFMS_mib1.3.6.1.4.1.43.15
linkBuilderFDDI_wghub_mib1.3.6.1.4.1.43.16
linkSwitch_mib1.3.6.1.4.1.43.17

RFC description

3Com (LinkBuilder) repeater/hub MIB for managing IEEE 802.3 network repeaters and media attachment units (MAU), including jabbering detection and port statistics.

Start monitoring 3Com LANBuilder network hub/repeater module 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 LBHUB-REPEATER-MIB