All MIBs › ATM-TC-MIB
Organization: IETF AToMMIB Working Group
Last Updated: 1998-10-19
Category: ATM, Network Interfaces, Textual Conventions and Registries
Description:
Provides textual conventions and OBJECT-IDENTITY definitions used by MIB modules for managing ATM-based interfaces, devices, networks, and services.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| TimeTicks | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is ATM-TC-MIB?
ATM-TC-MIB is a textual-conventions module in the ATM (Asynchronous Transfer Mode) networking MIB family, providing shared data types and OBJECT-IDENTITY definitions rather than device-specific runtime data. It doesn't expose monitorable counters itself; instead it defines conventions like traffic descriptor types that other ATM MIBs (e.g. ATM-MIB, ATM2-MIB) reference to describe virtual circuits, cell rates, and QoS classes on ATM interfaces. Because it is purely a support module, it has no direct role in exposing hardware/software health data such as uptime or temperature; it underpins the data types used by the ATM MIBs that do report that information. As the ATM-TC-MIB MIB file, it depends heavily on SNMPv2-SMI and SNMPv2-TC and is designed to be imported by other ATM-related MIB modules. It is typically deployed alongside carrier-grade ATM switches, routers with ATM interfaces, and DSL/telco access equipment.
IPNetwork Monitor allows you to monitor SNMP objects defined in ATM-TC-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, not tied to a specific manufacturer
- ATM switches and routers
- ATM-capable network interfaces
Monitoring Examples
As a TC-only module, ATM-TC-MIB does not define runtime data objects that would be polled directly for monitoring; its only sample object, atmTrafficDescriptorTypes, is an OBJECT-IDENTITY registry of traffic descriptor type identifiers used by other MIBs. Actual monitoring of ATM VCs, cell counts, or PVC status happens through MIBs like ATM-MIB that import these conventions. There is no realistic standalone monitoring scenario for this module.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| atmTrafficDescriptorTypes | 1.3.6.1.2.1.37.1.1 | |||
| atmNoTrafficDescriptor | 1.3.6.1.2.1.37.1.1.1 | This identifies the no ATM traffic descriptor type. Parameters 1, 2, 3, 4, and 5 are not used. This traffic descriptor type can be used for best effort traffic. | ||
| atmNoClpNoScr | 1.3.6.1.2.1.37.1.1.2 | This traffic descriptor type is for no CLP and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: not used Parameter 3: not used Parameter 4: not used Parameter 5: not used. | ||
| atmClpNoTaggingNoScr | 1.3.6.1.2.1.37.1.1.3 | This traffic descriptor is for CLP without tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: peak cell rate in cells/second for CLP=0 traffic Parameter 3: not used Parameter 4: not used Parameter 5: not used. | ||
| atmClpTaggingNoScr | 1.3.6.1.2.1.37.1.1.4 | This traffic descriptor is for CLP with tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: peak cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: not used Parameter 4: not used Parameter 5: not used. | ||
| atmNoClpScr | 1.3.6.1.2.1.37.1.1.5 | This traffic descriptor type is for no CLP with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: not used Parameter 5: not used. | ||
| atmClpNoTaggingScr | 1.3.6.1.2.1.37.1.1.6 | This traffic descriptor type is for CLP with Sustained Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic Parameter 3: maximum burst size in cells Parameter 4: not used Parameter 5: not used. | ||
| atmClpTaggingScr | 1.3.6.1.2.1.37.1.1.7 | This traffic descriptor type is for CLP with tagging and Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: maximum burst size in cells Parameter 4: not used Parameter 5: not used. | ||
| atmClpNoTaggingMcr | 1.3.6.1.2.1.37.1.1.8 | This traffic descriptor type is for CLP with Minimum Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: minimum cell rate in cells/second Parameter 4: unused Parameter 5: unused. | ||
| atmClpTransparentNoScr | 1.3.6.1.2.1.37.1.1.9 | This traffic descriptor type is for the CLP- transparent model and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type is applicable to connections following the CBR.1 conformance definition. Connections specifying this traffic descriptor type will be rejected at UNI 3.0 or UNI 3.1 interfaces. For a similar traffic descriptor type that can be accepted at UNI 3.0 and UNI 3.1 interfaces, see atmNoClpNoScr. | ||
| atmClpTransparentScr | 1.3.6.1.2.1.37.1.1.10 | This traffic descriptor type is for the CLP- transparent model with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to connections following the VBR.1 conformance definition. Connections specifying this traffic descriptor type will be rejected at UNI 3.0 or UNI 3.1 interfaces. For a similar traffic descriptor type that can be accepted at UNI 3.0 and UNI 3.1 interfaces, see atmNoClpScr. | ||
| atmNoClpTaggingNoScr | 1.3.6.1.2.1.37.1.1.11 | This traffic descriptor type is for no CLP with tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type is applicable to connections following the UBR.2 conformance definition . | ||
| atmNoClpNoScrCdvt | 1.3.6.1.2.1.37.1.1.12 | This traffic descriptor type is for no CLP and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type is applicable to CBR connections following the UNI 3.0/3.1 conformance definition for PCR CLP=0+1. These CBR connections differ from CBR.1 connections in that the CLR objective applies only to the CLP=0 cell flow. This traffic descriptor type is also applicable to connections following the UBR.1 conformance definition. | ||
| atmNoClpScrCdvt | 1.3.6.1.2.1.37.1.1.13 | This traffic descriptor type is for no CLP with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to VBR connections following the UNI 3.0/3.1 conformance definition for PCR CLP=0+1 and SCR CLP=0+1. These VBR connections differ from VBR.1 connections in that the CLR objective applies only to the CLP=0 cell flow. | ||
| atmClpNoTaggingScrCdvt | 1.3.6.1.2.1.37.1.1.14 | This traffic descriptor type is for CLP with Sustained Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to connections following the VBR.2 conformance definition. | ||
| atmClpTaggingScrCdvt | 1.3.6.1.2.1.37.1.1.15 | This traffic descriptor type is for CLP with tagging and Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to connections following the VBR.3 conformance definition. | ||
| atmTCMIB | 1.3.6.1.2.1.37.3 | This MIB Module provides Textual Conventions and OBJECT-IDENTITY Objects to be used by ATM systems. | ||
| atmObjectIdentities | 1.3.6.1.2.1.37.3.1 |
RFC description
IETF standard MIB (RFC 2514) providing textual conventions and object identities for ATM management objects.
Start monitoring ATM switches and ATM-capable network interfaces 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.