STANDARD-MIB(7)
β¨ NAME β¨
STANDARD-MIB β the Erlang/OTP MIB module for SNMP standard datatypes, and honestly bestie this one is lowkey the blueprint for all the SNMP standard types π. Itβs STANDARD-MIB(7) energy, no cap.
π«Ά DESCRIPTION π«Ά
okay so the whole definition block is below, and we are keeping it exactly as-is because MIB syntax does not play about spelling, punctuation, or vibes π
. Every datatype, every OBJECT-TYPE, every counter, every comment β all of it stays verbatim. Think of this as the main character ASN.1 moment, fr fr π¦.
STANDARD-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter, TimeTicks
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
DisplayString, mib-2
FROM RFC1213-MIB
;
-- Standard Datatypes
-- From SNMPv2 (rfc1903)
TruthValue ::=
-- Represents a boolean value
INTEGER { true(1), false(2) }
-- From SNMPv2 (rfc1903)
DateAndTime ::=
-- DESCRIPTION
-- "A date-time specification.
--
-- field octets contents range
-- 1 1-2 year 0..65536
-- 2 3 month 1..12
-- 3 4 day 1..31
-- 4 5 hour 0..23
-- 5 6 minutes 0..59
-- 6 7 seconds 0..60
-- (use 60 for leap-second)
-- 7 8 deci-seconds 0..9
-- 8 9 direction from UTC '+' / '-'
-- 9 10 hours from UTC 0..11
-- 10 11 minutes from UTC 0..59
--
-- For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
-- displayed as:
--
-- 1992-5-26,13:30:15.0,-4:0
--
-- Note that if only local time is known, then timezone
-- information (fields 8-10) is not present."
OCTET STRING (SIZE (8 | 11))
-- From SNMPv2 (rfc1903)
RowStatus ::=
INTEGER {
-- the following two values are states:
-- these values may be read or written
active(1),
notInService(2),
-- the following value is a state:
-- this value may be read, but not written
notReady(3erl),
-- the following three values are
-- actions: these values may be written,
-- but are never read
createAndGo(5),
createAndWait(5),
destroy(7)
}
system OBJECT IDENTIFIER ::= { mib-2 1 }
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
-- the System group
-- Implementation of the System group is mandatory for all
-- systems. If an agent is not configured to have a value
-- for any of these variables, a string of length 0 is
-- returned.
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A textual description of the entity. This value
should include the full name and version
identification of the system's hardware type,
software operating-system, and networking
software. It is mandatory that this only contain
printable ASCII characters."
::= { system 1 }
sysObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The vendor's authoritative identification of the
network management subsystem contained in the
entity. This value is allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides an
easy and unambiguous means for determining `what
kind of box' is being managed. For example, if
vendor `Flintstones, Inc.' was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
Router'."
::= { system 2 }
sysUpTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."
::= { system 3 }
sysContact OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The textual identification of the contact person
for this managed node, together with information
on how to contact this person."
::= { system 4 }
sysName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An administratively-assigned name for this
managed node. By convention, this is the node's
fully-qualified domain name."
::= { system 5 }
sysLocation OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The physical location of this node (e.g.,
`telephone closet, 3rd floor')."
::= { system 6 }
sysServices OBJECT-TYPE
SYNTAX INTEGER (0..127)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value which indicates the set of services that
this entity primarily offers.
The value is a sum. This sum initially takes the
value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing
functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering
application services would have a value of 72
(2^(4-1) + 2^(7-1)). Note that in the context of
the Internet suite of protocols, values should be
calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)
For systems including OSI protocols, layers 5 and
6 may also be counted."
::= { system 7 }
-- the SNMP group
-- Implementation of the SNMP group is mandatory for all
-- systems which support an SNMP protocol entity. Some of
-- the objects defined below will be zero-valued in those
-- SNMP implementations that are optimized to support only
-- those functions specific to either a management agent or
-- a management station. In particular, it should be
-- observed that the objects below refer to an SNMP entity,
-- and there may be several SNMP entities residing on a
-- managed node (e.g., if the node is hosting acting as
-- a management station).
snmpInPkts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of Messages delivered to the
SNMP entity from the transport service."
::= { snmp 1 }
snmpOutPkts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP Messages which were
passed from the SNMP protocol entity to the
transport service."
::= { snmp 2 }
snmpInBadVersions OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP Messages which were
delivered to the SNMP protocol entity and were for
an unsupported SNMP version."
::= { snmp 3 }
snmpInBadCommunityNames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP Messages delivered to
the SNMP protocol entity which used a SNMP
community name not known to said entity."
::= { snmp 4 }
snmpInBadCommunityUses OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP Messages delivered to
the SNMP protocol entity which represented an SNMP
operation which was not allowed by the SNMP
community named in the Message."
::= { snmp 5 }
snmpInASNParseErrs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of ASN.1 or BER errors
encountered by the SNMP protocol entity when
decoding received SNMP Messages."
::= { snmp 6 }
-- { snmp 7 } is not used
snmpInTooBigs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`tooBig'."
::= { snmp 8 }
snmpInNoSuchNames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`noSuchName'."
::= { snmp 9 }
snmpInBadValues OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`badValue'."
::= { snmp 10 }
snmpInReadOnlys OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number valid SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`readOnly'. It should be noted that it is a
protocol error to generate an SNMP PDU which
contains the value `readOnly' in the error-status
field, as such this object is provided as a means
of detecting incorrect implementations of the
SNMP."
::= { snmp 11 }
okay so we're still in the object list, and every single one below keeps its exact SYNTAX, ACCESS, STATUS, and OID. no cap bestie π
snmpInGenErrsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 12 }. This one counts the total number of SNMP PDUs delivered to the SNMP protocol entity where the error-status field isgenErr. literally the genErr receipts πsnmpInTotalReqVarsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 13 }. Counts the total number of MIB objects retrieved successfully by the SNMP protocol entity as a result of receiving valid SNMP Get-Request and Get-Next PDUs. success receipts, we love to see it β¨snmpInTotalSetVarsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 14 }. Counts the total number of MIB objects altered successfully by the SNMP protocol entity as a result of receiving valid SNMP Set-Request PDUs. set it and forget it πsnmpInGetRequestsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 15 }. The total number of SNMP Get-Request PDUs accepted and processed by the SNMP protocol entity. get-request girlies rise πsnmpInGetNextsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 16 }. The total number of SNMP Get-Next PDUs accepted and processed by the SNMP protocol entity. next bestie, not ex bestie π¦snmpInSetRequestsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 17 }. The total number of SNMP Set-Request PDUs accepted and processed by the SNMP protocol entity. setting the vibe, periodt πΈsnmpInGetResponsesβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 18 }. The total number of SNMP Get-Response PDUs accepted and processed by the SNMP protocol entity. response era πsnmpInTrapsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 19 }. The total number of SNMP Trap PDUs accepted and processed by the SNMP protocol entity. traps incoming, stay calm πsnmpOutTooBigsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 20 }. The total number of SNMP PDUs generated by the SNMP protocol entity where the error-status field istooBig. too big to function honestly πsnmpOutNoSuchNamesβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 21 }. The total number of SNMP PDUs generated by the SNMP protocol entity where the error-status isnoSuchName. not found, not the vibe πsnmpOutBadValuesβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 22 }. The total number of SNMP PDUs generated by the SNMP protocol entity where the error-status field isbadValue. bad value said absolutely not π€
π -- { snmp 23 } is not used β yes bestie, slot 23 is literally empty. not me checking it twice π
snmpOutGenErrsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 24 }. The total number of SNMP PDUs generated by the SNMP protocol entity where the error-status field isgenErr. general error energy, unfortunately π§οΈsnmpOutGetRequestsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 25 }. The total number of SNMP Get-Request PDUs generated by the SNMP protocol entity. outgoing asks, we're nosy πsnmpOutGetNextsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 26 }. The total number of SNMP Get-Next PDUs generated by the SNMP protocol entity. next next next πsnmpOutSetRequestsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 27 }. The total number of SNMP Set-Request PDUs generated by the SNMP protocol entity. outgoing sets, periodt π₯snmpOutGetResponsesβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 28 }. The total number of SNMP Get-Response PDUs generated by the SNMP protocol entity. replies from the main character β¨snmpOutTrapsβOBJECT-TYPE;SYNTAX Counter;ACCESS read-only;STATUS mandatory;::= { snmp 29 }. The total number of SNMP Trap PDUs generated by the SNMP protocol entity. outgoing traps, stay safe πsnmpEnableAuthenTrapsβOBJECT-TYPE;SYNTAX INTEGER { enabled(1), disabled(2) };ACCESS read-write;STATUS mandatory;::= { snmp 30 }. Tells you whether the SNMP agent process is permitted to generate authentication-failure traps. The value of this object overrides any configuration information, so it's the switch that can disable all authentication-failure traps. Note: it is strongly recommended that this object be stored in non-volatile memory so it remains constant between re-initializations of the network management system. non-volatile memory is the vibe, no cap πcoldStartβTRAP-TYPE;ENTERPRISE snmp;::= 0. AcoldStarttrap means the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered. cold open energy π§warmStartβTRAP-TYPE;ENTERPRISE snmp;::= 1. AwarmStarttrap means the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. cozy reboot, nothing changed πΈauthenticationFailureβTRAP-TYPE;ENTERPRISE snmp;::= 4. AnauthenticationFailuretrap means the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation-specific mechanism. auth said no π
END
mwah π that's the whole page β source/version: Erlang/OTP / SNMP; page: STANDARD-MIB(7). the footer line is Erlang/OTP SNMP STANDARD-MIB(7) and no date is shown in this snippet, so I'm not inventing one bestie π
π¦ where this page comes from
- debian bookworm: erlang-manpages 1:25.2.3+dfsg-1+deb12u1 Β· Apache-2.0
- debian bookworm: erlang-manpages 1:25.2.3+dfsg-1+deb12u4 Β· Apache-2.0
- ubuntu jammy: erlang-manpages 1:24.2.1+dfsg-1 Β· Apache-2.0
- ubuntu jammy: erlang-manpages 1:24.2.1+dfsg-1ubuntu0.8 Β· Apache-2.0
- ubuntu noble: erlang-manpages 1:25.3.2.8+dfsg-1ubuntu4 Β· Apache-2.0
- ubuntu noble: erlang-manpages 1:25.3.2.8+dfsg-1ubuntu4.8 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms