CXTokenBus-MIB: View SNMP OID List / Download MIB

VENDOR: MEMOTEC COMMUNICATIONS


 Home MIB: CXTokenBus-MIB
Download as:   
SNMPv2-CONF, CXProduct-SMI, SNMPv2-TC, SNMPv2-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 tbSapTable 1.3.6.1.4.1.495.2.1.5.9.1 no-access
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 no-access
The parameters for a particular frame relay module service access point.
         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.
         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) Enumeration: 'valid': 2, 'invalid': 1.
         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.
         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.
         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 Enumeration: 'upper': 2.
         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. Enumeration: 'disabled': 1, 'enabled': 2.
         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.
         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.
         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.
         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.
         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.
         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.
         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.
         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
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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
     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
     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
     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
     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
     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
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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).
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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.
     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).
     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.
     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.