SNMP-TSM-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: SNMP-TSM-MIB
Download as:   
SNMPv2-CONF, SNMPv2-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
 snmpTsmMIB 1.3.6.1.2.1.190
The Transport Security Model MIB. In keeping with the RFC 3411 design decisions to use self-contained documents, the RFC that contains the definition of this MIB module also includes the elements of procedure that are needed for processing the Transport Security Model for SNMP. These MIB objects SHOULD NOT be modified via other subsystems or models defined in other documents. This allows the Transport Security Model for SNMP to be designed and documented as independent and self-contained, having no direct impact on other modules, and this allows this module to be upgraded and supplemented as the need arises, and to move along the standards track on different time-lines from other modules. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5591; see the RFC itself for full legal notices.
         snmpTsmNotifications 1.3.6.1.2.1.190.0
         snmpTsmMIBObjects 1.3.6.1.2.1.190.1
             snmpTsmStats 1.3.6.1.2.1.190.1.1
                 snmpTsmInvalidCaches 1.3.6.1.2.1.190.1.1.1 counter32 read-only
The number of incoming messages dropped because the tmStateReference referred to an invalid cache.
                 snmpTsmInadequateSecurityLevels 1.3.6.1.2.1.190.1.1.2 counter32 read-only
The number of incoming messages dropped because the securityLevel asserted by the Transport Model was less than the securityLevel requested by the application.
                 snmpTsmUnknownPrefixes 1.3.6.1.2.1.190.1.1.3 counter32 read-only
The number of messages dropped because snmpTsmConfigurationUsePrefix was set to true and there is no known prefix for the specified transport domain.
                 snmpTsmInvalidPrefixes 1.3.6.1.2.1.190.1.1.4 counter32 read-only
The number of messages dropped because the securityName associated with an outgoing message did not contain a valid transport domain prefix.
             snmpTsmConfiguration 1.3.6.1.2.1.190.1.2
                 snmpTsmConfigurationUsePrefix 1.3.6.1.2.1.190.1.2.1 truthvalue read-write
If this object is set to true, then securityNames passing to and from the application are expected to contain a transport-domain-specific prefix. If this object is set to true, then a domain-specific prefix will be added by the TSM to the securityName for incoming messages and removed from the securityName when processing outgoing messages. Transport domains and prefixes are maintained in a registry by IANA. This object SHOULD persist across system reboots.
         snmpTsmConformance 1.3.6.1.2.1.190.2
             snmpTsmCompliances 1.3.6.1.2.1.190.2.1
                 snmpTsmCompliance 1.3.6.1.2.1.190.2.1.1
The compliance statement for SNMP engines that support the SNMP-TSM-MIB.
             snmpTsmGroups 1.3.6.1.2.1.190.2.2
                 snmpTsmGroup 1.3.6.1.2.1.190.2.2.2
A collection of objects for maintaining information of an SNMP engine that implements the SNMP Transport Security Model.