File indexing completed on 2024-05-12 04:02:09
0001 <!DOCTYPE html> 0002 <html><head> 0003 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> 0004 <title>test.mib</title> 0005 <meta name="generator" content="KF5::SyntaxHighlighting - Definition (MIB) - Theme (Breeze Dark)"/> 0006 </head><body style="background-color:#232629;color:#cfcfc2"><pre> 0007 SNMP-FRAMEWORK-MIB <span style="font-weight:bold">DEFINITIONS</span> ::= <span style="font-weight:bold">BEGIN</span> 0008 0009 <span style="font-weight:bold">IMPORTS</span> 0010 <span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">MODULE-IDENTITY</span><span style="color:#27ae60;font-style:italic">, </span><span style="font-weight:bold">OBJECT-TYPE</span><span style="color:#27ae60;font-style:italic">,</span> 0011 <span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">OBJECT-IDENTITY</span><span style="color:#27ae60;font-style:italic">,</span> 0012 <span style="color:#27ae60;font-style:italic"> snmpModules </span><span style="font-weight:bold">FROM</span> SNMPv2-SMI 0013 <span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">TEXTUAL-CONVENTION</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">FROM</span> SNMPv2-TC 0014 <span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">MODULE-COMPLIANCE</span><span style="color:#27ae60;font-style:italic">, </span><span style="font-weight:bold">OBJECT-GROUP</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">FROM</span> SNMPv2-CONF; 0015 0016 snmpFrameworkMIB <span style="font-weight:bold">MODULE-IDENTITY</span> 0017 <span style="font-weight:bold">LAST-UPDATED</span> <span style="color:#f44f4f">"200210140000Z"</span> 0018 <span style="font-weight:bold">ORGANIZATION</span> <span style="color:#f44f4f">"SNMPv3 Working Group"</span> 0019 <span style="font-weight:bold">CONTACT-INFO</span> <span style="color:#f44f4f">"WG-EMail: snmpv3@lists.tislabs.com</span> 0020 <span style="color:#f44f4f"> Subscribe: snmpv3-request@lists.tislabs.com</span> 0021 0022 <span style="color:#f44f4f"> Co-Chair: Russ Mundy</span> 0023 <span style="color:#f44f4f"> Network Associates Laboratories</span> 0024 <span style="color:#f44f4f"> postal: 15204 Omega Drive, Suite 300</span> 0025 <span style="color:#f44f4f"> Rockville, MD 20850-4601</span> 0026 <span style="color:#f44f4f"> USA</span> 0027 <span style="color:#f44f4f"> EMail: mundy@tislabs.com</span> 0028 <span style="color:#f44f4f"> phone: +1 301-947-7107</span> 0029 0030 <span style="color:#f44f4f"> Co-Chair &</span> 0031 <span style="color:#f44f4f"> Co-editor: David Harrington</span> 0032 <span style="color:#f44f4f"> Enterasys Networks</span> 0033 <span style="color:#f44f4f"> postal: 35 Industrial Way</span> 0034 <span style="color:#f44f4f"> P. O. Box 5005</span> 0035 <span style="color:#f44f4f"> Rochester, New Hampshire 03866-5005</span> 0036 <span style="color:#f44f4f"> USA</span> 0037 <span style="color:#f44f4f"> EMail: dbh@enterasys.com</span> 0038 <span style="color:#f44f4f"> phone: +1 603-337-2614</span> 0039 0040 <span style="color:#f44f4f"> Co-editor: Randy Presuhn</span> 0041 <span style="color:#f44f4f"> BMC Software, Inc.</span> 0042 <span style="color:#f44f4f"> postal: 2141 North First Street</span> 0043 <span style="color:#f44f4f"> San Jose, California 95131</span> 0044 <span style="color:#f44f4f"> USA</span> 0045 <span style="color:#f44f4f"> EMail: randy_presuhn@bmc.com</span> 0046 <span style="color:#f44f4f"> phone: +1 408-546-1006</span> 0047 0048 <span style="color:#f44f4f"> Co-editor: Bert Wijnen</span> 0049 <span style="color:#f44f4f"> Lucent Technologies</span> 0050 <span style="color:#f44f4f"> postal: Schagen 33</span> 0051 <span style="color:#f44f4f"> 3461 GL Linschoten</span> 0052 <span style="color:#f44f4f"> Netherlands</span> 0053 0054 <span style="color:#f44f4f"> EMail: bwijnen@lucent.com</span> 0055 <span style="color:#f44f4f"> phone: +31 348-680-485</span> 0056 <span style="color:#f44f4f"> "</span> 0057 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"The SNMP Management Architecture MIB</span> 0058 0059 <span style="color:#f44f4f"> Copyright (C) The Internet Society (2002). This</span> 0060 <span style="color:#f44f4f"> version of this MIB module is part of RFC 3411;</span> 0061 <span style="color:#f44f4f"> see the RFC itself for full legal notices.</span> 0062 <span style="color:#f44f4f"> "</span> 0063 0064 <span style="font-weight:bold">REVISION</span> <span style="color:#f44f4f">"200210140000Z"</span> <span style="color:#7a7c7d">-- 14 October 2002</span> 0065 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"Changes in this revision:</span> 0066 <span style="color:#f44f4f"> - Updated various administrative information.</span> 0067 <span style="color:#f44f4f"> - Corrected some typos.</span> 0068 <span style="color:#f44f4f"> - Corrected typo in description of SnmpEngineID</span> 0069 <span style="color:#f44f4f"> that led to range overlap for 127.</span> 0070 <span style="color:#f44f4f"> - Changed '255a' to '255t' in definition of</span> 0071 <span style="color:#f44f4f"> SnmpAdminString to align with current SMI.</span> 0072 <span style="color:#f44f4f"> - Reworded 'reserved' for value zero in</span> 0073 <span style="color:#f44f4f"> DESCRIPTION of SnmpSecurityModel.</span> 0074 <span style="color:#f44f4f"> - The algorithm for allocating security models</span> 0075 <span style="color:#f44f4f"> should give 256 per enterprise block, rather</span> 0076 <span style="color:#f44f4f"> than 255.</span> 0077 <span style="color:#f44f4f"> - The example engine ID of 'abcd' is not</span> 0078 <span style="color:#f44f4f"> legal. Replaced with '800002b804616263'H based</span> 0079 <span style="color:#f44f4f"> on example enterprise 696, string 'abc'.</span> 0080 <span style="color:#f44f4f"> - Added clarification that engineID should</span> 0081 <span style="color:#f44f4f"> persist across re-initializations.</span> 0082 <span style="color:#f44f4f"> This revision published as RFC 3411.</span> 0083 <span style="color:#f44f4f"> "</span> 0084 <span style="font-weight:bold">REVISION</span> <span style="color:#f44f4f">"199901190000Z"</span> <span style="color:#7a7c7d">-- 19 January 1999</span> 0085 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"Updated editors' addresses, fixed typos.</span> 0086 <span style="color:#f44f4f"> Published as RFC 2571.</span> 0087 <span style="color:#f44f4f"> "</span> 0088 <span style="font-weight:bold">REVISION</span> <span style="color:#f44f4f">"199711200000Z"</span> <span style="color:#7a7c7d">-- 20 November 1997</span> 0089 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"The initial version, published in RFC 2271.</span> 0090 <span style="color:#f44f4f"> "</span> 0091 ::= { snmpModules <span style="color:#f67400">10</span> } 0092 0093 <span style="color:#7a7c7d">-- Textual Conventions used in the SNMP Management Architecture ***</span> 0094 0095 <span style="color:#27ae60;font-style:italic">SnmpEngineID</span> ::= <span style="font-weight:bold">TEXTUAL-CONVENTION</span> 0096 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0097 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"An SNMP engine's administratively-unique identifier.</span> 0098 <span style="color:#f44f4f"> Objects of this type are for identification, not for</span> 0099 <span style="color:#f44f4f"> addressing, even though it is possible that an</span> 0100 <span style="color:#f44f4f"> address may have been used in the generation of</span> 0101 <span style="color:#f44f4f"> a specific value.</span> 0102 0103 <span style="color:#f44f4f"> The value for this object may not be all zeros or</span> 0104 <span style="color:#f44f4f"> all 'ff'H or the empty (zero length) string.</span> 0105 0106 <span style="color:#f44f4f"> The initial value for this object may be configured</span> 0107 <span style="color:#f44f4f"> via an operator console entry or via an algorithmic</span> 0108 <span style="color:#f44f4f"> function. In the latter case, the following</span> 0109 <span style="color:#f44f4f"> example algorithm is recommended.</span> 0110 0111 <span style="color:#f44f4f"> In cases where there are multiple engines on the</span> 0112 <span style="color:#f44f4f"> same system, the use of this algorithm is NOT</span> 0113 <span style="color:#f44f4f"> appropriate, as it would result in all of those</span> 0114 <span style="color:#f44f4f"> engines ending up with the same ID value.</span> 0115 0116 <span style="color:#f44f4f"> 1) The very first bit is used to indicate how the</span> 0117 <span style="color:#f44f4f"> rest of the data is composed.</span> 0118 0119 <span style="color:#f44f4f"> 0 - as defined by enterprise using former methods</span> 0120 <span style="color:#f44f4f"> that existed before SNMPv3. See item 2 below.</span> 0121 0122 <span style="color:#f44f4f"> 1 - as defined by this architecture, see item 3</span> 0123 <span style="color:#f44f4f"> below.</span> 0124 0125 <span style="color:#f44f4f"> Note that this allows existing uses of the</span> 0126 <span style="color:#f44f4f"> engineID (also known as AgentID [RFC1910]) to</span> 0127 <span style="color:#f44f4f"> co-exist with any new uses.</span> 0128 0129 <span style="color:#f44f4f"> 2) The snmpEngineID has a length of 12 octets.</span> 0130 0131 <span style="color:#f44f4f"> The first four octets are set to the binary</span> 0132 <span style="color:#f44f4f"> equivalent of the agent's SNMP management</span> 0133 <span style="color:#f44f4f"> private enterprise number as assigned by the</span> 0134 <span style="color:#f44f4f"> Internet Assigned Numbers Authority (IANA).</span> 0135 <span style="color:#f44f4f"> For example, if Acme Networks has been assigned</span> 0136 <span style="color:#f44f4f"> { enterprises 696 }, the first four octets would</span> 0137 <span style="color:#f44f4f"> be assigned '000002b8'H.</span> 0138 0139 <span style="color:#f44f4f"> The remaining eight octets are determined via</span> 0140 <span style="color:#f44f4f"> one or more enterprise-specific methods. Such</span> 0141 <span style="color:#f44f4f"> methods must be designed so as to maximize the</span> 0142 <span style="color:#f44f4f"> possibility that the value of this object will</span> 0143 <span style="color:#f44f4f"> be unique in the agent's administrative domain.</span> 0144 <span style="color:#f44f4f"> For example, it may be the IP address of the SNMP</span> 0145 <span style="color:#f44f4f"> entity, or the MAC address of one of the</span> 0146 <span style="color:#f44f4f"> interfaces, with each address suitably padded</span> 0147 <span style="color:#f44f4f"> with random octets. If multiple methods are</span> 0148 <span style="color:#f44f4f"> defined, then it is recommended that the first</span> 0149 <span style="color:#f44f4f"> octet indicate the method being used and the</span> 0150 <span style="color:#f44f4f"> remaining octets be a function of the method.</span> 0151 0152 <span style="color:#f44f4f"> 3) The length of the octet string varies.</span> 0153 0154 <span style="color:#f44f4f"> The first four octets are set to the binary</span> 0155 <span style="color:#f44f4f"> equivalent of the agent's SNMP management</span> 0156 <span style="color:#f44f4f"> private enterprise number as assigned by the</span> 0157 <span style="color:#f44f4f"> Internet Assigned Numbers Authority (IANA).</span> 0158 <span style="color:#f44f4f"> For example, if Acme Networks has been assigned</span> 0159 <span style="color:#f44f4f"> { enterprises 696 }, the first four octets would</span> 0160 <span style="color:#f44f4f"> be assigned '000002b8'H.</span> 0161 0162 <span style="color:#f44f4f"> The very first bit is set to 1. For example, the</span> 0163 <span style="color:#f44f4f"> above value for Acme Networks now changes to be</span> 0164 <span style="color:#f44f4f"> '800002b8'H.</span> 0165 0166 <span style="color:#f44f4f"> The fifth octet indicates how the rest (6th and</span> 0167 <span style="color:#f44f4f"> following octets) are formatted. The values for</span> 0168 <span style="color:#f44f4f"> the fifth octet are:</span> 0169 0170 <span style="color:#f44f4f"> 0 - reserved, unused.</span> 0171 0172 <span style="color:#f44f4f"> 1 - IPv4 address (4 octets)</span> 0173 <span style="color:#f44f4f"> lowest non-special IP address</span> 0174 0175 <span style="color:#f44f4f"> 2 - IPv6 address (16 octets)</span> 0176 <span style="color:#f44f4f"> lowest non-special IP address</span> 0177 0178 <span style="color:#f44f4f"> 3 - MAC address (6 octets)</span> 0179 <span style="color:#f44f4f"> lowest IEEE MAC address, canonical</span> 0180 <span style="color:#f44f4f"> order</span> 0181 0182 <span style="color:#f44f4f"> 4 - Text, administratively assigned</span> 0183 <span style="color:#f44f4f"> Maximum remaining length 27</span> 0184 0185 <span style="color:#f44f4f"> 5 - Octets, administratively assigned</span> 0186 <span style="color:#f44f4f"> Maximum remaining length 27</span> 0187 0188 <span style="color:#f44f4f"> 6-127 - reserved, unused</span> 0189 0190 <span style="color:#f44f4f"> 128-255 - as defined by the enterprise</span> 0191 <span style="color:#f44f4f"> Maximum remaining length 27</span> 0192 <span style="color:#f44f4f"> "</span> 0193 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">OCTET</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">STRING</span><span style="color:#27ae60;font-style:italic"> </span>(<span style="font-weight:bold">SIZE</span>(<span style="color:#f67400">5..32</span>)) 0194 0195 <span style="color:#27ae60;font-style:italic">SnmpSecurityModel</span> ::= <span style="font-weight:bold">TEXTUAL-CONVENTION</span> 0196 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0197 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"An identifier that uniquely identifies a</span> 0198 <span style="color:#f44f4f"> Security Model of the Security Subsystem within</span> 0199 <span style="color:#f44f4f"> this SNMP Management Architecture.</span> 0200 0201 <span style="color:#f44f4f"> The values for securityModel are allocated as</span> 0202 <span style="color:#f44f4f"> follows:</span> 0203 0204 <span style="color:#f44f4f"> - The zero value does not identify any particular</span> 0205 <span style="color:#f44f4f"> security model.</span> 0206 0207 <span style="color:#f44f4f"> - Values between 1 and 255, inclusive, are reserved</span> 0208 <span style="color:#f44f4f"> for standards-track Security Models and are</span> 0209 <span style="color:#f44f4f"> managed by the Internet Assigned Numbers Authority</span> 0210 <span style="color:#f44f4f"> (IANA).</span> 0211 <span style="color:#f44f4f"> - Values greater than 255 are allocated to</span> 0212 <span style="color:#f44f4f"> enterprise-specific Security Models. An</span> 0213 <span style="color:#f44f4f"> enterprise-specific securityModel value is defined</span> 0214 <span style="color:#f44f4f"> to be:</span> 0215 0216 <span style="color:#f44f4f"> enterpriseID * 256 + security model within</span> 0217 <span style="color:#f44f4f"> enterprise</span> 0218 0219 <span style="color:#f44f4f"> For example, the fourth Security Model defined by</span> 0220 <span style="color:#f44f4f"> the enterprise whose enterpriseID is 1 would be</span> 0221 <span style="color:#f44f4f"> 259.</span> 0222 0223 <span style="color:#f44f4f"> This scheme for allocation of securityModel</span> 0224 <span style="color:#f44f4f"> values allows for a maximum of 255 standards-</span> 0225 <span style="color:#f44f4f"> based Security Models, and for a maximum of</span> 0226 <span style="color:#f44f4f"> 256 Security Models per enterprise.</span> 0227 0228 <span style="color:#f44f4f"> It is believed that the assignment of new</span> 0229 <span style="color:#f44f4f"> securityModel values will be rare in practice</span> 0230 <span style="color:#f44f4f"> because the larger the number of simultaneously</span> 0231 <span style="color:#f44f4f"> utilized Security Models, the larger the</span> 0232 <span style="color:#f44f4f"> chance that interoperability will suffer.</span> 0233 <span style="color:#f44f4f"> Consequently, it is believed that such a range</span> 0234 <span style="color:#f44f4f"> will be sufficient. In the unlikely event that</span> 0235 <span style="color:#f44f4f"> the standards committee finds this number to be</span> 0236 <span style="color:#f44f4f"> insufficient over time, an enterprise number</span> 0237 <span style="color:#f44f4f"> can be allocated to obtain an additional 256</span> 0238 <span style="color:#f44f4f"> possible values.</span> 0239 0240 <span style="color:#f44f4f"> Note that the most significant bit must be zero;</span> 0241 <span style="color:#f44f4f"> hence, there are 23 bits allocated for various</span> 0242 <span style="color:#f44f4f"> organizations to design and define non-standard</span> 0243 0244 <span style="color:#f44f4f"> securityModels. This limits the ability to</span> 0245 <span style="color:#f44f4f"> define new proprietary implementations of Security</span> 0246 <span style="color:#f44f4f"> Models to the first 8,388,608 enterprises.</span> 0247 0248 <span style="color:#f44f4f"> It is worthwhile to note that, in its encoded</span> 0249 <span style="color:#f44f4f"> form, the securityModel value will normally</span> 0250 <span style="color:#f44f4f"> require only a single byte since, in practice,</span> 0251 <span style="color:#f44f4f"> the leftmost bits will be zero for most messages</span> 0252 <span style="color:#f44f4f"> and sign extension is suppressed by the encoding</span> 0253 <span style="color:#f44f4f"> rules.</span> 0254 0255 <span style="color:#f44f4f"> As of this writing, there are several values</span> 0256 <span style="color:#f44f4f"> of securityModel defined for use with SNMP or</span> 0257 <span style="color:#f44f4f"> reserved for use with supporting MIB objects.</span> 0258 <span style="color:#f44f4f"> They are as follows:</span> 0259 0260 <span style="color:#f44f4f"> 0 reserved for 'any'</span> 0261 <span style="color:#f44f4f"> 1 reserved for SNMPv1</span> 0262 <span style="color:#f44f4f"> 2 reserved for SNMPv2c</span> 0263 <span style="color:#f44f4f"> 3 User-Based Security Model (USM)</span> 0264 <span style="color:#f44f4f"> "</span> 0265 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">INTEGER</span>(<span style="color:#f67400">0</span> <span style="color:#f67400">..</span> <span style="color:#f67400">2147483647</span>) 0266 0267 <span style="color:#27ae60;font-style:italic">SnmpMessageProcessingModel</span> ::= <span style="font-weight:bold">TEXTUAL-CONVENTION</span> 0268 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0269 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"An identifier that uniquely identifies a Message</span> 0270 <span style="color:#f44f4f"> Processing Model of the Message Processing</span> 0271 <span style="color:#f44f4f"> Subsystem within this SNMP Management Architecture.</span> 0272 0273 <span style="color:#f44f4f"> The values for messageProcessingModel are</span> 0274 <span style="color:#f44f4f"> allocated as follows:</span> 0275 0276 <span style="color:#f44f4f"> - Values between 0 and 255, inclusive, are</span> 0277 <span style="color:#f44f4f"> reserved for standards-track Message Processing</span> 0278 <span style="color:#f44f4f"> Models and are managed by the Internet Assigned</span> 0279 <span style="color:#f44f4f"> Numbers Authority (IANA).</span> 0280 0281 <span style="color:#f44f4f"> - Values greater than 255 are allocated to</span> 0282 <span style="color:#f44f4f"> enterprise-specific Message Processing Models.</span> 0283 <span style="color:#f44f4f"> An enterprise messageProcessingModel value is</span> 0284 <span style="color:#f44f4f"> defined to be:</span> 0285 0286 <span style="color:#f44f4f"> enterpriseID * 256 +</span> 0287 <span style="color:#f44f4f"> messageProcessingModel within enterprise</span> 0288 0289 <span style="color:#f44f4f"> For example, the fourth Message Processing Model</span> 0290 <span style="color:#f44f4f"> defined by the enterprise whose enterpriseID</span> 0291 0292 <span style="color:#f44f4f"> is 1 would be 259.</span> 0293 0294 <span style="color:#f44f4f"> This scheme for allocating messageProcessingModel</span> 0295 <span style="color:#f44f4f"> values allows for a maximum of 255 standards-</span> 0296 <span style="color:#f44f4f"> based Message Processing Models, and for a</span> 0297 <span style="color:#f44f4f"> maximum of 256 Message Processing Models per</span> 0298 <span style="color:#f44f4f"> enterprise.</span> 0299 0300 <span style="color:#f44f4f"> It is believed that the assignment of new</span> 0301 <span style="color:#f44f4f"> messageProcessingModel values will be rare</span> 0302 <span style="color:#f44f4f"> in practice because the larger the number of</span> 0303 <span style="color:#f44f4f"> simultaneously utilized Message Processing Models,</span> 0304 <span style="color:#f44f4f"> the larger the chance that interoperability</span> 0305 <span style="color:#f44f4f"> will suffer. It is believed that such a range</span> 0306 <span style="color:#f44f4f"> will be sufficient. In the unlikely event that</span> 0307 <span style="color:#f44f4f"> the standards committee finds this number to be</span> 0308 <span style="color:#f44f4f"> insufficient over time, an enterprise number</span> 0309 <span style="color:#f44f4f"> can be allocated to obtain an additional 256</span> 0310 <span style="color:#f44f4f"> possible values.</span> 0311 0312 <span style="color:#f44f4f"> Note that the most significant bit must be zero;</span> 0313 <span style="color:#f44f4f"> hence, there are 23 bits allocated for various</span> 0314 <span style="color:#f44f4f"> organizations to design and define non-standard</span> 0315 <span style="color:#f44f4f"> messageProcessingModels. This limits the ability</span> 0316 <span style="color:#f44f4f"> to define new proprietary implementations of</span> 0317 <span style="color:#f44f4f"> Message Processing Models to the first 8,388,608</span> 0318 <span style="color:#f44f4f"> enterprises.</span> 0319 0320 <span style="color:#f44f4f"> It is worthwhile to note that, in its encoded</span> 0321 <span style="color:#f44f4f"> form, the messageProcessingModel value will</span> 0322 <span style="color:#f44f4f"> normally require only a single byte since, in</span> 0323 <span style="color:#f44f4f"> practice, the leftmost bits will be zero for</span> 0324 <span style="color:#f44f4f"> most messages and sign extension is suppressed</span> 0325 <span style="color:#f44f4f"> by the encoding rules.</span> 0326 0327 <span style="color:#f44f4f"> As of this writing, there are several values of</span> 0328 <span style="color:#f44f4f"> messageProcessingModel defined for use with SNMP.</span> 0329 <span style="color:#f44f4f"> They are as follows:</span> 0330 0331 <span style="color:#f44f4f"> 0 reserved for SNMPv1</span> 0332 <span style="color:#f44f4f"> 1 reserved for SNMPv2c</span> 0333 <span style="color:#f44f4f"> 2 reserved for SNMPv2u and SNMPv2*</span> 0334 <span style="color:#f44f4f"> 3 reserved for SNMPv3</span> 0335 <span style="color:#f44f4f"> "</span> 0336 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">INTEGER</span>(<span style="color:#f67400">0</span> <span style="color:#f67400">..</span> <span style="color:#f67400">2147483647</span>) 0337 0338 <span style="color:#27ae60;font-style:italic">SnmpSecurityLevel</span> ::= <span style="font-weight:bold">TEXTUAL-CONVENTION</span> 0339 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0340 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"A Level of Security at which SNMP messages can be</span> 0341 <span style="color:#f44f4f"> sent or with which operations are being processed;</span> 0342 <span style="color:#f44f4f"> in particular, one of:</span> 0343 0344 <span style="color:#f44f4f"> noAuthNoPriv - without authentication and</span> 0345 <span style="color:#f44f4f"> without privacy,</span> 0346 <span style="color:#f44f4f"> authNoPriv - with authentication but</span> 0347 <span style="color:#f44f4f"> without privacy,</span> 0348 <span style="color:#f44f4f"> authPriv - with authentication and</span> 0349 <span style="color:#f44f4f"> with privacy.</span> 0350 0351 <span style="color:#f44f4f"> These three values are ordered such that</span> 0352 <span style="color:#f44f4f"> noAuthNoPriv is less than authNoPriv and</span> 0353 <span style="color:#f44f4f"> authNoPriv is less than authPriv.</span> 0354 <span style="color:#f44f4f"> "</span> 0355 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">INTEGER</span><span style="color:#27ae60;font-style:italic"> </span>{ noAuthNoPriv(<span style="color:#f67400">1</span>), 0356 authNoPriv(<span style="color:#f67400">2</span>), 0357 authPriv(<span style="color:#f67400">3</span>) 0358 } 0359 0360 <span style="color:#27ae60;font-style:italic">SnmpAdminString</span> ::= <span style="font-weight:bold">TEXTUAL-CONVENTION</span> 0361 <span style="font-weight:bold">DISPLAY-HINT</span> <span style="color:#f44f4f">"255t"</span> 0362 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0363 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"An octet string containing administrative</span> 0364 <span style="color:#f44f4f"> information, preferably in human-readable form.</span> 0365 0366 <span style="color:#f44f4f"> To facilitate internationalization, this</span> 0367 <span style="color:#f44f4f"> information is represented using the ISO/IEC</span> 0368 <span style="color:#f44f4f"> IS 10646-1 character set, encoded as an octet</span> 0369 <span style="color:#f44f4f"> string using the UTF-8 transformation format</span> 0370 <span style="color:#f44f4f"> described in [RFC2279].</span> 0371 0372 <span style="color:#f44f4f"> Since additional code points are added by</span> 0373 <span style="color:#f44f4f"> amendments to the 10646 standard from time</span> 0374 <span style="color:#f44f4f"> to time, implementations must be prepared to</span> 0375 <span style="color:#f44f4f"> encounter any code point from 0x00000000 to</span> 0376 <span style="color:#f44f4f"> 0x7fffffff. Byte sequences that do not</span> 0377 <span style="color:#f44f4f"> correspond to the valid UTF-8 encoding of a</span> 0378 <span style="color:#f44f4f"> code point or are outside this range are</span> 0379 <span style="color:#f44f4f"> prohibited.</span> 0380 0381 <span style="color:#f44f4f"> The use of control codes should be avoided.</span> 0382 0383 <span style="color:#f44f4f"> When it is necessary to represent a newline,</span> 0384 <span style="color:#f44f4f"> the control code sequence CR LF should be used.</span> 0385 0386 <span style="color:#f44f4f"> The use of leading or trailing white space should</span> 0387 <span style="color:#f44f4f"> be avoided.</span> 0388 0389 <span style="color:#f44f4f"> For code points not directly supported by user</span> 0390 <span style="color:#f44f4f"> interface hardware or software, an alternative</span> 0391 <span style="color:#f44f4f"> means of entry and display, such as hexadecimal,</span> 0392 <span style="color:#f44f4f"> may be provided.</span> 0393 0394 <span style="color:#f44f4f"> For information encoded in 7-bit US-ASCII,</span> 0395 <span style="color:#f44f4f"> the UTF-8 encoding is identical to the</span> 0396 <span style="color:#f44f4f"> US-ASCII encoding.</span> 0397 0398 <span style="color:#f44f4f"> UTF-8 may require multiple bytes to represent a</span> 0399 <span style="color:#f44f4f"> single character / code point; thus the length</span> 0400 <span style="color:#f44f4f"> of this object in octets may be different from</span> 0401 <span style="color:#f44f4f"> the number of characters encoded. Similarly,</span> 0402 <span style="color:#f44f4f"> size constraints refer to the number of encoded</span> 0403 <span style="color:#f44f4f"> octets, not the number of characters represented</span> 0404 <span style="color:#f44f4f"> by an encoding.</span> 0405 0406 <span style="color:#f44f4f"> Note that when this TC is used for an object that</span> 0407 <span style="color:#f44f4f"> is used or envisioned to be used as an index, then</span> 0408 <span style="color:#f44f4f"> a SIZE restriction MUST be specified so that the</span> 0409 <span style="color:#f44f4f"> number of sub-identifiers for any object instance</span> 0410 <span style="color:#f44f4f"> does not exceed the limit of 128, as defined by</span> 0411 <span style="color:#f44f4f"> [RFC3416].</span> 0412 0413 <span style="color:#f44f4f"> Note that the size of an SnmpAdminString object is</span> 0414 <span style="color:#f44f4f"> measured in octets, not characters.</span> 0415 <span style="color:#f44f4f"> "</span> 0416 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">OCTET</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">STRING</span><span style="color:#27ae60;font-style:italic"> </span>(<span style="font-weight:bold">SIZE</span> (<span style="color:#f67400">0..255</span>)) 0417 0418 <span style="color:#7a7c7d">-- Administrative assignments ***************************************</span> 0419 0420 snmpFrameworkAdmin 0421 <span style="font-weight:bold">OBJECT</span> <span style="font-weight:bold">IDENTIFIER</span> ::= { snmpFrameworkMIB <span style="color:#f67400">1</span> } 0422 snmpFrameworkMIBObjects 0423 <span style="font-weight:bold">OBJECT</span> <span style="font-weight:bold">IDENTIFIER</span> ::= { snmpFrameworkMIB <span style="color:#f67400">2</span> } 0424 snmpFrameworkMIBConformance 0425 <span style="font-weight:bold">OBJECT</span> <span style="font-weight:bold">IDENTIFIER</span> ::= { snmpFrameworkMIB <span style="color:#f67400">3</span> } 0426 0427 <span style="color:#7a7c7d">-- the snmpEngine Group ********************************************</span> 0428 0429 snmpEngine <span style="font-weight:bold">OBJECT</span> <span style="font-weight:bold">IDENTIFIER</span> ::= { snmpFrameworkMIBObjects <span style="color:#f67400">1</span> } 0430 0431 snmpEngineID <span style="font-weight:bold">OBJECT-TYPE</span> 0432 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> SnmpEngineID</span> 0433 <span style="font-weight:bold">MAX-ACCESS</span> <span style="color:#2980b9">read-only</span> 0434 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0435 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"An SNMP engine's administratively-unique identifier.</span> 0436 0437 <span style="color:#f44f4f"> This information SHOULD be stored in non-volatile</span> 0438 <span style="color:#f44f4f"> storage so that it remains constant across</span> 0439 <span style="color:#f44f4f"> re-initializations of the SNMP engine.</span> 0440 <span style="color:#f44f4f"> "</span> 0441 ::= { snmpEngine <span style="color:#f67400">1</span> } 0442 0443 snmpEngineBoots <span style="font-weight:bold">OBJECT-TYPE</span> 0444 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">INTEGER</span><span style="color:#27ae60;font-style:italic"> </span>(<span style="color:#f67400">1..2147483647</span>) 0445 <span style="font-weight:bold">MAX-ACCESS</span> <span style="color:#2980b9">read-only</span> 0446 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0447 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"The number of times that the SNMP engine has</span> 0448 <span style="color:#f44f4f"> (re-)initialized itself since snmpEngineID</span> 0449 <span style="color:#f44f4f"> was last configured.</span> 0450 <span style="color:#f44f4f"> "</span> 0451 ::= { snmpEngine <span style="color:#f67400">2</span> } 0452 0453 snmpEngineTime <span style="font-weight:bold">OBJECT-TYPE</span> 0454 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">INTEGER</span><span style="color:#27ae60;font-style:italic"> </span>(<span style="color:#f67400">0..2147483647</span>) 0455 <span style="font-weight:bold">UNITS</span> <span style="color:#f44f4f">"seconds"</span> 0456 <span style="font-weight:bold">MAX-ACCESS</span> <span style="color:#2980b9">read-only</span> 0457 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0458 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"The number of seconds since the value of</span> 0459 <span style="color:#f44f4f"> the snmpEngineBoots object last changed.</span> 0460 <span style="color:#f44f4f"> When incrementing this object's value would</span> 0461 <span style="color:#f44f4f"> cause it to exceed its maximum,</span> 0462 <span style="color:#f44f4f"> snmpEngineBoots is incremented as if a</span> 0463 <span style="color:#f44f4f"> re-initialization had occurred, and this</span> 0464 <span style="color:#f44f4f"> object's value consequently reverts to zero.</span> 0465 <span style="color:#f44f4f"> "</span> 0466 ::= { snmpEngine <span style="color:#f67400">3</span> } 0467 0468 snmpEngineMaxMessageSize <span style="font-weight:bold">OBJECT-TYPE</span> 0469 <span style="font-weight:bold">SYNTAX</span><span style="color:#27ae60;font-style:italic"> </span><span style="font-weight:bold">INTEGER</span><span style="color:#27ae60;font-style:italic"> </span>(<span style="color:#f67400">484..2147483647</span>) 0470 <span style="font-weight:bold">MAX-ACCESS</span> <span style="color:#2980b9">read-only</span> 0471 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0472 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"The maximum length in octets of an SNMP message</span> 0473 <span style="color:#f44f4f"> which this SNMP engine can send or receive and</span> 0474 <span style="color:#f44f4f"> process, determined as the minimum of the maximum</span> 0475 <span style="color:#f44f4f"> message size values supported among all of the</span> 0476 <span style="color:#f44f4f"> transports available to and supported by the engine.</span> 0477 <span style="color:#f44f4f"> "</span> 0478 ::= { snmpEngine <span style="color:#f67400">4</span> } 0479 0480 <span style="color:#7a7c7d">-- Registration Points for Authentication and Privacy Protocols **</span> 0481 0482 snmpAuthProtocols <span style="font-weight:bold">OBJECT-IDENTITY</span> 0483 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0484 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"Registration point for standards-track</span> 0485 <span style="color:#f44f4f"> authentication protocols used in SNMP Management</span> 0486 <span style="color:#f44f4f"> Frameworks.</span> 0487 <span style="color:#f44f4f"> "</span> 0488 ::= { snmpFrameworkAdmin <span style="color:#f67400">1</span> } 0489 0490 snmpPrivProtocols <span style="font-weight:bold">OBJECT-IDENTITY</span> 0491 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0492 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"Registration point for standards-track privacy</span> 0493 <span style="color:#f44f4f"> protocols used in SNMP Management Frameworks.</span> 0494 <span style="color:#f44f4f"> "</span> 0495 ::= { snmpFrameworkAdmin <span style="color:#f67400">2</span> } 0496 0497 <span style="color:#7a7c7d">-- Conformance information ******************************************</span> 0498 0499 snmpFrameworkMIBCompliances 0500 <span style="font-weight:bold">OBJECT</span> <span style="font-weight:bold">IDENTIFIER</span> ::= {snmpFrameworkMIBConformance <span style="color:#f67400">1</span>} 0501 snmpFrameworkMIBGroups 0502 <span style="font-weight:bold">OBJECT</span> <span style="font-weight:bold">IDENTIFIER</span> ::= {snmpFrameworkMIBConformance <span style="color:#f67400">2</span>} 0503 0504 <span style="color:#7a7c7d">-- compliance statements</span> 0505 0506 snmpFrameworkMIBCompliance <span style="font-weight:bold">MODULE-COMPLIANCE</span> 0507 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0508 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"The compliance statement for SNMP engines which</span> 0509 <span style="color:#f44f4f"> implement the SNMP Management Framework MIB.</span> 0510 <span style="color:#f44f4f"> "</span> 0511 <span style="font-weight:bold">MODULE</span> <span style="color:#7a7c7d">-- this module</span> 0512 <span style="font-weight:bold">MANDATORY-GROUPS</span> { snmpEngineGroup } 0513 ::= { snmpFrameworkMIBCompliances <span style="color:#f67400">1</span> } 0514 0515 <span style="color:#7a7c7d">-- units of conformance</span> 0516 0517 snmpEngineGroup <span style="font-weight:bold">OBJECT-GROUP</span> 0518 <span style="font-weight:bold">OBJECTS</span> { 0519 snmpEngineID, 0520 snmpEngineBoots, 0521 snmpEngineTime, 0522 snmpEngineMaxMessageSize 0523 } 0524 <span style="font-weight:bold">STATUS</span> <span style="color:#2980b9">current</span> 0525 <span style="font-weight:bold">DESCRIPTION</span> <span style="color:#f44f4f">"A collection of objects for identifying and</span> 0526 <span style="color:#f44f4f"> determining the configuration and current timeliness</span> 0527 0528 <span style="color:#f44f4f"> values of an SNMP engine.</span> 0529 <span style="color:#f44f4f"> "</span> 0530 ::= { snmpFrameworkMIBGroups <span style="color:#f67400">1</span> } 0531 0532 <span style="font-weight:bold">END</span> 0533 </pre></body></html>