Transport-Subsystem-MIB

File: Transport-Subsystem-MIB.mib (9997 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF
SNMP-FRAMEWORK-MIB TRANSPORT-ADDRESS-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE mib-2
Integer32 Unsigned32 Gauge32
TestAndIncr StorageType RowStatus
MODULE-COMPLIANCE OBJECT-GROUP SnmpSecurityModel
SnmpAdminString SnmpSecurityLevel SnmpEngineID
TransportAddress TransportAddressType

Defined Types

SnmpTransportModel  
An identifier that uniquely identifies a Transport Model of the Transport Subsystem within the SNMP Management Architecture. The values for transportModel are allocated as follows: - The zero value does not identify any particular transport model. - Values between 1 and 255, inclusive, are reserved for standards-track Transport Models and are managed by the Internet Assigned Numbers Authority (IANA). - Values greater than 255 are allocated to enterprise-specific Transport Models. An enterprise-specific transportModel value is defined to be: enterpriseID * 256 + transport model within enterprise For example, the fourth Transport Model defined by the enterprise whose enterpriseID is 1 would be 260. This scheme for allocation of transportModel values allows for a maximum of 255 standards- based Transport Models, and for a maximum of 256 Transport Models per enterprise. It is believed that the assignment of new transportModel values will be rare in practice because the larger the number of simultaneously utilized Transport Models, the larger the chance that interoperability will suffer. Consequently, it is believed that such a range will be sufficient. In the unlikely event that the standards committee finds this number to be insufficient over time, an enterprise number can be allocated to obtain an additional 256 possible values. Note that the most significant bit must be zero; hence, there are 23 bits allocated for various organizations to design and define non-standard transportModels. This limits the ability to define new proprietary implementations of Transport Models to the first 8,388,608 enterprises. It is worthwhile to note that, in its encoded form, the transportModel value will normally require only a single byte since, in practice, the leftmost bits will be zero for most messages and sign extension is suppressed by the encoding rules. As of this writing, there are several values of transportModel defined for use with SNMP or reserved for use with supporting MIB objects. They are as follows: 0 reserved for 'any' 1 reserved for UDP 2 reserved for TCP 3 SSH Transport Model
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Defined Values

tmsMIB 1.3.6.1.2.1.1
The Transport Subsystem MIB Module Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices. -- NOTE to RFC editor: replace XXXX with actual RFC number -- for this document and remove this note
MODULE-IDENTITY    

tmsNotifications 1.3.6.1.2.1.1.0
OBJECT IDENTIFIER    

tmsObjects 1.3.6.1.2.1.1.1
OBJECT IDENTIFIER    

tmsConformance 1.3.6.1.2.1.1.2
OBJECT IDENTIFIER    

tmsStats 1.3.6.1.2.1.1.1.1
OBJECT IDENTIFIER    

tmsGroups 1.3.6.1.2.1.1.2.1
OBJECT IDENTIFIER    

tmsCompliances 1.3.6.1.2.1.1.2.2
OBJECT IDENTIFIER    

tmsGroup 1.3.6.1.2.1.1.2.1.2
A collection of objects for maintaining session information of an SNMP engine which implements the Transport subsystem.
Status: current Access: not-set
OBJECT-GROUP    

tmsCompliance 1.3.6.1.2.1.1.2.2.1
The compliance statement for SNMP engines that support the Transport-Subsystem-MIB
Status: current Access: not-set
MODULE-COMPLIANCE