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