CXTokenBus-MIB

All MIBs › CXTokenBus-MIB

Category: Technology: Token Ring, Vendor: Memotec

Description: Manages Token Bus (IEEE 802.4) network interface configuration on CX Memotec devices.

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

CXTokenBus-MIB is a Memotec/Aastra CX product MIB for managing IEEE 802.4 Token Bus network interfaces on CX access devices. It exposes SAP table entries, device polling intervals, frame/buffer descriptor counts (transmit and receive), maximum frame sizes per priority class, and token-passing timing parameters such as high-priority token hold time and target rotation time. It supports monitoring of the Token Bus interface's operational health, tracking buffer/frame descriptor exhaustion, polling interval drift, and token rotation timing that, if abnormal, indicate congestion or a malfunctioning token-passing station on the bus. It depends on CXProduct-SMI for OID registration and represents a legacy LAN interface type that would coexist with other CX interface MIBs (Ethernet, SDLC) on the same device. It was used on Memotec/Aastra CX equipment supporting IEEE 802.4 Token Bus LANs, a technology common in certain manufacturing/process-control network environments of the era. Network engineers evaluating or troubleshooting this functionality can download the CXTokenBus-MIB file directly to load it into their MIB browser.

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

Memotec/Aastra CX device with IEEE 802.4 Token Bus interface

Monitoring Examples

An operator can poll tbRxFrameDescriptors and tbRxBufferDescriptors alongside tbTxFrameDescriptors/tbTxBufferDescriptors to check whether the device is running low on receive or transmit buffers, which would manifest as dropped frames under load. Checking tbHiPriorityTokenHoldTime and tbTargetRotationTimeClass4 against configured baselines helps confirm the token bus is rotating within expected timing bounds; excessive rotation time suggests a station holding the token too long. The tbSapTable lets an administrator verify configured SAP bindings for upper-layer protocols riding over the Token Bus interface.

What Can Be Monitored

frame/buffer descriptor availability
token hold time
target token rotation time
device polling interval
SAP configuration

Imported Objects

From CXProduct-SMI

Alias
SapIndex
cxTokenBus	OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

OIDs

