CHIPDOT5-MIB

All MIBs › CHIPDOT5-MIB

Category: SNA and Legacy Protocols, Vendor: 3Com

Description: Provides Chipcom (3Com) extensions to IEEE 802.5 Token Ring interface management for ring-based campus networks.

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

CHIPDOT5-MIB provides Chipcom (3Com) vendor extensions to IEEE 802.5 Token Ring interface management, supplementing the standard dot5 MIB objects for ring-based campus network equipment. It exposes a dot5Table indexed by dot5IfIndex covering ring status, ring open status, ring speed, upstream neighbor, active-monitor participation, and functional address configuration, plus dot5Commands for issuing ring control actions and a dot5StatsTable for ring statistics. This MIB is used to monitor the hardware/link status of Token Ring interfaces: whether a ring segment is open or closed (dot5RingOpenStatus), its current operating state (dot5RingState/dot5RingStatus), configured versus actual ring speed, and whether the local station is participating as active monitor, which together reveal ring health and topology problems. It directly extends the standard IEEE 802.5-based dot5 MIB (RFC 1231) conventions, layering Chipcom-specific objects onto the standard Token Ring interface model. It was deployed in enterprise campus networks using Chipcom (3Com) Token Ring hubs/concentrators in the 1990s. Engineers can download the CHIPDOT5-MIB file directly to load it into their MIB browser.

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

Chipcom (3Com) Token Ring hub/concentrator

Monitoring Examples

An operator polls dot5Table entries by dot5IfIndex to check dot5RingStatus and dot5RingOpenStatus, confirming whether a given Token Ring port's ring is closed (normal) or open (a break/fault); dot5RingSpeed confirms the port is running at the expected 4 or 16 Mbps. dot5ActMonParticipate shows whether the station is acting as active monitor, and a ring that keeps losing its active monitor or repeatedly reports open status suggests a cabling fault or a failing station causing ring beaconing. dot5StatsTable would then provide counters (e.g., line errors, burst errors) an admin could examine to pinpoint which station segment is generating the faults.

What Can Be Monitored

