CISCO-TM

All MIBs › CISCO-TM

Organization: Cisco Systems, Inc.

Last Updated: 2001-08-23

Category: Cisco Devices, MPLS and Traffic Engineering, Routing Protocols

Description: Manages traffic matrix data collection for traffic engineering providing aggregate flow demand measurements across the network.

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 CISCO-TM?

CISCO-TM is a small Cisco support MIB that extends the standard IETF SNMPv2-TM (SNMP Transport Mappings) MIB with additional Cisco-specific transport-address textual conventions, despite a name that might suggest 'traffic matrix' - its module description explicitly states it is an extension of SNMPv2-TM. It does not fall into a data-monitoring category like interfaces, environment, or performance counters; instead it supplies TEXTUAL-CONVENTION type definitions that other Cisco MIBs import to encode transport addresses consistently. Because it defines no scalar or table objects of its own, it plays no direct role in monitoring hardware or software status - no uptime, temperature, CPU, or fault data is carried here, only supporting type definitions used elsewhere. Its one clear, stated dependency is on the IETF-standard SNMPv2-TM MIB, which it extends. It is deployed implicitly, wherever other Cisco MIBs need standardized transport-address encoding, and is not itself polled by network management systems. Engineers can download the CISCO-TM file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-TM. 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 supporting module used across Cisco network devices
not tied to a specific device type

Monitoring Examples

CISCO-TM has no sample objects and defines no runtime data objects of its own (sample_objects is empty) - it is a supporting textual-convention module extending SNMPv2-TM that other Cisco MIBs import, so there is no monitoring scenario to describe for this module directly.

Imported Objects

From CISCO-SMI

ciscoDomains

OBJECT-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-IDENTITY

From SNMPv2-TC

TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Description
ciscoTransportMappings	1.3.6.1.4.1.9.19.1	Extension of SNMPv2-TM MIB
snmpUDPVPNDomain	1.3.6.1.4.1.9.19.1.1	This transport domain is used to specify that particular SNMP messages are to be sent/received over a particular Virtual Private Network (VPN), implemented using MPLS (Multiprotocol Label Switching). The corresponding transport address is of type SnmpUDPVPNAddress. A VPN is defined as a set of sites with a common community of interest. Sites within an MPLS-based VPN often have private addresses which aren't accessible from outside of the VPN, and may be duplicates of private addresses used in other VPNs. To uniquely identify such a private address, it must be associated with a particular VPN routing/forwarding instance, also known as a VRF (VPN Routing and Forwarding table).
snmpAAL5Domain	1.3.6.1.4.1.9.19.1.2	This transport domain is used to specify that particular SNMP messages are to be sent/received over AAL5 transport. The corresponding transport address is of type SnmpAAL5VCIdentifier. An ATM VCC referenced by a SnmpAAL5VCIdentifier must be used only for SNMP packets, and not for any other kind of packets. Care must be taken with the use of this domain because its associated transport address, SnmpAAL5VCIdentifier, contains identifiers which only have local and temporal uniqueness: ifIndex, VPI, VCI. Use of this transport mapping is not recommended, except in circumstances where an IP address is not available and thus a mapping over UDP, such as snmpUDPDomain, can not be used.
snmpCNSDomain	1.3.6.1.4.1.9.19.1.3	This transport domain is used for transporting SNMP messages over the CNS Event Service. The corresponding transport addresses are of type SnmpCNSIdentifier. CNS Event service is an event based transport mechanism. Events are published by producers on particular subjects. Consumers listening for these subjects receive the events. Point to point communication is provided on the CNS Event Service by the use of Name Space Mapper Service that uses the device-id, appended at the end of the subject, to locate a specific target. An Event Agent subject used by a SnmpCNSIdentifier must be used only for SNMP events, and not for any other kind of events. Use of this transport mapping is not recommended, except in circumstances where an IP address is not available and thus a mapping over UDP, such as snmpUDPDomain, can not be used.

RFC description

Cisco transport mappings extending SNMPv2-TM for UDP-VPN and custom transport domains.

Start monitoring Cisco network devices (SNMPv2-TM transport extension) 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 CISCO-TM

What Is CISCO-TM?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description