OID symbolic	OID numeric	Type	Access	Description
tbSapTable	1.3.6.1.4.1.495.2.1.5.9.1		not-accessible	A table containing configuration information about each LLC service access point.
tbSapEntry	1.3.6.1.4.1.495.2.1.5.9.1.1		not-accessible	The parameters for a particular frame relay module service access point.
SAP tbSapNumber	1.3.6.1.4.1.495.2.1.5.9.1.1.1	SapIndex	read-only	This object serves to identify the service access point by a numerical value.
INT tbSapRowStatus	1.3.6.1.4.1.495.2.1.5.9.1.1.2	INTEGER	read-write	Indicates whether the particular service access point is configured within the MIB. Service access point entries (rows) may be created by setting this object value to 'valid', or deleted by changing this object value to 'invalid'. Options: invalid (1) valid (2)
ALI tbSapAlias	1.3.6.1.4.1.495.2.1.5.9.1.1.3	Alias	read-write	Identifies the service access point by a textual name. Names are unique per service access point.
ALI tbSapCompanionAlias	1.3.6.1.4.1.495.2.1.5.9.1.1.4	Alias	read-write	Identifies the remote service access point that will communicate with this service access point by a textual name. Names are unique per service access point.
INT tbSapType	1.3.6.1.4.1.495.2.1.5.9.1.1.5	INTEGER	read-write	This object serves to identify the service access point by type: 'lower' or 'upper'. In our case, only upper is relevent but this object is kept for uniformity with the other Sap definition in the system
INT tbSapStatGathering	1.3.6.1.4.1.495.2.1.5.9.1.1.6	INTEGER	read-write	This object specifies if the SAP statistics will be updated. If disabled, the counter will always be zero.
CTR tbSapStatRxUnitDataFrames	1.3.6.1.4.1.495.2.1.5.9.1.1.7	Counter	read-only	Indicates the number of data frames received from the upper layer which requested no acknowledgment from the destination token bus module.
CTR tbSapStatRxUnitDataOctets	1.3.6.1.4.1.495.2.1.5.9.1.1.8	Counter	read-only	Indicates the number of data octets received from the upper layer which requested no acknowledgment from the destination token bus module.
CTR tbSapStatRxDataAckFrames	1.3.6.1.4.1.495.2.1.5.9.1.1.9	Counter	read-only	Indicates the number of data frames received from the upper layer which requested an acknowledgment from the destination token bus module.
CTR tbSapStatRxDataAckOctets	1.3.6.1.4.1.495.2.1.5.9.1.1.10	Counter	read-only	Indicates the number of data octets received from the upper layer which requested an acknowledgment from the destination token bus module.
CTR tbSapStatTxUnitDataFrames	1.3.6.1.4.1.495.2.1.5.9.1.1.11	Counter	read-only	Indicates the number of data frames sent to the upper layer where the originating card did not request an acknowledgment.
CTR tbSapStatTxUnitDataOctets	1.3.6.1.4.1.495.2.1.5.9.1.1.12	Counter	read-only	Indicates the number of data octets sent to the upper layer where the originating card did not request an acknowledgment.
CTR tbSapStatTxDataAckFrames	1.3.6.1.4.1.495.2.1.5.9.1.1.13	Counter	read-only	Indicates the number of data frames sent to the upper layer where the originating card requested an acknowledgment.
CTR tbSapStatTxDataAckOctets	1.3.6.1.4.1.495.2.1.5.9.1.1.14	Counter	read-only	Indicates the number of data octets sent to the upper layer where the originating card requested an acknowledgment.
tbDevice	1.3.6.1.4.1.495.2.1.5.9.2
INT tbDevPollingInterval	1.3.6.1.4.1.495.2.1.5.9.2.1	INTEGER	read-write	This determine how often the Token Bus Device will be polled for transmission completion and frame reception. This value is in millisecond. If this value is 0, the token bus module is waiting for an external polling message. This is the case in special test software only.
INT tbRxFrameDescriptors	1.3.6.1.4.1.495.2.1.5.9.2.2	INTEGER	read-write	Number of frame descriptors allocated to the token bus device (MC68824) to perform the receive process.
INT tbRxBufferDescriptors	1.3.6.1.4.1.495.2.1.5.9.2.3	INTEGER	read-write	Number of buffer descriptors allocated to the token bus device (MC68824) to perform the receive process.
INT tbTxFrameDescriptors	1.3.6.1.4.1.495.2.1.5.9.2.4	INTEGER	read-write	Number of frame descriptors allocated to the token bus device (MC68824) to perform the transmission process.
INT tbTxBufferDescriptors	1.3.6.1.4.1.495.2.1.5.9.2.5	INTEGER	read-write	Number of buffer descriptors allocated to the token bus device (MC68824) to perform the transmission process.
INT tbMaxFrameSizeClass6	1.3.6.1.4.1.495.2.1.5.9.2.6	INTEGER	read-write	Maximum frame size permit to be transmitted at the access class 6. This maximum must be enforced to guaranty the maximum token rotation time specified above.
INT tbMaxFrameSizeClass4	1.3.6.1.4.1.495.2.1.5.9.2.7	INTEGER	read-write	Maximum frame size permit to be transmitted at the access class 4.
INT tbMaxFrameSizeClass2	1.3.6.1.4.1.495.2.1.5.9.2.8	INTEGER	read-write	Maximum frame size permit to be transmitted at the access class 2.
INT tbMaxFrameSizeClass0	1.3.6.1.4.1.495.2.1.5.9.2.9	INTEGER	read-write	Maximum frame size permit to be transmitted at the access class 0.
INT tbHiPriorityTokenHoldTime	1.3.6.1.4.1.495.2.1.5.9.2.10	INTEGER	read-write	Maximum time a station can hold the token to transmit frame at the highest priority (access class 6). The value to configure may be calculated with this formula: tbHiPriorityTokenHoldTime=(target rotation time(sec)) * Bus Clock frequency ------------------------------------------------- number of card * 64
INT tbTargetRotationTimeClass4	1.3.6.1.4.1.495.2.1.5.9.2.11	INTEGER	read-write	This parameter defines the target rotation time for the access class 4. The value to configure may be calculated with this formula: tbTargetRotationTimeClass4=(target rotation time(sec)) * Bus Clock frequency ------------------------------------------------- 64
INT tbTargetRotationTimeClass2	1.3.6.1.4.1.495.2.1.5.9.2.12	INTEGER	read-write	This parameter defines the target rotation time for the access class 2. The value to configure may be calculated with this formula: tbTargetRotationTimeClass2=(target rotation time(sec)) * Bus Clock frequency ------------------------------------------------ 64
INT tbTargetRotationTimeClass0	1.3.6.1.4.1.495.2.1.5.9.2.13	INTEGER	read-write	This parameter defines the target rotation time for the access class 0. The value to configure may be calculated with this formula: tbTargetRotationTimeClass0=(target rotation time(sec)) * Bus Clock frequency ------------------------------------------------- 64
INT tbTargetRotationForMaintenance	1.3.6.1.4.1.495.2.1.5.9.2.14	INTEGER	read-write	This parameter defines the target rotation time for the ring maintenance. The value to configure may be calculated with this formula: tbTargetRotationorMaintenance = target rotation time(sec)) * Bus Clock frequency ------------------------------------------------ 64
INT tbMaxInterSolicitCount	1.3.6.1.4.1.495.2.1.5.9.2.15	INTEGER	read-write	This parameter defines the target rotation time for the ring maintenance. The value to configure may be calculated with this formula: tbTimeForMaintenance = (target rotation time(sec)) * Bus Clock frequency ------------------------------------------------- 64
INT tbNonRwrMaxRetryLimit	1.3.6.1.4.1.495.2.1.5.9.2.16	INTEGER	read-write	This parameter specifies how many times the MC68824 chip set will try to retransmit a request with no response (RWNR) frame on which it detected a transmission failure.
INT tbRwrMaxRetryLimit	1.3.6.1.4.1.495.2.1.5.9.2.17	INTEGER	read-write	This parameter specifies how many time the MC68824 chip set will try to retransmit a request with response (RWR) frame on which it detected a transmission failure through a lack of response.
INT tbSlotTime	1.3.6.1.4.1.495.2.1.5.9.2.18	INTEGER	read-write	This parameter specifies how much time the MC68824 chip set will wait for a response on a transmission a request with response (RWR) frame. This parameter must be specified in octet time.
CTR tbTxNonRwrFailures	1.3.6.1.4.1.495.2.1.5.9.2.19	Counter	read-only	Number of transmission failures related to the request with no response frames.
CTR tbTxRwrFailures	1.3.6.1.4.1.495.2.1.5.9.2.20	Counter	read-only	Number of transmission failure related to the request with response frames.
CTR tbUnexpectedFrame6s	1.3.6.1.4.1.495.2.1.5.9.2.21	Counter	read-only	This counter incrementes when the TBC hears an unexpected frame when expecting a response to a transmitted request with response frame. An unexpected frame in this case is any valid frame which is not a response frame addressed to this station. Upon detecting this event, the TBC increment this counter and goes to the IDLE without passing the token.
CTR tbUnexpectedFrame10s	1.3.6.1.4.1.495.2.1.5.9.2.22	Counter	read-only	The TBC module incremented this counter when it executes the 'unexpected frame 10' transition the IEEE 802.4 access control machine (ACM). It occurs when the TBC attempted to solicit a new successor and while waiting for a response, heard either a data frame not sent by itself. When this event occurs, it indicates a protocol error, possibly a duplicate token situation. After this event, The TBC will go to the IDLE without passing the token.
CTR tbNbUnderruns	1.3.6.1.4.1.495.2.1.5.9.2.23	Counter	read-only	This statistic represents the number of times the TBC detected a FIFO underrun during transmission.
CTR tbRxRetryRwrFrames	1.3.6.1.4.1.495.2.1.5.9.2.24	Counter	read-only	Number of detected retransmitted request with response frame. This event mostly occurs when the RWR frame or its response is lost.
CTR tbRxNullLsduRwrFrames	1.3.6.1.4.1.495.2.1.5.9.2.25	Counter	read-only	Number of received request with response frame which did not contain any LLC service data unit (LDSU).
CTR tbNbPassedTokens	1.3.6.1.4.1.495.2.1.5.9.2.26	Counter	read-only	Number of time this station thinks it has sucessfully passed the token. It can be used to calculate the average token rotation time.
CTR tbNbHeardTokens	1.3.6.1.4.1.495.2.1.5.9.2.27	Counter	read-only	Number of time this station heard a token where Destination Address (DA) or Source Address (SA) are not equal to This Station (TS) address. This number can be used to determine how many stations there is on the logical ring.
CTR tbNbNoSuccessor8Passes	1.3.6.1.4.1.495.2.1.5.9.2.28	Counter	read-only	This statistic indicates the number of times this station has gone through the no successor 8 arc in the state machine. This happens when the TBC fails to pass the token and does not succeed in finding a new successor station. The counter is incremented only if the TBC thinks it is not the only active station in the network. A significantly large value in this counter may indicate a 'faulty' transmitter condition in this station.
CTR tbNbWhoFollowsFrames	1.3.6.1.4.1.495.2.1.5.9.2.29	Counter	read-only	This statistic is the number of times this station has had to look for a new next station to pass the token to. This frame is sent as part of the TBC's effort to pass the token to its former successor's successor if the original successor station does not respond to the token. This counter is incremented by two every time a failure occurs.
CTR tbNbTokenPassFailures	1.3.6.1.4.1.495.2.1.5.9.2.30	Counter	read-only	This statistic indicates the number of token pass failed transitions when pass state is equal to pass token. Upon failing to pass the token, the TBC tries to send a second token (pass state equals repeat pass token). If this effort fails too, this counter is not incremented again; but the TBC will then send a who follows frame and the who follows query counter will be incremented.
CTR tbRxPeriodNonSilences	1.3.6.1.4.1.495.2.1.5.9.2.31	Counter	read-only	This statistic is the number of received periods of non-silence.
CTR tbRxBadCrcFrames	1.3.6.1.4.1.495.2.1.5.9.2.32	Counter	read-only	This statistic tracks the number of received frames with FCS (or CRC) errors and the E-bit reset.
CTR tbRxEBitSetFrames	1.3.6.1.4.1.495.2.1.5.9.2.33	Counter	read-only	This statistic counts the number of received frames with the E-bit set in the end delimiter. The E bit, or error bit, is set by the regenerative repeater (headend remodulator), when the headend detects a FCS error on the forward channel.
CTR tbRxFrameFragments	1.3.6.1.4.1.495.2.1.5.9.2.34	Counter	read-only	This statistic represents the number of frame fragments (start delimiter (SD) not followed by a valid end delimiter (ED)). A valid frame consists of only data (zero or one MAC symbols) between the SD and the ED. If an SD is detected and then, before a valid ED, the TBC detects either silence, non data (not part of the aligned ED), or bad signal, then this counter is incremented. Note that this includes abort sequences.
CTR tbRxFrameTooLongs	1.3.6.1.4.1.495.2.1.5.9.2.35	Counter	read-only	This statistic is the number of received frames tart are too long (>8 KBytes).
CTR tbNbNoFdBdErrors	1.3.6.1.4.1.495.2.1.5.9.2.36	Counter	read-only	This statistic counts the number of frames that were not received because there were not enough frame descriptors or there were not enough buffers.
CTR tbNbOverruns	1.3.6.1.4.1.495.2.1.5.9.2.37	Counter	read-only	This statistic represents the number of times the TBC detected a FIFO overrun during receive.

RFC description

Token Bus LLC service access point configuration and statistics for Connexta devices.

Start monitoring Memotec/Aastra Token Bus devices 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 CXTokenBus-MIB

What Is CXTokenBus-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description