ring status and open status
ring speed
active monitor participation
upstream neighbor
ring statistics
functional address configuration

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
DisplayString
Gauge
IpAddress
NetworkAddress
TimeTicks
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
alarmGroup	1.3.6.1.4.1.49.2.3.4.7
boardGroup	1.3.6.1.4.1.49.2.3.4.5
chipBridge	1.3.6.1.4.1.49.2.3.6
chipcom	1.3.6.1.4.1.49
chipDownload	1.3.6.1.4.1.49.2.7
chipEcho	1.3.6.1.4.1.49.2.2
chipExperiment	1.3.6.1.4.1.49.2.4
chipExpTokenRing	1.3.6.1.4.1.49.2.4.1
chipGen	1.3.6.1.4.1.49.2.1
chipmib02	1.3.6.1.4.1.49.2
chipProducts	1.3.6.1.4.1.49.2.3
chipSetIBM16	1.3.6.1.4.1.49.2.4.1.1.4.1
chipSetTItms380	1.3.6.1.4.1.49.2.4.1.1.4.2
chipSetTItms380c16	1.3.6.1.4.1.49.2.4.1.1.4.3
chipTFTP	1.3.6.1.4.1.49.2.6
chipTTY	1.3.6.1.4.1.49.2.5
dot1dBridge	1.3.6.1.4.1.49.2.4.14
dot5	1.3.6.1.4.1.49.2.4.1.1
INT dot5ActMonParticipate	1.3.6.1.4.1.49.2.4.1.1.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.
dot5ChipSets	1.3.6.1.4.1.49.2.4.1.1.4
INT dot5Commands	1.3.6.1.4.1.49.2.4.1.1.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).
dot5Entry	1.3.6.1.4.1.49.2.4.1.1.1.1		not-accessible	A list of Token Ring status and parameter values for an 802.5 interface.
MAC dot5Functional	1.3.6.1.4.1.49.2.4.1.1.1.1.9	MacAddress	read-write	The bit mask of all Token Ring functional addresses for which this interface will accept frames.
INT dot5IfIndex	1.3.6.1.4.1.49.2.4.1.1.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 dot5RingOpenStatus	1.3.6.1.4.1.49.2.4.1.1.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.4.1.49.2.4.1.1.1.1.6	INTEGER	read-write	The ring's bandwidth.
INT dot5RingState	1.3.6.1.4.1.49.2.4.1.1.1.1.4	INTEGER	read-only	The current interface state with respect to entering or leaving the ring.
INT dot5RingStatus	1.3.6.1.4.1.49.2.4.1.1.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.
CTR dot5StatsAbortTransErrors	1.3.6.1.4.1.49.2.4.1.1.2.1.5	Counter	read-only	This counter is incremented when a station transmits an abort delimiter while transmitting.
CTR dot5StatsACErrors	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsBurstErrors	1.3.6.1.4.1.49.2.4.1.1.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).
dot5StatsEntry	1.3.6.1.4.1.49.2.4.1.1.2.1		not-accessible	An entry contains the 802.5 statistics for a particular interface.
CTR dot5StatsFrameCopiedErrors	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsFreqErrors	1.3.6.1.4.1.49.2.4.1.1.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 ispecified by the IEEE 802.5 standard, see chapter 7 in [10].
CTR dot5StatsHardErrors	1.3.6.1.4.1.49.2.4.1.1.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.
INT dot5StatsIfIndex	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsInternalErrors	1.3.6.1.4.1.49.2.4.1.1.2.1.6	Counter	read-only	This counter is incremented when a station recognizes an internal error.
CTR dot5StatsLineErrors	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsLobeWires	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsLostFrameErrors	1.3.6.1.4.1.49.2.4.1.1.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.4.1.49.2.4.1.1.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 dot5StatsRecoverys	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsRemoves	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsSignalLoss	1.3.6.1.4.1.49.2.4.1.1.2.1.13	Counter	read-only	The number of times this interface has detected the loss of signal condition from the ring.
CTR dot5StatsSingles	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsSoftErrors	1.3.6.1.4.1.49.2.4.1.1.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.
dot5StatsTable	1.3.6.1.4.1.49.2.4.1.1.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.
CTR dot5StatsTokenErrors	1.3.6.1.4.1.49.2.4.1.1.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 dot5StatsTransmitBeacons	1.3.6.1.4.1.49.2.4.1.1.2.1.14	Counter	read-only	The number of times this interface has transmitted a beacon frame.
dot5Table	1.3.6.1.4.1.49.2.4.1.1.1		not-accessible	This table contains Token Ring interface parameters and state variables, one entry per 802.5 interface.
dot5Tests	1.3.6.1.4.1.49.2.4.1.1.3
INT dot5TimerActiveMon	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerBeaconReceive	1.3.6.1.4.1.49.2.4.1.1.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.
INT dot5TimerBeaconTransmit	1.3.6.1.4.1.49.2.4.1.1.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.
dot5TimerEntry	1.3.6.1.4.1.49.2.4.1.1.5.1		not-accessible	A list of Token Ring timer values for an 802.5 interface.
INT dot5TimerErrorReport	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerHolding	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerIfIndex	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerNoToken	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerQueuePDU	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerReturnRepeat	1.3.6.1.4.1.49.2.4.1.1.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 dot5TimerStandbyMon	1.3.6.1.4.1.49.2.4.1.1.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.
dot5TimerTable	1.3.6.1.4.1.49.2.4.1.1.5		not-accessible	This table contains Token Ring interface timer values, one entry per 802.5 interface.
INT dot5TimerValidTransmit	1.3.6.1.4.1.49.2.4.1.1.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.
MAC dot5UpStream	1.3.6.1.4.1.49.2.4.1.1.1.1.7	MacAddress	read-only	The MAC-address of the up stream neighbor station in the ring.
emm	1.3.6.1.4.1.49.2.3.5
fmm	1.3.6.1.4.1.49.2.3.8
focus1	1.3.6.1.4.1.49.2.3.9
hardwareGroup	1.3.6.1.4.1.49.2.3.4.2
hubGroup	1.3.6.1.4.1.49.2.3.4.4
hubSysGroup	1.3.6.1.4.1.49.2.3.4.1
midnight	1.3.6.1.4.1.49.2.3.3
oebm	1.3.6.1.4.1.49.2.3.2
oeim	1.3.6.1.4.1.49.2.3.10
ol50nnMCTL	1.3.6.1.4.1.49.2.3.1.4.4.3
ol50nnMHCTL	1.3.6.1.4.1.49.2.3.1.4.4.33
ol50nnMRCTL	1.3.6.1.4.1.49.2.3.1.4.4.23
ol51nnBEE	1.3.6.1.4.1.49.2.3.1.4.4.9
ol51nnIx	1.3.6.1.4.1.49.2.3.1.4.4.31
ol51nnMAUIF	1.3.6.1.4.1.49.2.3.1.4.4.12
ol51nnMAUIM	1.3.6.1.4.1.49.2.3.1.4.4.13
ol51nnMBNC	1.3.6.1.4.1.49.2.3.1.4.4.8
ol51nnMFB	1.3.6.1.4.1.49.2.3.1.4.4.24
ol51nnMFBP	1.3.6.1.4.1.49.2.3.1.4.4.16
ol51nnMFIB	1.3.6.1.4.1.49.2.3.1.4.4.5
ol51nnMFL	1.3.6.1.4.1.49.2.3.1.4.4.22
ol51nnMFP	1.3.6.1.4.1.49.2.3.1.4.4.15
ol51nnMMGT	1.3.6.1.4.1.49.2.3.1.4.4.4
ol51nnMTP	1.3.6.1.4.1.49.2.3.1.4.4.7
ol51nnMTPCL	1.3.6.1.4.1.49.2.3.1.4.4.29
ol51nnMTPL	1.3.6.1.4.1.49.2.3.1.4.4.17
ol51nnMTPPL	1.3.6.1.4.1.49.2.3.1.4.4.18
ol51nnMTS	1.3.6.1.4.1.49.2.3.1.4.4.21
ol51nnMUTP	1.3.6.1.4.1.49.2.3.1.4.4.6
ol51nnREE	1.3.6.1.4.1.49.2.3.1.4.4.11
ol51nnRES	1.3.6.1.4.1.49.2.3.1.4.4.10
ol5208MTP	1.3.6.1.4.1.49.2.3.1.4.4.14
ol52nnBTT	1.3.6.1.4.1.49.2.3.1.4.4.30
ol52nnMFR	1.3.6.1.4.1.49.2.3.1.4.4.20
ol52nnMMGT	1.3.6.1.4.1.49.2.3.1.4.4.32
ol52nnMTP	1.3.6.1.4.1.49.2.3.1.4.4.19
ol53nnMFBMIC	1.3.6.1.4.1.49.2.3.1.4.4.26
ol53nnMFIBST	1.3.6.1.4.1.49.2.3.1.4.4.27
ol53nnMMGT	1.3.6.1.4.1.49.2.3.1.4.4.25
ol53nnMSTP	1.3.6.1.4.1.49.2.3.1.4.4.28
olAgents	1.3.6.1.4.1.49.2.3.1.1
olAlarm	1.3.6.1.4.1.49.2.3.1.7
olConc	1.3.6.1.4.1.49.2.3.1.2
olEnet	1.3.6.1.4.1.49.2.3.1.5.2
olEnv	1.3.6.1.4.1.49.2.3.1.3
olFDDInet	1.3.6.1.4.1.49.2.3.1.5.4
olGroups	1.3.6.1.4.1.49.2.3.1.6
olModules	1.3.6.1.4.1.49.2.3.1.4
olNet	1.3.6.1.4.1.49.2.3.1.5.1
olNets	1.3.6.1.4.1.49.2.3.1.5
olSpecMods	1.3.6.1.4.1.49.2.3.1.4.4
olThresh	1.3.6.1.4.1.49.2.3.1.7.1
olThreshControl	1.3.6.1.4.1.49.2.3.1.7.1.1
olTRnet	1.3.6.1.4.1.49.2.3.1.5.3
online	1.3.6.1.4.1.49.2.3.1
portGroup	1.3.6.1.4.1.49.2.3.4.6
softwareGroup	1.3.6.1.4.1.49.2.3.4.3
testInsertFunc	1.3.6.1.4.1.49.2.4.1.1.3.1
trmm	1.3.6.1.4.1.49.2.3.7
workGroupHub	1.3.6.1.4.1.49.2.3.4

RFC description

Chipcom Token Ring management MIB for bridges and interconnect modules, defining switch and port configuration objects.

Start monitoring Chipcom (3Com) Token Ring hub/concentrator (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.

Download CHIPDOT5-MIB

What Is CHIPDOT5-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description