TCAv2-MIB: View SNMP OID List / Download MIB

VENDOR: BELLCORE


 Home MIB: TCAv2-MIB
Download as:   

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
 bellcore 1.3.6.1.4.1.148
         requirements 1.3.6.1.4.1.148.1
             tcaMIB 1.3.6.1.4.1.148.1.5
                 tcaObjects 1.3.6.1.4.1.148.1.5.1
                     tcaTable 1.3.6.1.4.1.148.1.5.1.1 no-access
The Threshold Crossing Alert table.
                         tcaEntry 1.3.6.1.4.1.148.1.5.1.1.1 no-access
An entry in the Threshold Crossing Alert table.
                             tcaIfIndex 1.3.6.1.4.1.148.1.5.1.1.1.1 integer no-access
The value of this object is equal to MIB II's ifIndex value for this interface sublayer (ifEntry).
                             tcaIndex 1.3.6.1.4.1.148.1.5.1.1.1.2 integer no-access
The value of this object is used as one of the indices for this table. It is a unique identifier for this row in the table for this interface (ifIndex). The value of this object can be from 1 to N, where N is the number of potential TCAs for this interface sublayer (ifEntry).
                             tcaObject 1.3.6.1.4.1.148.1.5.1.1.1.3 object identifier read-only
The value of this object is the OBJECT IDENTIFIER of the counter object being thresholded. The counter objects being thresholded are defined in other MIB Modules.
                             tcaObjectDesc 1.3.6.1.4.1.148.1.5.1.1.1.4 displaystring read-only
The value of this object is a description of the counter object being thresholded. For example, DS1 Coding Violations.
                             tcaThreshold 1.3.6.1.4.1.148.1.5.1.1.1.5 integer read-only
The value of this object is the threshold value of the counter object being thresholded.
                             tcaSampleType 1.3.6.1.4.1.148.1.5.1.1.1.6 integer read-only
The value of this object is the sample type of the object being thresholded from the perspective of the CNM or XA-OM customer. This object can be used for the following data types: (a) Counters (b) Counters measured over certain intervals, where the Counters are reset to zero at the end of the interval and as a result have the syntax Gauge. (c) Gauges (other than (b)) (d) (Enumerated) INTEGER (e) (Enumerated) INTEGER that is used as a bitmap. The enumerated values of this object apply to these data types as follows: | possible values | data type | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | --------------------+---+---+---+---+---+---+---+---+ (a) Counter | | X | | | | | | | (b) IntervalCounter | X | | | | | | | | (c) Gauge | | | X | X | | | | | (d) Enum INT | | | | | X | X | | | (e) Enum INT(bitmap)| | | | | | | X | X | --------------------+---+---+---+---+---+---+---+---+ (a) Counter values can only rise. An alarm may be triggered when the value has risen a delta amount within a sample period. (b) IntervalCounter values can only rise within an interval and are reset at the end of the interval. An alarm may be triggered when the value has exceeded an absolute value. (c) A Gauge value may rise and fall. An alarm may be triggered when the value has risen or fallen a certain amount. (d) An INTEGER may assume values in any sequence. An alarm may be triggered when the value does equal or doesnot equal a certain specified value. (e) A bitmap may assume values that represent one or more bits to be set. An alarm may be triggered when the value does include or not include the combined value of certain bits. Note that for (c), (d), and (e) only one alarm needs to be generated, i.e., at first detection of this event. Enumeration: 'intervalNotAtValueAlarm': 6, 'intervalDeltaValue': 2, 'intervalAbsoluteValue': 1, 'intervalIncludesNotValue': 8, 'intervalRisingAlarm': 4, 'intervalAtValueAlarm': 5, 'intervalIncludesValue': 7, 'intervalFallingAlarm': 3.
                             tcaCounts 1.3.6.1.4.1.148.1.5.1.1.1.7 counter read-only
The value of this object is the number of times the threshold was crossed for this counter object, since sysUpTime was initialized or restarted. This counter is a continuous counter. It should be noted that as this object has a SYNTAX of Counter, that it does not have a defined initial value. However, it is recommended that this object be initialized to zero.
                             tcaTimeStamp 1.3.6.1.4.1.148.1.5.1.1.1.8 timestamp read-only
The value of this object is equal to the value of MIB-II's sysUpTime object at which last (latest) threshold was crossed for this counter object. The value of this object is set to zero at (re)initialization.
                             tcaTrapEnabler 1.3.6.1.4.1.148.1.5.1.1.1.9 integer read-write
Indicates whether fyiTraps should be generated for this threshold crossing count (tcaObject). The physical layer counters' and gauges' (e.g., DS1, DS3, SONET, and PLCP) TCAs should have a default value of disabled(2). The SMDS service violations and higher layer protocol violations counters' TCAs should have a default value of enabled(1). A fyiTrap, when generated, shall have the following varBind list: tcaObject, tcaObjectDesc, tcaThreshold, and tcaTimeStamp. Enumeration: 'disabled': 2, 'enabled': 1.
                 tcaConformance 1.3.6.1.4.1.148.1.5.2
                     tcaGroups 1.3.6.1.4.1.148.1.5.2.1
                         tcaGroup 1.3.6.1.4.1.148.1.5.2.1.1
                     tcaCompliances 1.3.6.1.4.1.148.1.5.2.2
                         tcaCompliance 1.3.6.1.4.1.148.1.5.2.2.1