CISCO-TM: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-TM
Download as:   
SNMPv2-CONF, SNMPv2-SMI, CISCO-SMI, SNMPv2-TC

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
 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.