This is a summary of information regarding objects below the snmpFrameworkMIB MIB object, which is defined within the SNMP-FRAMEWORK-MIB MIB document as .1.3.6.1.6.3.10.
Name | Type | Access | OID | Description |
---|---|---|---|---|
1
snmpEngineID |
OCTETSTR
Legal Lengths: 5 .. 32 SnmpEngineID | ReadOnly | .1.3.6.1.6.3.10.2.1.1 |
Note: this object is based on the SnmpEngineID TEXTUAL-CONVENTION. An SNMP engine's administratively-unique identifier. This information SHOULD be stored in non-volatile storage so that it remains constant across re-initializations of the SNMP engine. |
2
snmpEngineBoots |
INTEGER
Legal values: 1 .. 2147483647 | ReadOnly | .1.3.6.1.6.3.10.2.1.2 |
The number of times that the SNMP engine has (re-)initialized itself since snmpEngineID was last configured. |
3
snmpEngineTime |
INTEGER
Legal values: 0 .. 2147483647 | ReadOnly | .1.3.6.1.6.3.10.2.1.3 |
The number of seconds since the value of the snmpEngineBoots object last changed. When incrementing this object's value would cause it to exceed its maximum, snmpEngineBoots is incremented as if a re-initialization had occurred, and this object's value consequently reverts to zero. |
4
snmpEngineMaxMessageSize |
INTEGER
Legal values: 484 .. 2147483647 | ReadOnly | .1.3.6.1.6.3.10.2.1.4 |
The maximum length in octets of an SNMP message which this SNMP engine can send or receive and process, determined as the minimum of the maximum message size values supported among all of the transports available to and supported by the engine. |
SCALAR OBJECTS
TABLE OBJECTS |
These TEXTUAL-CONVENTIONS are used in other parts of the document above. They are SNMP's way of defining a datatype that is used repeatedly by other MIB objects. Any implementation implementing objects that use one of these definitions must follow its DESCRIPTION clause as well as the DESCRIPTION clause of the object itself.
Name | Type | Description |
---|---|---|
SnmpEngineID | OCTETSTR | An SNMP engine's administratively-unique identifier. Objects of this type are for identification, not for addressing, even though it is possible that an address may have been used in the generation of a specific value. The value for this object may not be all zeros or all 'ff'H or the empty (zero length) string. The initial value for this object may be configured via an operator console entry or via an algorithmic function. In the latter case, the following example algorithm is recommended. In cases where there are multiple engines on the same system, the use of this algorithm is NOT appropriate, as it would result in all of those engines ending up with the same ID value. 1) The very first bit is used to indicate how the rest of the data is composed. 0 - as defined by enterprise using former methods that existed before SNMPv3. See item 2 below. 1 - as defined by this architecture, see item 3 below. Note that this allows existing uses of the engineID (also known as AgentID [RFC1910]) to co-exist with any new uses. 2) The snmpEngineID has a length of 12 octets. The first four octets are set to the binary equivalent of the agent's SNMP management private enterprise number as assigned by the Internet Assigned Numbers Authority (IANA). For example, if Acme Networks has been assigned { enterprises 696 }, the first four octets would be assigned '000002b8'H. The remaining eight octets are determined via one or more enterprise-specific methods. Such methods must be designed so as to maximize the possibility that the value of this object will be unique in the agent's administrative domain. For example, it may be the IP address of the SNMP entity, or the MAC address of one of the interfaces, with each address suitably padded with random octets. If multiple methods are defined, then it is recommended that the first octet indicate the method being used and the remaining octets be a function of the method. 3) The length of the octet string varies. The first four octets are set to the binary equivalent of the agent's SNMP management private enterprise number as assigned by the Internet Assigned Numbers Authority (IANA). For example, if Acme Networks has been assigned { enterprises 696 }, the first four octets would be assigned '000002b8'H. The very first bit is set to 1. For example, the above value for Acme Networks now changes to be '800002b8'H. The fifth octet indicates how the rest (6th and following octets) are formatted. The values for the fifth octet are: 0 - reserved, unused. 1 - IPv4 address (4 octets) lowest non-special IP address 2 - IPv6 address (16 octets) lowest non-special IP address 3 - MAC address (6 octets) lowest IEEE MAC address, canonical order 4 - Text, administratively a |
Tree view generated by running: snmptranslate -Tp SNMP-FRAMEWORK-MIB::snmpFrameworkMIB
+--snmpFrameworkMIB(10) | +--snmpFrameworkAdmin(1) | | | +--snmpAuthProtocols(1) | +--snmpPrivProtocols(2) | +--snmpFrameworkMIBObjects(2) | | | +--snmpEngine(1) | | | +-- -R-- String snmpEngineID(1) | | Textual Convention: SnmpEngineID | | Size: 5..32 | +-- -R-- INTEGER snmpEngineBoots(2) | | Range: 1..2147483647 | +-- -R-- INTEGER snmpEngineTime(3) | | Range: 0..2147483647 | +-- -R-- INTEGER snmpEngineMaxMessageSize(4) | Range: 484..2147483647 | +--snmpFrameworkMIBConformance(3) | +--snmpFrameworkMIBCompliances(1) | | | +--snmpFrameworkMIBCompliance(1) | +--snmpFrameworkMIBGroups(2) | +--snmpEngineGroup(1)
Last modified: Wednesday, 01-Aug-2018 04:41:28 UTC
For questions regarding web content and site functionality, please write to the net-snmp-users mail list.