UDP-MIB
Monitored by Observium The MIB module for managing UDP implementations.
Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFC 4113;
see the RFC itself for full legal notices.
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Network statistics
Explore Observium network monitoring
- Source file
UDP-MIB- Last revised
- Identity
udpMIB- Base OID
1.3.6.1.2.1.50
Imported Objects
| INET-ADDRESS-MIB | InetAddress InetAddressType InetPortNumber |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter32 Counter64 Integer32 IpAddress mib-2 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32 |
Net-SNMP examples using the rfc MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'UDP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'UDP-MIB::udpMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'UDP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'UDP-MIB::udpMIB'
Objects (25)
4 directly used by Observium
Showing 25 of 25 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.2.1.50 |
||
.1.3.6.1.2.1.50.2 |
||
.1.3.6.1.2.1.50.2.1 |
||
.1.3.6.1.2.1.50.2.2 |
||
.1.3.6.1.2.1.7 |
||
|
|
.1.3.6.1.2.1.7.1 |
|
|
|
.1.3.6.1.2.1.7.2 |
|
|
|
.1.3.6.1.2.1.7.3 |
|
|
|
.1.3.6.1.2.1.7.4 |
|
|
|
.1.3.6.1.2.1.7.5 |
|
|
|
.1.3.6.1.2.1.7.5.1 |
|
|
|
.1.3.6.1.2.1.7.5.1.1 |
|
|
|
Integer32
|
.1.3.6.1.2.1.7.5.1.2 |
.1.3.6.1.2.1.7.7 |
||
.1.3.6.1.2.1.7.7.1 |
||
.1.3.6.1.2.1.7.7.1.1 |
||
.1.3.6.1.2.1.7.7.1.2 |
||
.1.3.6.1.2.1.7.7.1.3 |
||
.1.3.6.1.2.1.7.7.1.4 |
||
.1.3.6.1.2.1.7.7.1.5 |
||
.1.3.6.1.2.1.7.7.1.6 |
||
|
Unsigned32
|
.1.3.6.1.2.1.7.7.1.7 |
|
.1.3.6.1.2.1.7.7.1.8 |
||
.1.3.6.1.2.1.7.8 |
||
.1.3.6.1.2.1.7.9 |
Dependencies (4) 3 direct · 1 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- INET-ADDRESS-MIBrfc
- SNMPv2-CONFrfc
- UDP-MIBrfcselected
Conformance Groups (4)
|
udpGroup
deprecated
|
The deprecated group of objects providing for
management of UDP over IPv4. |
.1.3.6.1.2.1.50.2.2.1
|
|
The group of objects providing for counters of UDP
statistics. |
.1.3.6.1.2.1.50.2.2.2
|
|
|
The group of objects providing for counters of high
speed UDP implementations. |
.1.3.6.1.2.1.50.2.2.3
|
|
|
The group of objects providing for the IP version
independent management of UDP 'endpoints'. |
.1.3.6.1.2.1.50.2.2.4
|
Compliance Statements (2)
OID
.1.3.6.1.2.1.50.2.1.1The compliance statement for IPv4-only systems that
implement UDP. For IP version independence, this
compliance statement is deprecated in favor of
udpMIBCompliance2. However, agents are still
encouraged to implement these objects in order to
interoperate with the deployed base of managers.
implement UDP. For IP version independence, this
compliance statement is deprecated in favor of
udpMIBCompliance2. However, agents are still
encouraged to implement these objects in order to
interoperate with the deployed base of managers.
Required groups
| mandatory | udpGroup |
OID
.1.3.6.1.2.1.50.2.1.2The compliance statement for systems that implement
UDP.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, but
for which we have the following compliance
requirements, expressed in OBJECT clause form in this
description clause:
-- OBJECT udpEndpointLocalAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3),
-- ipv6z(4) }
-- DESCRIPTION
-- Support for dns(5) is not required.
-- OBJECT udpEndpointLocalAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
-- OBJECT udpEndpointRemoteAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3),
-- ipv6z(4) }
-- DESCRIPTION
-- Support for dns(5) is not required.
-- OBJECT udpEndpointRemoteAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
UDP.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, but
for which we have the following compliance
requirements, expressed in OBJECT clause form in this
description clause:
-- OBJECT udpEndpointLocalAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3),
-- ipv6z(4) }
-- DESCRIPTION
-- Support for dns(5) is not required.
-- OBJECT udpEndpointLocalAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
-- OBJECT udpEndpointRemoteAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3),
-- ipv6z(4) }
-- DESCRIPTION
-- Support for dns(5) is not required.
-- OBJECT udpEndpointRemoteAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
Required groups
| mandatory | udpBaseGroup | |
| mandatory | udpEndpointGroup | |
| optional | udpHCGroup |
This group is mandatory for systems that are capable of receiving or transmitting more than 1 million UDP datagrams per second. 1 million datagrams per second will cause a Counter32 to wrap in just over an hour. |