| 1 |
<!DOCTYPE html> |
| 2 |
<html><head> |
| 3 |
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| 4 |
<title>test.mib</title> |
| 5 |
<meta name="generator" content="KF5::SyntaxHighlighting - Definition (MIB) - Theme (Breeze Light)"/> |
| 6 |
</head><body style="background-color:#ffffff;color:#1f1c1b"><pre> |
| 7 |
SNMP-FRAMEWORK-MIB <span style="font-weight:bold;">DEFINITIONS</span> ::= <span style="font-weight:bold;">BEGIN</span> |
| 8 |
|
| 9 |
<span style="font-weight:bold;">IMPORTS</span> |
| 10 |
<span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">MODULE-IDENTITY</span><span style="color:#ff5500;font-style:italic;">, </span><span style="font-weight:bold;">OBJECT-TYPE</span><span style="color:#ff5500;font-style:italic;">,</span> |
| 11 |
<span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">OBJECT-IDENTITY</span><span style="color:#ff5500;font-style:italic;">,</span> |
| 12 |
<span style="color:#ff5500;font-style:italic;"> snmpModules </span><span style="font-weight:bold;">FROM</span> SNMPv2-SMI |
| 13 |
<span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">TEXTUAL-CONVENTION</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">FROM</span> SNMPv2-TC |
| 14 |
<span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">MODULE-COMPLIANCE</span><span style="color:#ff5500;font-style:italic;">, </span><span style="font-weight:bold;">OBJECT-GROUP</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">FROM</span> SNMPv2-CONF; |
| 15 |
|
| 16 |
snmpFrameworkMIB <span style="font-weight:bold;">MODULE-IDENTITY</span> |
| 17 |
<span style="font-weight:bold;">LAST-UPDATED</span> <span style="color:#bf0303;">"200210140000Z"</span> |
| 18 |
<span style="font-weight:bold;">ORGANIZATION</span> <span style="color:#bf0303;">"SNMPv3 Working Group"</span> |
| 19 |
<span style="font-weight:bold;">CONTACT-INFO</span> <span style="color:#bf0303;">"WG-EMail: [email protected]</span> |
| 20 |
<span style="color:#bf0303;"> Subscribe: [email protected]</span> |
| 21 |
|
| 22 |
<span style="color:#bf0303;"> Co-Chair: Russ Mundy</span> |
| 23 |
<span style="color:#bf0303;"> Network Associates Laboratories</span> |
| 24 |
<span style="color:#bf0303;"> postal: 15204 Omega Drive, Suite 300</span> |
| 25 |
<span style="color:#bf0303;"> Rockville, MD 20850-4601</span> |
| 26 |
<span style="color:#bf0303;"> USA</span> |
| 27 |
<span style="color:#bf0303;"> EMail: [email protected]</span> |
| 28 |
<span style="color:#bf0303;"> phone: +1 301-947-7107</span> |
| 29 |
|
| 30 |
<span style="color:#bf0303;"> Co-Chair &</span> |
| 31 |
<span style="color:#bf0303;"> Co-editor: David Harrington</span> |
| 32 |
<span style="color:#bf0303;"> Enterasys Networks</span> |
| 33 |
<span style="color:#bf0303;"> postal: 35 Industrial Way</span> |
| 34 |
<span style="color:#bf0303;"> P. O. Box 5005</span> |
| 35 |
<span style="color:#bf0303;"> Rochester, New Hampshire 03866-5005</span> |
| 36 |
<span style="color:#bf0303;"> USA</span> |
| 37 |
<span style="color:#bf0303;"> EMail: [email protected]</span> |
| 38 |
<span style="color:#bf0303;"> phone: +1 603-337-2614</span> |
| 39 |
|
| 40 |
<span style="color:#bf0303;"> Co-editor: Randy Presuhn</span> |
| 41 |
<span style="color:#bf0303;"> BMC Software, Inc.</span> |
| 42 |
<span style="color:#bf0303;"> postal: 2141 North First Street</span> |
| 43 |
<span style="color:#bf0303;"> San Jose, California 95131</span> |
| 44 |
<span style="color:#bf0303;"> USA</span> |
| 45 |
<span style="color:#bf0303;"> EMail: [email protected]</span> |
| 46 |
<span style="color:#bf0303;"> phone: +1 408-546-1006</span> |
| 47 |
|
| 48 |
<span style="color:#bf0303;"> Co-editor: Bert Wijnen</span> |
| 49 |
<span style="color:#bf0303;"> Lucent Technologies</span> |
| 50 |
<span style="color:#bf0303;"> postal: Schagen 33</span> |
| 51 |
<span style="color:#bf0303;"> 3461 GL Linschoten</span> |
| 52 |
<span style="color:#bf0303;"> Netherlands</span> |
| 53 |
|
| 54 |
<span style="color:#bf0303;"> EMail: [email protected]</span> |
| 55 |
<span style="color:#bf0303;"> phone: +31 348-680-485</span> |
| 56 |
<span style="color:#bf0303;"> "</span> |
| 57 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"The SNMP Management Architecture MIB</span> |
| 58 |
|
| 59 |
<span style="color:#bf0303;"> Copyright (C) The Internet Society (2002). This</span> |
| 60 |
<span style="color:#bf0303;"> version of this MIB module is part of RFC 3411;</span> |
| 61 |
<span style="color:#bf0303;"> see the RFC itself for full legal notices.</span> |
| 62 |
<span style="color:#bf0303;"> "</span> |
| 63 |
|
| 64 |
<span style="font-weight:bold;">REVISION</span> <span style="color:#bf0303;">"200210140000Z"</span> <span style="color:#898887;">-- 14 October 2002</span> |
| 65 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"Changes in this revision:</span> |
| 66 |
<span style="color:#bf0303;"> - Updated various administrative information.</span> |
| 67 |
<span style="color:#bf0303;"> - Corrected some typos.</span> |
| 68 |
<span style="color:#bf0303;"> - Corrected typo in description of SnmpEngineID</span> |
| 69 |
<span style="color:#bf0303;"> that led to range overlap for 127.</span> |
| 70 |
<span style="color:#bf0303;"> - Changed '255a' to '255t' in definition of</span> |
| 71 |
<span style="color:#bf0303;"> SnmpAdminString to align with current SMI.</span> |
| 72 |
<span style="color:#bf0303;"> - Reworded 'reserved' for value zero in</span> |
| 73 |
<span style="color:#bf0303;"> DESCRIPTION of SnmpSecurityModel.</span> |
| 74 |
<span style="color:#bf0303;"> - The algorithm for allocating security models</span> |
| 75 |
<span style="color:#bf0303;"> should give 256 per enterprise block, rather</span> |
| 76 |
<span style="color:#bf0303;"> than 255.</span> |
| 77 |
<span style="color:#bf0303;"> - The example engine ID of 'abcd' is not</span> |
| 78 |
<span style="color:#bf0303;"> legal. Replaced with '800002b804616263'H based</span> |
| 79 |
<span style="color:#bf0303;"> on example enterprise 696, string 'abc'.</span> |
| 80 |
<span style="color:#bf0303;"> - Added clarification that engineID should</span> |
| 81 |
<span style="color:#bf0303;"> persist across re-initializations.</span> |
| 82 |
<span style="color:#bf0303;"> This revision published as RFC 3411.</span> |
| 83 |
<span style="color:#bf0303;"> "</span> |
| 84 |
<span style="font-weight:bold;">REVISION</span> <span style="color:#bf0303;">"199901190000Z"</span> <span style="color:#898887;">-- 19 January 1999</span> |
| 85 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"Updated editors' addresses, fixed typos.</span> |
| 86 |
<span style="color:#bf0303;"> Published as RFC 2571.</span> |
| 87 |
<span style="color:#bf0303;"> "</span> |
| 88 |
<span style="font-weight:bold;">REVISION</span> <span style="color:#bf0303;">"199711200000Z"</span> <span style="color:#898887;">-- 20 November 1997</span> |
| 89 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"The initial version, published in RFC 2271.</span> |
| 90 |
<span style="color:#bf0303;"> "</span> |
| 91 |
::= { snmpModules <span style="color:#b08000;">10</span> } |
| 92 |
|
| 93 |
<span style="color:#898887;">-- Textual Conventions used in the SNMP Management Architecture ***</span> |
| 94 |
|
| 95 |
<span style="color:#ff5500;font-style:italic;">SnmpEngineID</span> ::= <span style="font-weight:bold;">TEXTUAL-CONVENTION</span> |
| 96 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 97 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"An SNMP engine's administratively-unique identifier.</span> |
| 98 |
<span style="color:#bf0303;"> Objects of this type are for identification, not for</span> |
| 99 |
<span style="color:#bf0303;"> addressing, even though it is possible that an</span> |
| 100 |
<span style="color:#bf0303;"> address may have been used in the generation of</span> |
| 101 |
<span style="color:#bf0303;"> a specific value.</span> |
| 102 |
|
| 103 |
<span style="color:#bf0303;"> The value for this object may not be all zeros or</span> |
| 104 |
<span style="color:#bf0303;"> all 'ff'H or the empty (zero length) string.</span> |
| 105 |
|
| 106 |
<span style="color:#bf0303;"> The initial value for this object may be configured</span> |
| 107 |
<span style="color:#bf0303;"> via an operator console entry or via an algorithmic</span> |
| 108 |
<span style="color:#bf0303;"> function. In the latter case, the following</span> |
| 109 |
<span style="color:#bf0303;"> example algorithm is recommended.</span> |
| 110 |
|
| 111 |
<span style="color:#bf0303;"> In cases where there are multiple engines on the</span> |
| 112 |
<span style="color:#bf0303;"> same system, the use of this algorithm is NOT</span> |
| 113 |
<span style="color:#bf0303;"> appropriate, as it would result in all of those</span> |
| 114 |
<span style="color:#bf0303;"> engines ending up with the same ID value.</span> |
| 115 |
|
| 116 |
<span style="color:#bf0303;"> 1) The very first bit is used to indicate how the</span> |
| 117 |
<span style="color:#bf0303;"> rest of the data is composed.</span> |
| 118 |
|
| 119 |
<span style="color:#bf0303;"> 0 - as defined by enterprise using former methods</span> |
| 120 |
<span style="color:#bf0303;"> that existed before SNMPv3. See item 2 below.</span> |
| 121 |
|
| 122 |
<span style="color:#bf0303;"> 1 - as defined by this architecture, see item 3</span> |
| 123 |
<span style="color:#bf0303;"> below.</span> |
| 124 |
|
| 125 |
<span style="color:#bf0303;"> Note that this allows existing uses of the</span> |
| 126 |
<span style="color:#bf0303;"> engineID (also known as AgentID [RFC1910]) to</span> |
| 127 |
<span style="color:#bf0303;"> co-exist with any new uses.</span> |
| 128 |
|
| 129 |
<span style="color:#bf0303;"> 2) The snmpEngineID has a length of 12 octets.</span> |
| 130 |
|
| 131 |
<span style="color:#bf0303;"> The first four octets are set to the binary</span> |
| 132 |
<span style="color:#bf0303;"> equivalent of the agent's SNMP management</span> |
| 133 |
<span style="color:#bf0303;"> private enterprise number as assigned by the</span> |
| 134 |
<span style="color:#bf0303;"> Internet Assigned Numbers Authority (IANA).</span> |
| 135 |
<span style="color:#bf0303;"> For example, if Acme Networks has been assigned</span> |
| 136 |
<span style="color:#bf0303;"> { enterprises 696 }, the first four octets would</span> |
| 137 |
<span style="color:#bf0303;"> be assigned '000002b8'H.</span> |
| 138 |
|
| 139 |
<span style="color:#bf0303;"> The remaining eight octets are determined via</span> |
| 140 |
<span style="color:#bf0303;"> one or more enterprise-specific methods. Such</span> |
| 141 |
<span style="color:#bf0303;"> methods must be designed so as to maximize the</span> |
| 142 |
<span style="color:#bf0303;"> possibility that the value of this object will</span> |
| 143 |
<span style="color:#bf0303;"> be unique in the agent's administrative domain.</span> |
| 144 |
<span style="color:#bf0303;"> For example, it may be the IP address of the SNMP</span> |
| 145 |
<span style="color:#bf0303;"> entity, or the MAC address of one of the</span> |
| 146 |
<span style="color:#bf0303;"> interfaces, with each address suitably padded</span> |
| 147 |
<span style="color:#bf0303;"> with random octets. If multiple methods are</span> |
| 148 |
<span style="color:#bf0303;"> defined, then it is recommended that the first</span> |
| 149 |
<span style="color:#bf0303;"> octet indicate the method being used and the</span> |
| 150 |
<span style="color:#bf0303;"> remaining octets be a function of the method.</span> |
| 151 |
|
| 152 |
<span style="color:#bf0303;"> 3) The length of the octet string varies.</span> |
| 153 |
|
| 154 |
<span style="color:#bf0303;"> The first four octets are set to the binary</span> |
| 155 |
<span style="color:#bf0303;"> equivalent of the agent's SNMP management</span> |
| 156 |
<span style="color:#bf0303;"> private enterprise number as assigned by the</span> |
| 157 |
<span style="color:#bf0303;"> Internet Assigned Numbers Authority (IANA).</span> |
| 158 |
<span style="color:#bf0303;"> For example, if Acme Networks has been assigned</span> |
| 159 |
<span style="color:#bf0303;"> { enterprises 696 }, the first four octets would</span> |
| 160 |
<span style="color:#bf0303;"> be assigned '000002b8'H.</span> |
| 161 |
|
| 162 |
<span style="color:#bf0303;"> The very first bit is set to 1. For example, the</span> |
| 163 |
<span style="color:#bf0303;"> above value for Acme Networks now changes to be</span> |
| 164 |
<span style="color:#bf0303;"> '800002b8'H.</span> |
| 165 |
|
| 166 |
<span style="color:#bf0303;"> The fifth octet indicates how the rest (6th and</span> |
| 167 |
<span style="color:#bf0303;"> following octets) are formatted. The values for</span> |
| 168 |
<span style="color:#bf0303;"> the fifth octet are:</span> |
| 169 |
|
| 170 |
<span style="color:#bf0303;"> 0 - reserved, unused.</span> |
| 171 |
|
| 172 |
<span style="color:#bf0303;"> 1 - IPv4 address (4 octets)</span> |
| 173 |
<span style="color:#bf0303;"> lowest non-special IP address</span> |
| 174 |
|
| 175 |
<span style="color:#bf0303;"> 2 - IPv6 address (16 octets)</span> |
| 176 |
<span style="color:#bf0303;"> lowest non-special IP address</span> |
| 177 |
|
| 178 |
<span style="color:#bf0303;"> 3 - MAC address (6 octets)</span> |
| 179 |
<span style="color:#bf0303;"> lowest IEEE MAC address, canonical</span> |
| 180 |
<span style="color:#bf0303;"> order</span> |
| 181 |
|
| 182 |
<span style="color:#bf0303;"> 4 - Text, administratively assigned</span> |
| 183 |
<span style="color:#bf0303;"> Maximum remaining length 27</span> |
| 184 |
|
| 185 |
<span style="color:#bf0303;"> 5 - Octets, administratively assigned</span> |
| 186 |
<span style="color:#bf0303;"> Maximum remaining length 27</span> |
| 187 |
|
| 188 |
<span style="color:#bf0303;"> 6-127 - reserved, unused</span> |
| 189 |
|
| 190 |
<span style="color:#bf0303;"> 128-255 - as defined by the enterprise</span> |
| 191 |
<span style="color:#bf0303;"> Maximum remaining length 27</span> |
| 192 |
<span style="color:#bf0303;"> "</span> |
| 193 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">OCTET</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">STRING</span><span style="color:#ff5500;font-style:italic;"> </span>(<span style="font-weight:bold;">SIZE</span>(<span style="color:#b08000;">5..32</span>)) |
| 194 |
|
| 195 |
<span style="color:#ff5500;font-style:italic;">SnmpSecurityModel</span> ::= <span style="font-weight:bold;">TEXTUAL-CONVENTION</span> |
| 196 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 197 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"An identifier that uniquely identifies a</span> |
| 198 |
<span style="color:#bf0303;"> Security Model of the Security Subsystem within</span> |
| 199 |
<span style="color:#bf0303;"> this SNMP Management Architecture.</span> |
| 200 |
|
| 201 |
<span style="color:#bf0303;"> The values for securityModel are allocated as</span> |
| 202 |
<span style="color:#bf0303;"> follows:</span> |
| 203 |
|
| 204 |
<span style="color:#bf0303;"> - The zero value does not identify any particular</span> |
| 205 |
<span style="color:#bf0303;"> security model.</span> |
| 206 |
|
| 207 |
<span style="color:#bf0303;"> - Values between 1 and 255, inclusive, are reserved</span> |
| 208 |
<span style="color:#bf0303;"> for standards-track Security Models and are</span> |
| 209 |
<span style="color:#bf0303;"> managed by the Internet Assigned Numbers Authority</span> |
| 210 |
<span style="color:#bf0303;"> (IANA).</span> |
| 211 |
<span style="color:#bf0303;"> - Values greater than 255 are allocated to</span> |
| 212 |
<span style="color:#bf0303;"> enterprise-specific Security Models. An</span> |
| 213 |
<span style="color:#bf0303;"> enterprise-specific securityModel value is defined</span> |
| 214 |
<span style="color:#bf0303;"> to be:</span> |
| 215 |
|
| 216 |
<span style="color:#bf0303;"> enterpriseID * 256 + security model within</span> |
| 217 |
<span style="color:#bf0303;"> enterprise</span> |
| 218 |
|
| 219 |
<span style="color:#bf0303;"> For example, the fourth Security Model defined by</span> |
| 220 |
<span style="color:#bf0303;"> the enterprise whose enterpriseID is 1 would be</span> |
| 221 |
<span style="color:#bf0303;"> 259.</span> |
| 222 |
|
| 223 |
<span style="color:#bf0303;"> This scheme for allocation of securityModel</span> |
| 224 |
<span style="color:#bf0303;"> values allows for a maximum of 255 standards-</span> |
| 225 |
<span style="color:#bf0303;"> based Security Models, and for a maximum of</span> |
| 226 |
<span style="color:#bf0303;"> 256 Security Models per enterprise.</span> |
| 227 |
|
| 228 |
<span style="color:#bf0303;"> It is believed that the assignment of new</span> |
| 229 |
<span style="color:#bf0303;"> securityModel values will be rare in practice</span> |
| 230 |
<span style="color:#bf0303;"> because the larger the number of simultaneously</span> |
| 231 |
<span style="color:#bf0303;"> utilized Security Models, the larger the</span> |
| 232 |
<span style="color:#bf0303;"> chance that interoperability will suffer.</span> |
| 233 |
<span style="color:#bf0303;"> Consequently, it is believed that such a range</span> |
| 234 |
<span style="color:#bf0303;"> will be sufficient. In the unlikely event that</span> |
| 235 |
<span style="color:#bf0303;"> the standards committee finds this number to be</span> |
| 236 |
<span style="color:#bf0303;"> insufficient over time, an enterprise number</span> |
| 237 |
<span style="color:#bf0303;"> can be allocated to obtain an additional 256</span> |
| 238 |
<span style="color:#bf0303;"> possible values.</span> |
| 239 |
|
| 240 |
<span style="color:#bf0303;"> Note that the most significant bit must be zero;</span> |
| 241 |
<span style="color:#bf0303;"> hence, there are 23 bits allocated for various</span> |
| 242 |
<span style="color:#bf0303;"> organizations to design and define non-standard</span> |
| 243 |
|
| 244 |
<span style="color:#bf0303;"> securityModels. This limits the ability to</span> |
| 245 |
<span style="color:#bf0303;"> define new proprietary implementations of Security</span> |
| 246 |
<span style="color:#bf0303;"> Models to the first 8,388,608 enterprises.</span> |
| 247 |
|
| 248 |
<span style="color:#bf0303;"> It is worthwhile to note that, in its encoded</span> |
| 249 |
<span style="color:#bf0303;"> form, the securityModel value will normally</span> |
| 250 |
<span style="color:#bf0303;"> require only a single byte since, in practice,</span> |
| 251 |
<span style="color:#bf0303;"> the leftmost bits will be zero for most messages</span> |
| 252 |
<span style="color:#bf0303;"> and sign extension is suppressed by the encoding</span> |
| 253 |
<span style="color:#bf0303;"> rules.</span> |
| 254 |
|
| 255 |
<span style="color:#bf0303;"> As of this writing, there are several values</span> |
| 256 |
<span style="color:#bf0303;"> of securityModel defined for use with SNMP or</span> |
| 257 |
<span style="color:#bf0303;"> reserved for use with supporting MIB objects.</span> |
| 258 |
<span style="color:#bf0303;"> They are as follows:</span> |
| 259 |
|
| 260 |
<span style="color:#bf0303;"> 0 reserved for 'any'</span> |
| 261 |
<span style="color:#bf0303;"> 1 reserved for SNMPv1</span> |
| 262 |
<span style="color:#bf0303;"> 2 reserved for SNMPv2c</span> |
| 263 |
<span style="color:#bf0303;"> 3 User-Based Security Model (USM)</span> |
| 264 |
<span style="color:#bf0303;"> "</span> |
| 265 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">INTEGER</span>(<span style="color:#b08000;">0</span> <span style="color:#b08000;">..</span> <span style="color:#b08000;">2147483647</span>) |
| 266 |
|
| 267 |
<span style="color:#ff5500;font-style:italic;">SnmpMessageProcessingModel</span> ::= <span style="font-weight:bold;">TEXTUAL-CONVENTION</span> |
| 268 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 269 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"An identifier that uniquely identifies a Message</span> |
| 270 |
<span style="color:#bf0303;"> Processing Model of the Message Processing</span> |
| 271 |
<span style="color:#bf0303;"> Subsystem within this SNMP Management Architecture.</span> |
| 272 |
|
| 273 |
<span style="color:#bf0303;"> The values for messageProcessingModel are</span> |
| 274 |
<span style="color:#bf0303;"> allocated as follows:</span> |
| 275 |
|
| 276 |
<span style="color:#bf0303;"> - Values between 0 and 255, inclusive, are</span> |
| 277 |
<span style="color:#bf0303;"> reserved for standards-track Message Processing</span> |
| 278 |
<span style="color:#bf0303;"> Models and are managed by the Internet Assigned</span> |
| 279 |
<span style="color:#bf0303;"> Numbers Authority (IANA).</span> |
| 280 |
|
| 281 |
<span style="color:#bf0303;"> - Values greater than 255 are allocated to</span> |
| 282 |
<span style="color:#bf0303;"> enterprise-specific Message Processing Models.</span> |
| 283 |
<span style="color:#bf0303;"> An enterprise messageProcessingModel value is</span> |
| 284 |
<span style="color:#bf0303;"> defined to be:</span> |
| 285 |
|
| 286 |
<span style="color:#bf0303;"> enterpriseID * 256 +</span> |
| 287 |
<span style="color:#bf0303;"> messageProcessingModel within enterprise</span> |
| 288 |
|
| 289 |
<span style="color:#bf0303;"> For example, the fourth Message Processing Model</span> |
| 290 |
<span style="color:#bf0303;"> defined by the enterprise whose enterpriseID</span> |
| 291 |
|
| 292 |
<span style="color:#bf0303;"> is 1 would be 259.</span> |
| 293 |
|
| 294 |
<span style="color:#bf0303;"> This scheme for allocating messageProcessingModel</span> |
| 295 |
<span style="color:#bf0303;"> values allows for a maximum of 255 standards-</span> |
| 296 |
<span style="color:#bf0303;"> based Message Processing Models, and for a</span> |
| 297 |
<span style="color:#bf0303;"> maximum of 256 Message Processing Models per</span> |
| 298 |
<span style="color:#bf0303;"> enterprise.</span> |
| 299 |
|
| 300 |
<span style="color:#bf0303;"> It is believed that the assignment of new</span> |
| 301 |
<span style="color:#bf0303;"> messageProcessingModel values will be rare</span> |
| 302 |
<span style="color:#bf0303;"> in practice because the larger the number of</span> |
| 303 |
<span style="color:#bf0303;"> simultaneously utilized Message Processing Models,</span> |
| 304 |
<span style="color:#bf0303;"> the larger the chance that interoperability</span> |
| 305 |
<span style="color:#bf0303;"> will suffer. It is believed that such a range</span> |
| 306 |
<span style="color:#bf0303;"> will be sufficient. In the unlikely event that</span> |
| 307 |
<span style="color:#bf0303;"> the standards committee finds this number to be</span> |
| 308 |
<span style="color:#bf0303;"> insufficient over time, an enterprise number</span> |
| 309 |
<span style="color:#bf0303;"> can be allocated to obtain an additional 256</span> |
| 310 |
<span style="color:#bf0303;"> possible values.</span> |
| 311 |
|
| 312 |
<span style="color:#bf0303;"> Note that the most significant bit must be zero;</span> |
| 313 |
<span style="color:#bf0303;"> hence, there are 23 bits allocated for various</span> |
| 314 |
<span style="color:#bf0303;"> organizations to design and define non-standard</span> |
| 315 |
<span style="color:#bf0303;"> messageProcessingModels. This limits the ability</span> |
| 316 |
<span style="color:#bf0303;"> to define new proprietary implementations of</span> |
| 317 |
<span style="color:#bf0303;"> Message Processing Models to the first 8,388,608</span> |
| 318 |
<span style="color:#bf0303;"> enterprises.</span> |
| 319 |
|
| 320 |
<span style="color:#bf0303;"> It is worthwhile to note that, in its encoded</span> |
| 321 |
<span style="color:#bf0303;"> form, the messageProcessingModel value will</span> |
| 322 |
<span style="color:#bf0303;"> normally require only a single byte since, in</span> |
| 323 |
<span style="color:#bf0303;"> practice, the leftmost bits will be zero for</span> |
| 324 |
<span style="color:#bf0303;"> most messages and sign extension is suppressed</span> |
| 325 |
<span style="color:#bf0303;"> by the encoding rules.</span> |
| 326 |
|
| 327 |
<span style="color:#bf0303;"> As of this writing, there are several values of</span> |
| 328 |
<span style="color:#bf0303;"> messageProcessingModel defined for use with SNMP.</span> |
| 329 |
<span style="color:#bf0303;"> They are as follows:</span> |
| 330 |
|
| 331 |
<span style="color:#bf0303;"> 0 reserved for SNMPv1</span> |
| 332 |
<span style="color:#bf0303;"> 1 reserved for SNMPv2c</span> |
| 333 |
<span style="color:#bf0303;"> 2 reserved for SNMPv2u and SNMPv2*</span> |
| 334 |
<span style="color:#bf0303;"> 3 reserved for SNMPv3</span> |
| 335 |
<span style="color:#bf0303;"> "</span> |
| 336 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">INTEGER</span>(<span style="color:#b08000;">0</span> <span style="color:#b08000;">..</span> <span style="color:#b08000;">2147483647</span>) |
| 337 |
|
| 338 |
<span style="color:#ff5500;font-style:italic;">SnmpSecurityLevel</span> ::= <span style="font-weight:bold;">TEXTUAL-CONVENTION</span> |
| 339 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 340 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"A Level of Security at which SNMP messages can be</span> |
| 341 |
<span style="color:#bf0303;"> sent or with which operations are being processed;</span> |
| 342 |
<span style="color:#bf0303;"> in particular, one of:</span> |
| 343 |
|
| 344 |
<span style="color:#bf0303;"> noAuthNoPriv - without authentication and</span> |
| 345 |
<span style="color:#bf0303;"> without privacy,</span> |
| 346 |
<span style="color:#bf0303;"> authNoPriv - with authentication but</span> |
| 347 |
<span style="color:#bf0303;"> without privacy,</span> |
| 348 |
<span style="color:#bf0303;"> authPriv - with authentication and</span> |
| 349 |
<span style="color:#bf0303;"> with privacy.</span> |
| 350 |
|
| 351 |
<span style="color:#bf0303;"> These three values are ordered such that</span> |
| 352 |
<span style="color:#bf0303;"> noAuthNoPriv is less than authNoPriv and</span> |
| 353 |
<span style="color:#bf0303;"> authNoPriv is less than authPriv.</span> |
| 354 |
<span style="color:#bf0303;"> "</span> |
| 355 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">INTEGER</span><span style="color:#ff5500;font-style:italic;"> </span>{ noAuthNoPriv(<span style="color:#b08000;">1</span>), |
| 356 |
authNoPriv(<span style="color:#b08000;">2</span>), |
| 357 |
authPriv(<span style="color:#b08000;">3</span>) |
| 358 |
} |
| 359 |
|
| 360 |
<span style="color:#ff5500;font-style:italic;">SnmpAdminString</span> ::= <span style="font-weight:bold;">TEXTUAL-CONVENTION</span> |
| 361 |
<span style="font-weight:bold;">DISPLAY-HINT</span> <span style="color:#bf0303;">"255t"</span> |
| 362 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 363 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"An octet string containing administrative</span> |
| 364 |
<span style="color:#bf0303;"> information, preferably in human-readable form.</span> |
| 365 |
|
| 366 |
<span style="color:#bf0303;"> To facilitate internationalization, this</span> |
| 367 |
<span style="color:#bf0303;"> information is represented using the ISO/IEC</span> |
| 368 |
<span style="color:#bf0303;"> IS 10646-1 character set, encoded as an octet</span> |
| 369 |
<span style="color:#bf0303;"> string using the UTF-8 transformation format</span> |
| 370 |
<span style="color:#bf0303;"> described in [RFC2279].</span> |
| 371 |
|
| 372 |
<span style="color:#bf0303;"> Since additional code points are added by</span> |
| 373 |
<span style="color:#bf0303;"> amendments to the 10646 standard from time</span> |
| 374 |
<span style="color:#bf0303;"> to time, implementations must be prepared to</span> |
| 375 |
<span style="color:#bf0303;"> encounter any code point from 0x00000000 to</span> |
| 376 |
<span style="color:#bf0303;"> 0x7fffffff. Byte sequences that do not</span> |
| 377 |
<span style="color:#bf0303;"> correspond to the valid UTF-8 encoding of a</span> |
| 378 |
<span style="color:#bf0303;"> code point or are outside this range are</span> |
| 379 |
<span style="color:#bf0303;"> prohibited.</span> |
| 380 |
|
| 381 |
<span style="color:#bf0303;"> The use of control codes should be avoided.</span> |
| 382 |
|
| 383 |
<span style="color:#bf0303;"> When it is necessary to represent a newline,</span> |
| 384 |
<span style="color:#bf0303;"> the control code sequence CR LF should be used.</span> |
| 385 |
|
| 386 |
<span style="color:#bf0303;"> The use of leading or trailing white space should</span> |
| 387 |
<span style="color:#bf0303;"> be avoided.</span> |
| 388 |
|
| 389 |
<span style="color:#bf0303;"> For code points not directly supported by user</span> |
| 390 |
<span style="color:#bf0303;"> interface hardware or software, an alternative</span> |
| 391 |
<span style="color:#bf0303;"> means of entry and display, such as hexadecimal,</span> |
| 392 |
<span style="color:#bf0303;"> may be provided.</span> |
| 393 |
|
| 394 |
<span style="color:#bf0303;"> For information encoded in 7-bit US-ASCII,</span> |
| 395 |
<span style="color:#bf0303;"> the UTF-8 encoding is identical to the</span> |
| 396 |
<span style="color:#bf0303;"> US-ASCII encoding.</span> |
| 397 |
|
| 398 |
<span style="color:#bf0303;"> UTF-8 may require multiple bytes to represent a</span> |
| 399 |
<span style="color:#bf0303;"> single character / code point; thus the length</span> |
| 400 |
<span style="color:#bf0303;"> of this object in octets may be different from</span> |
| 401 |
<span style="color:#bf0303;"> the number of characters encoded. Similarly,</span> |
| 402 |
<span style="color:#bf0303;"> size constraints refer to the number of encoded</span> |
| 403 |
<span style="color:#bf0303;"> octets, not the number of characters represented</span> |
| 404 |
<span style="color:#bf0303;"> by an encoding.</span> |
| 405 |
|
| 406 |
<span style="color:#bf0303;"> Note that when this TC is used for an object that</span> |
| 407 |
<span style="color:#bf0303;"> is used or envisioned to be used as an index, then</span> |
| 408 |
<span style="color:#bf0303;"> a SIZE restriction MUST be specified so that the</span> |
| 409 |
<span style="color:#bf0303;"> number of sub-identifiers for any object instance</span> |
| 410 |
<span style="color:#bf0303;"> does not exceed the limit of 128, as defined by</span> |
| 411 |
<span style="color:#bf0303;"> [RFC3416].</span> |
| 412 |
|
| 413 |
<span style="color:#bf0303;"> Note that the size of an SnmpAdminString object is</span> |
| 414 |
<span style="color:#bf0303;"> measured in octets, not characters.</span> |
| 415 |
<span style="color:#bf0303;"> "</span> |
| 416 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">OCTET</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">STRING</span><span style="color:#ff5500;font-style:italic;"> </span>(<span style="font-weight:bold;">SIZE</span> (<span style="color:#b08000;">0..255</span>)) |
| 417 |
|
| 418 |
<span style="color:#898887;">-- Administrative assignments ***************************************</span> |
| 419 |
|
| 420 |
snmpFrameworkAdmin |
| 421 |
<span style="font-weight:bold;">OBJECT</span> <span style="font-weight:bold;">IDENTIFIER</span> ::= { snmpFrameworkMIB <span style="color:#b08000;">1</span> } |
| 422 |
snmpFrameworkMIBObjects |
| 423 |
<span style="font-weight:bold;">OBJECT</span> <span style="font-weight:bold;">IDENTIFIER</span> ::= { snmpFrameworkMIB <span style="color:#b08000;">2</span> } |
| 424 |
snmpFrameworkMIBConformance |
| 425 |
<span style="font-weight:bold;">OBJECT</span> <span style="font-weight:bold;">IDENTIFIER</span> ::= { snmpFrameworkMIB <span style="color:#b08000;">3</span> } |
| 426 |
|
| 427 |
<span style="color:#898887;">-- the snmpEngine Group ********************************************</span> |
| 428 |
|
| 429 |
snmpEngine <span style="font-weight:bold;">OBJECT</span> <span style="font-weight:bold;">IDENTIFIER</span> ::= { snmpFrameworkMIBObjects <span style="color:#b08000;">1</span> } |
| 430 |
|
| 431 |
snmpEngineID <span style="font-weight:bold;">OBJECT-TYPE</span> |
| 432 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> SnmpEngineID</span> |
| 433 |
<span style="font-weight:bold;">MAX-ACCESS</span> <span style="color:#0057ae;">read-only</span> |
| 434 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 435 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"An SNMP engine's administratively-unique identifier.</span> |
| 436 |
|
| 437 |
<span style="color:#bf0303;"> This information SHOULD be stored in non-volatile</span> |
| 438 |
<span style="color:#bf0303;"> storage so that it remains constant across</span> |
| 439 |
<span style="color:#bf0303;"> re-initializations of the SNMP engine.</span> |
| 440 |
<span style="color:#bf0303;"> "</span> |
| 441 |
::= { snmpEngine <span style="color:#b08000;">1</span> } |
| 442 |
|
| 443 |
snmpEngineBoots <span style="font-weight:bold;">OBJECT-TYPE</span> |
| 444 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">INTEGER</span><span style="color:#ff5500;font-style:italic;"> </span>(<span style="color:#b08000;">1..2147483647</span>) |
| 445 |
<span style="font-weight:bold;">MAX-ACCESS</span> <span style="color:#0057ae;">read-only</span> |
| 446 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 447 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"The number of times that the SNMP engine has</span> |
| 448 |
<span style="color:#bf0303;"> (re-)initialized itself since snmpEngineID</span> |
| 449 |
<span style="color:#bf0303;"> was last configured.</span> |
| 450 |
<span style="color:#bf0303;"> "</span> |
| 451 |
::= { snmpEngine <span style="color:#b08000;">2</span> } |
| 452 |
|
| 453 |
snmpEngineTime <span style="font-weight:bold;">OBJECT-TYPE</span> |
| 454 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">INTEGER</span><span style="color:#ff5500;font-style:italic;"> </span>(<span style="color:#b08000;">0..2147483647</span>) |
| 455 |
<span style="font-weight:bold;">UNITS</span> <span style="color:#bf0303;">"seconds"</span> |
| 456 |
<span style="font-weight:bold;">MAX-ACCESS</span> <span style="color:#0057ae;">read-only</span> |
| 457 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 458 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"The number of seconds since the value of</span> |
| 459 |
<span style="color:#bf0303;"> the snmpEngineBoots object last changed.</span> |
| 460 |
<span style="color:#bf0303;"> When incrementing this object's value would</span> |
| 461 |
<span style="color:#bf0303;"> cause it to exceed its maximum,</span> |
| 462 |
<span style="color:#bf0303;"> snmpEngineBoots is incremented as if a</span> |
| 463 |
<span style="color:#bf0303;"> re-initialization had occurred, and this</span> |
| 464 |
<span style="color:#bf0303;"> object's value consequently reverts to zero.</span> |
| 465 |
<span style="color:#bf0303;"> "</span> |
| 466 |
::= { snmpEngine <span style="color:#b08000;">3</span> } |
| 467 |
|
| 468 |
snmpEngineMaxMessageSize <span style="font-weight:bold;">OBJECT-TYPE</span> |
| 469 |
<span style="font-weight:bold;">SYNTAX</span><span style="color:#ff5500;font-style:italic;"> </span><span style="font-weight:bold;">INTEGER</span><span style="color:#ff5500;font-style:italic;"> </span>(<span style="color:#b08000;">484..2147483647</span>) |
| 470 |
<span style="font-weight:bold;">MAX-ACCESS</span> <span style="color:#0057ae;">read-only</span> |
| 471 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 472 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"The maximum length in octets of an SNMP message</span> |
| 473 |
<span style="color:#bf0303;"> which this SNMP engine can send or receive and</span> |
| 474 |
<span style="color:#bf0303;"> process, determined as the minimum of the maximum</span> |
| 475 |
<span style="color:#bf0303;"> message size values supported among all of the</span> |
| 476 |
<span style="color:#bf0303;"> transports available to and supported by the engine.</span> |
| 477 |
<span style="color:#bf0303;"> "</span> |
| 478 |
::= { snmpEngine <span style="color:#b08000;">4</span> } |
| 479 |
|
| 480 |
<span style="color:#898887;">-- Registration Points for Authentication and Privacy Protocols **</span> |
| 481 |
|
| 482 |
snmpAuthProtocols <span style="font-weight:bold;">OBJECT-IDENTITY</span> |
| 483 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 484 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"Registration point for standards-track</span> |
| 485 |
<span style="color:#bf0303;"> authentication protocols used in SNMP Management</span> |
| 486 |
<span style="color:#bf0303;"> Frameworks.</span> |
| 487 |
<span style="color:#bf0303;"> "</span> |
| 488 |
::= { snmpFrameworkAdmin <span style="color:#b08000;">1</span> } |
| 489 |
|
| 490 |
snmpPrivProtocols <span style="font-weight:bold;">OBJECT-IDENTITY</span> |
| 491 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 492 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"Registration point for standards-track privacy</span> |
| 493 |
<span style="color:#bf0303;"> protocols used in SNMP Management Frameworks.</span> |
| 494 |
<span style="color:#bf0303;"> "</span> |
| 495 |
::= { snmpFrameworkAdmin <span style="color:#b08000;">2</span> } |
| 496 |
|
| 497 |
<span style="color:#898887;">-- Conformance information ******************************************</span> |
| 498 |
|
| 499 |
snmpFrameworkMIBCompliances |
| 500 |
<span style="font-weight:bold;">OBJECT</span> <span style="font-weight:bold;">IDENTIFIER</span> ::= {snmpFrameworkMIBConformance <span style="color:#b08000;">1</span>} |
| 501 |
snmpFrameworkMIBGroups |
| 502 |
<span style="font-weight:bold;">OBJECT</span> <span style="font-weight:bold;">IDENTIFIER</span> ::= {snmpFrameworkMIBConformance <span style="color:#b08000;">2</span>} |
| 503 |
|
| 504 |
<span style="color:#898887;">-- compliance statements</span> |
| 505 |
|
| 506 |
snmpFrameworkMIBCompliance <span style="font-weight:bold;">MODULE-COMPLIANCE</span> |
| 507 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 508 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"The compliance statement for SNMP engines which</span> |
| 509 |
<span style="color:#bf0303;"> implement the SNMP Management Framework MIB.</span> |
| 510 |
<span style="color:#bf0303;"> "</span> |
| 511 |
<span style="font-weight:bold;">MODULE</span> <span style="color:#898887;">-- this module</span> |
| 512 |
<span style="font-weight:bold;">MANDATORY-GROUPS</span> { snmpEngineGroup } |
| 513 |
::= { snmpFrameworkMIBCompliances <span style="color:#b08000;">1</span> } |
| 514 |
|
| 515 |
<span style="color:#898887;">-- units of conformance</span> |
| 516 |
|
| 517 |
snmpEngineGroup <span style="font-weight:bold;">OBJECT-GROUP</span> |
| 518 |
<span style="font-weight:bold;">OBJECTS</span> { |
| 519 |
snmpEngineID, |
| 520 |
snmpEngineBoots, |
| 521 |
snmpEngineTime, |
| 522 |
snmpEngineMaxMessageSize |
| 523 |
} |
| 524 |
<span style="font-weight:bold;">STATUS</span> <span style="color:#0057ae;">current</span> |
| 525 |
<span style="font-weight:bold;">DESCRIPTION</span> <span style="color:#bf0303;">"A collection of objects for identifying and</span> |
| 526 |
<span style="color:#bf0303;"> determining the configuration and current timeliness</span> |
| 527 |
|
| 528 |
<span style="color:#bf0303;"> values of an SNMP engine.</span> |
| 529 |
<span style="color:#bf0303;"> "</span> |
| 530 |
::= { snmpFrameworkMIBGroups <span style="color:#b08000;">1</span> } |
| 531 |
|
| 532 |
<span style="font-weight:bold;">END</span> |
| 533 |
</pre></body></html> |