All MIBs › RFC1231-MIB
Category: IETF Standards
Description: Defines management objects for IEEE 802.5 Token Ring interface monitoring per RFC 1231.
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 RFC1231-MIB?
This is a vendor-neutral IETF standards MIB (RFC 1231) defining management objects for IEEE 802.5 Token Ring network interfaces, applicable to any compliant Token Ring adapter, bridge, or router regardless of manufacturer. It exposes ring-level configuration (ring speed, functional address) and a rich set of hardware error-statistics counters covering line errors, burst errors, token errors, ring purge errors, and soft errors, plus ring station identification. It is squarely a hardware-health monitoring MIB: rising error counters reveal cabling problems, a failing adapter, or ring instability such as beaconing, and the ring station table shows which stations are currently active on the ring. It complements the standard IF-MIB (RFC 2863) since Token Ring interfaces are indexed by ifIndex like any other interface type. It was historically deployed on Token Ring adapters, bridges, and routers in IBM-centric enterprise LANs, technology that is now largely obsolete and replaced by Ethernet. Engineers can download the RFC1231-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1231-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
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- IEEE 802.5 Token Ring network interface/adapter
- Token Ring bridge or router
Monitoring Examples
An administrator polling dot5StatsTable objects such as dot5StatsLineErrors, dot5StatsBurstErrors, and dot5StatsTokenErrors for a given ring interface can detect rising error counts indicating cable degradation, a failing network adapter, or ring beaconing events. dot5StatsRingRecoveries and dot5StatsSoftErrors indicate transient wiring problems that should be investigated before they escalate into a hard ring failure.
What Can Be Monitored
- Token Ring line error count
- burst error count
- token error count
- ring recovery count
- soft error count
- ring station status
This MIB depends on
Related MIBs
Imported Objects
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| dot5 | 1.3.6.1.2.1.10.9 | |||
| dot5Table | 1.3.6.1.2.1.10.9.1 | not-accessible | This table contains Token Ring interface parameters and state variables, one entry per 802.5 interface. | |
| dot5Entry | 1.3.6.1.2.1.10.9.1.1 | not-accessible | A list of Token Ring status and parameter values for an 802.5 interface. | |
| INT dot5IfIndex | 1.3.6.1.2.1.10.9.1.1.1 | INTEGER | read-only | The value of this object identifies the 802.5 interface for which this entry contains management information. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface. |
| INT dot5Commands | 1.3.6.1.2.1.10.9.1.1.2 | INTEGER | read-write | When this object is set to the value of open(2), the station should go into the open state. The progress and success of the open is given by the values of the objects dot5RingState and dot5RingOpenStatus. When this object is set to the value of reset(3), then the station should do a reset. On a reset, all MIB counters should retain their values, if possible. Other side affects are dependent on the hardware chip set. When this object is set to the value of close(4), the station should go into the stopped state by removing itself from the ring. Setting this object to a value of no-op(1) has no effect. When read, this object always has a value of no-op(1). |
| INT dot5RingStatus | 1.3.6.1.2.1.10.9.1.1.3 | INTEGER | read-only | The current interface status which can be used to diagnose fluctuating problems that can occur on token rings, after a station has successfully been added to the ring. Before an open is completed, this object has the value for the 'no status' condition. The dot5RingState and dot5RingOpenStatus objects provide for debugging problems when the station can not even enter the ring. The object's value is a sum of values, one for each currently applicable condition. The following values are defined for various conditions: 0 = No Problems detected 32 = Ring Recovery 64 = Single Station 256 = Remove Received 512 = reserved 1024 = Auto-Removal Error 2048 = Lobe Wire Fault 4096 = Transmit Beacon 8192 = Soft Error 16384 = Hard Error 32768 = Signal Loss 131072 = no status, open not completed. |
| INT dot5RingState | 1.3.6.1.2.1.10.9.1.1.4 | INTEGER | read-only | The current interface state with respect to entering or leaving the ring. |
| INT dot5RingOpenStatus | 1.3.6.1.2.1.10.9.1.1.5 | INTEGER | read-only | This object indicates the success, or the reason for failure, of the station's most recent attempt to enter the ring. |
| INT dot5RingSpeed | 1.3.6.1.2.1.10.9.1.1.6 | INTEGER | read-write | The ring's bandwidth. |
| MAC dot5UpStream | 1.3.6.1.2.1.10.9.1.1.7 | MacAddress | read-only | The MAC-address of the up stream neighbor station in the ring. |
| INT dot5ActMonParticipate | 1.3.6.1.2.1.10.9.1.1.8 | INTEGER | read-write | If this object has a value of true(1) then this interface will participate in the active monitor selection process. If the value is false(2) then it will not. Setting this object might not have an effect until the next time the interface is opened. |
| MAC dot5Functional | 1.3.6.1.2.1.10.9.1.1.9 | MacAddress | read-write | The bit mask of all Token Ring functional addresses for which this interface will accept frames. |
| dot5StatsTable | 1.3.6.1.2.1.10.9.2 | not-accessible | A table containing Token Ring statistics, one entry per 802.5 interface. All the statistics are defined using the syntax Counter as 32-bit wrap around counters. Thus, if an interface's hardware maintains these statistics in 16-bit counters, then the agent must read the hardware's counters frequently enough to prevent loss of significance, in order to maintain 32-bit counters in software. | |
| dot5StatsEntry | 1.3.6.1.2.1.10.9.2.1 | not-accessible | An entry contains the 802.5 statistics for a particular interface. | |
| INT dot5StatsIfIndex | 1.3.6.1.2.1.10.9.2.1.1 | INTEGER | read-only | The value of this object identifies the 802.5 interface for which this entry contains management information. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface. |
| CTR dot5StatsLineErrors | 1.3.6.1.2.1.10.9.2.1.2 | Counter | read-only | This counter is incremented when a frame or token is copied or repeated by a station, the E bit is zero in the frame or token and one of the following conditions exists: 1) there is a non-data bit (J or K bit) between the SD and the ED of the frame or token, or 2) there is an FCS error in the frame. |
| CTR dot5StatsBurstErrors | 1.3.6.1.2.1.10.9.2.1.3 | Counter | read-only | This counter is incremented when a station detects the absence of transitions for five half-bit timers (burst-five error). |
| CTR dot5StatsACErrors | 1.3.6.1.2.1.10.9.2.1.4 | Counter | read-only | This counter is incremented when a station receives an AMP or SMP frame in which A is equal to C is equal to 0, and then receives another SMP frame with A is equal to C is equal to 0 without first receiving an AMP frame. It denotes a station that cannot set the AC bits properly. |
| CTR dot5StatsAbortTransErrors | 1.3.6.1.2.1.10.9.2.1.5 | Counter | read-only | This counter is incremented when a station transmits an abort delimiter while transmitting. |
| CTR dot5StatsInternalErrors | 1.3.6.1.2.1.10.9.2.1.6 | Counter | read-only | This counter is incremented when a station recognizes an internal error. |
| CTR dot5StatsLostFrameErrors | 1.3.6.1.2.1.10.9.2.1.7 | Counter | read-only | This counter is incremented when a station is transmitting and its TRR timer expires. This condition denotes a condition where a transmitting station in strip mode does not receive the trailer of the frame before the TRR timer goes off. |
| CTR dot5StatsReceiveCongestions | 1.3.6.1.2.1.10.9.2.1.8 | Counter | read-only | This counter is incremented when a station recognizes a frame addressed to its specific address, but has no available buffer space indicating that the station is congested. |
| CTR dot5StatsFrameCopiedErrors | 1.3.6.1.2.1.10.9.2.1.9 | Counter | read-only | This counter is incremented when a station recognizes a frame addressed to its specific address and detects that the FS field A bits are set to 1 indicating a possible line hit or duplicate address. |
| CTR dot5StatsTokenErrors | 1.3.6.1.2.1.10.9.2.1.10 | Counter | read-only | This counter is incremented when a station acting as the active monitor recognizes an error condition that needs a token transmitted. |
| CTR dot5StatsSoftErrors | 1.3.6.1.2.1.10.9.2.1.11 | Counter | read-only | The number of Soft Errors the interface has detected. It directly corresponds to the number of Report Error MAC frames that this interface has transmitted. Soft Errors are those which are recoverable by the MAC layer protocols. |
| CTR dot5StatsHardErrors | 1.3.6.1.2.1.10.9.2.1.12 | Counter | read-only | The number of times this interface has detected an immediately recoverable fatal error. It denotes the number of times this interface is either transmitting or receiving beacon MAC frames. |
| CTR dot5StatsSignalLoss | 1.3.6.1.2.1.10.9.2.1.13 | Counter | read-only | The number of times this interface has detected the loss of signal condition from the ring. |
| CTR dot5StatsTransmitBeacons | 1.3.6.1.2.1.10.9.2.1.14 | Counter | read-only | The number of times this interface has transmitted a beacon frame. |
| CTR dot5StatsRecoverys | 1.3.6.1.2.1.10.9.2.1.15 | Counter | read-only | The number of Claim Token MAC frames received or transmitted after the interface has received a Ring Purge MAC frame. This counter signifies the number of times the ring has been purged and is being recovered back into a normal operating state. |
| CTR dot5StatsLobeWires | 1.3.6.1.2.1.10.9.2.1.16 | Counter | read-only | The number of times the interface has detected an open or short circuit in the lobe data path. The adapter will be closed and dot5RingState will signify this condition. |
| CTR dot5StatsRemoves | 1.3.6.1.2.1.10.9.2.1.17 | Counter | read-only | The number of times the interface has received a Remove Ring Station MAC frame request. When this frame is received the interface will enter the close state and dot5RingState will signify this condition. |
| CTR dot5StatsSingles | 1.3.6.1.2.1.10.9.2.1.18 | Counter | read-only | The number of times the interface has sensed that it is the only station on the ring. This will happen if the interface is the first one up on a ring, or if there is a hardware problem. |
| CTR dot5StatsFreqErrors | 1.3.6.1.2.1.10.9.2.1.19 | Counter | read-only | The number of times the interface has detected that the frequency of the incoming signal differs from the expected frequency by more than that specified by the IEEE 802.5 standard, see chapter 7 in [10]. |
| dot5Tests | 1.3.6.1.2.1.10.9.3 | |||
| testInsertFunc | 1.3.6.1.2.1.10.9.3.1 | |||
| dot5ChipSets | 1.3.6.1.2.1.10.9.4 | |||
| chipSetIBM16 | 1.3.6.1.2.1.10.9.4.1 | |||
| chipSetTItms380 | 1.3.6.1.2.1.10.9.4.2 | |||
| chipSetTItms380c16 | 1.3.6.1.2.1.10.9.4.3 | |||
| dot5TimerTable | 1.3.6.1.2.1.10.9.5 | not-accessible | This table contains Token Ring interface timer values, one entry per 802.5 interface. | |
| dot5TimerEntry | 1.3.6.1.2.1.10.9.5.1 | not-accessible | A list of Token Ring timer values for an 802.5 interface. | |
| INT dot5TimerIfIndex | 1.3.6.1.2.1.10.9.5.1.1 | INTEGER | read-only | The value of this object identifies the 802.5 interface for which this entry contains timer values. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface. |
| INT dot5TimerReturnRepeat | 1.3.6.1.2.1.10.9.5.1.2 | INTEGER | read-only | The time-out value used to ensure the interface will return to Repeat State, in units of 100 micro-seconds. The value should be greater than the maximum ring latency. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerHolding | 1.3.6.1.2.1.10.9.5.1.3 | INTEGER | read-only | Maximum period of time a station is permitted to transmit frames after capturing a token, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerQueuePDU | 1.3.6.1.2.1.10.9.5.1.4 | INTEGER | read-only | The time-out value for enqueuing of an SMP PDU after reception of an AMP or SMP frame in which the A and C bits were equal to 0, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerValidTransmit | 1.3.6.1.2.1.10.9.5.1.5 | INTEGER | read-only | The time-out value used by the active monitor to detect the absence of valid transmissions, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerNoToken | 1.3.6.1.2.1.10.9.5.1.6 | INTEGER | read-only | The time-out value used to recover from various-related error situations [9]. If N is the maximum number of stations on the ring, the value of this timer is normally: dot5TimerReturnRepeat + N*dot5TimerHolding. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerActiveMon | 1.3.6.1.2.1.10.9.5.1.7 | INTEGER | read-only | The time-out value used by the active monitor to stimulate the enqueuing of an AMP PDU for transmission, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerStandbyMon | 1.3.6.1.2.1.10.9.5.1.8 | INTEGER | read-only | The time-out value used by the stand-by monitors to ensure that there is an active monitor on the ring and to detect a continuous stream of tokens, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerErrorReport | 1.3.6.1.2.1.10.9.5.1.9 | INTEGER | read-only | The time-out value which determines how often a station shall send a Report Error MAC frame to report its error counters, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerBeaconTransmit | 1.3.6.1.2.1.10.9.5.1.10 | INTEGER | read-only | The time-out value which determines how long a station shall remain in the state of transmitting Beacon frames before entering the Bypass state, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
| INT dot5TimerBeaconReceive | 1.3.6.1.2.1.10.9.5.1.11 | INTEGER | read-only | The time-out value which determines how long a station shall receive Beacon frames from its downstream neighbor before entering the Bypass state, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers. |
RFC description
RFC 1231 defines the IEEE 802.5 Token Ring MIB for managing Token Ring network interfaces, including statistics, timers, and interface parameters (obsoleted by RFC 1743/1748).
Start monitoring vendor-neutral, standards-based MIB, IEEE 802.5 Token Ring network interface/adapter, bridge or router 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.