TCAv2-MIB

All MIBs › TCAv2-MIB

Description: TCAv2-MIB module

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

TCAv2-MIB is Bellcore/Telcordia's Threshold Crossing Alert MIB (version 2), a telecom-industry standard that lets a device report configurable performance-threshold crossings against interface- or object-level counters. It exposes a table of monitored objects and thresholds: tcaIfIndex/tcaIndex identify the interface and TCA instance, tcaObject/tcaObjectDesc name the monitored variable, tcaThreshold and tcaSampleType define the crossing condition and sampling method, tcaCounts and tcaTimeStamp record how often and when the threshold was crossed, and tcaTrapEnabler controls whether a trap is fired. Its monitoring purpose is squarely performance/fault-oriented: it lets an operator define thresholds on any interface counter, such as an error rate, and be notified in near real time when a monitored parameter crosses into an abnormal range, rather than having to continuously poll and compute the condition externally. It is designed to layer on top of standard interface/counter MIBs, referencing objects like ifIndex via tcaIfIndex, and Bellcore/Telcordia telecom network-management requirements documents. It is deployed on telecom transport and access equipment where Telcordia-aligned threshold-crossing alerting is required for performance management. Engineers can download the TCAv2-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TCAv2-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 (Bellcore/Telcordia), not tied to a specific manufacturer
telecom transport/access network equipment

Monitoring Examples

An operator would configure a tcaTable entry with tcaIfIndex pointing at a specific interface, tcaObject naming an error counter, and tcaThreshold/tcaSampleType defining an acceptable rate, then rely on tcaTrapEnabler to fire a trap the moment tcaCounts increments, signaling the interface has crossed into a fault condition. tcaTimeStamp would be checked afterward to correlate the crossing event with other logs from around the same time, helping pinpoint what caused the degradation.

What Can Be Monitored

configured threshold-crossing alerts
monitored object/counter per interface
threshold value and sample type
crossing count and timestamp
trap enable/disable per alert

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

From RFC1213-MIB

DisplayString

From SNMPv2-TC

TimeStamp

OIDs

OID symbolic	OID numeric	Type	Access	Description
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		not-accessible	The Threshold Crossing Alert table.
tcaEntry	1.3.6.1.4.1.148.1.5.1.1.1		not-accessible	An entry in the Threshold Crossing Alert table.
INT tcaIfIndex	1.3.6.1.4.1.148.1.5.1.1.1.1	INTEGER	not-accessible	The value of this object is equal to MIB II's ifIndex value for this interface sublayer (ifEntry).
INT tcaIndex	1.3.6.1.4.1.148.1.5.1.1.1.2	INTEGER	not-accessible	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).
OID 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.
STR 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.
INT 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.
INT 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.
CTR 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.
TIM 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.
INT 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.
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

RFC description

Implements Threshold Crossing Alert monitoring and notification for network interface counters and performance metrics.

Start monitoring telecom transport/access network equipment 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 TCAv2-MIB

What Is TCAv2-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description