DISMAN-PING-MIB

Monitored by Observium
        The Ping MIB (DISMAN-PING-MIB) provides the capability of
controlling the use of the ping function at a remote
host.
        
Copyright (C) The Internet Society (2006).  This version of
this MIB module is part of RFC 4560; 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.
Discovery Polling
Explore Observium network monitoring
Source file
DISMAN-PING-MIB
Last revised
Identity
pingMIB
Base OID
1.3.6.1.2.1.80
Imported Objects
IF-MIB InterfaceIndexOrZero
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime RowStatus StorageType TEXTUAL-CONVENTION (no object page) TruthValue
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 'DISMAN-PING-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DISMAN-PING-MIB::pingMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DISMAN-PING-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-PING-MIB::pingMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (56)
15 directly used by Observium
.1.3.6.1.2.1.80
.1.3.6.1.2.1.80.0
.1.3.6.1.2.1.80.1
.1.3.6.1.2.1.80.1.1
.1.3.6.1.2.1.80.1.2
pingCtlEntry OBS ✓
.1.3.6.1.2.1.80.1.2.1
OctetString
.1.3.6.1.2.1.80.1.2.1.1
.1.3.6.1.2.1.80.1.2.1.10
.1.3.6.1.2.1.80.1.2.1.11
.1.3.6.1.2.1.80.1.2.1.12
Bits
.1.3.6.1.2.1.80.1.2.1.13
Unsigned32
.1.3.6.1.2.1.80.1.2.1.14
Unsigned32
.1.3.6.1.2.1.80.1.2.1.15
pingCtlType OBS ✓ r/w
ObjectIdentifier
.1.3.6.1.2.1.80.1.2.1.16
.1.3.6.1.2.1.80.1.2.1.17
.1.3.6.1.2.1.80.1.2.1.18
.1.3.6.1.2.1.80.1.2.1.19
OctetString
.1.3.6.1.2.1.80.1.2.1.2
.1.3.6.1.2.1.80.1.2.1.20
.1.3.6.1.2.1.80.1.2.1.21
Unsigned32
.1.3.6.1.2.1.80.1.2.1.22
pingCtlRowStatus OBS ✓ r/w
.1.3.6.1.2.1.80.1.2.1.23
.1.3.6.1.2.1.80.1.2.1.3
pingCtlTargetAddress OBS ✓ r/w
.1.3.6.1.2.1.80.1.2.1.4
octetsUnsigned32
.1.3.6.1.2.1.80.1.2.1.5
pingCtlTimeOut OBS ✓ r/w
secondsUnsigned32
.1.3.6.1.2.1.80.1.2.1.6
probesUnsigned32
.1.3.6.1.2.1.80.1.2.1.7
pingCtlAdminStatus OBS ✓ r/w
Enumeration
.1.3.6.1.2.1.80.1.2.1.8
OctetString
.1.3.6.1.2.1.80.1.2.1.9
.1.3.6.1.2.1.80.1.3
.1.3.6.1.2.1.80.1.3.1
Enumeration
.1.3.6.1.2.1.80.1.3.1.1
.1.3.6.1.2.1.80.1.3.1.10
.1.3.6.1.2.1.80.1.3.1.2
.1.3.6.1.2.1.80.1.3.1.3
.1.3.6.1.2.1.80.1.3.1.4
.1.3.6.1.2.1.80.1.3.1.5
.1.3.6.1.2.1.80.1.3.1.6
.1.3.6.1.2.1.80.1.3.1.7
.1.3.6.1.2.1.80.1.3.1.8
.1.3.6.1.2.1.80.1.3.1.9
.1.3.6.1.2.1.80.1.4
.1.3.6.1.2.1.80.1.4.1
Unsigned32
.1.3.6.1.2.1.80.1.4.1.1
.1.3.6.1.2.1.80.1.4.1.2
.1.3.6.1.2.1.80.1.4.1.3
.1.3.6.1.2.1.80.1.4.1.4
.1.3.6.1.2.1.80.1.4.1.5
.1.3.6.1.2.1.80.2
.1.3.6.1.2.1.80.2.1
.1.3.6.1.2.1.80.2.2
.1.3.6.1.2.1.80.3
.1.3.6.1.2.1.80.3.1
.1.3.6.1.2.1.80.3.2
.1.3.6.1.2.1.80.3.3
.1.3.6.1.2.1.80.3.4
Dependencies (8) 6 direct · 2 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
Type Definitions (1)
Enumeration
responseReceived(1)
unknown(2)
internalError(3)
requestTimedOut(4)
unknownDestinationAddress(5)
noRouteToTarget(6)
interfaceInactiveToTarget(7)
arpFailure(8)
maxConcurrentLimitReached(9)
unableToResolveDnsName(10)
invalidHostAddress(11)
Conformance Groups (6)
pingGroup deprecated
The group of objects that constitute the remote ping
capability.
.1.3.6.1.2.1.80.2.2.1
The group of DateAndTime objects.
.1.3.6.1.2.1.80.2.2.2
The notification that are required to be supported by
implementations of this MIB.
.1.3.6.1.2.1.80.2.2.3
The group of objects that constitute the remote ping
capability.
.1.3.6.1.2.1.80.2.2.4
The RowStatus object of the pingCtlTable.
.1.3.6.1.2.1.80.2.2.5
The group of objects that constitute the history
capability.
.1.3.6.1.2.1.80.2.2.6
Compliance Statements (3)

OID .1.3.6.1.2.1.80.2.1.1
The compliance statement for the DISMAN-PING-MIB. This
compliance statement has been deprecated because the
group pingGroup and the pingTimeStampGroup have been
split and deprecated. The pingFullCompliance statement
is semantically identical to the deprecated
pingCompliance statement.
Required groups
mandatory pingGroup
mandatory pingNotificationsGroup
optional pingTimeStampGroup This group is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this group is not supported the values
for the objects in this group be reported as
'0000000000000000'H.
Object refinements
ObjectAccessSyntaxDescription
pingMaxConcurrentRequests readonly
The agent is not required to support set
operations to this object.
pingCtlStorageType readonly
Write access is not required. It is also allowed
that implementations support only the volatile
StorageType enumeration.
pingCtlType readonly
Write access is not required. In addition, the only
value that MUST be supported by an implementation is
pingIcmpEcho.
pingCtlByPassRouteTable readonly
This object is not required by implementations that
are not capable of its implementation. The function
represented by this object is implementable if the
setsockopt SOL_SOCKET SO_DONTROUTE option is
supported.
pingCtlSourceAddressType readonly
unknown(0), ipv4(1), ipv6(2)
This object is not required by implementations that
are not capable of binding the send socket with a
source address. An implementation is only required to
support IPv4 and IPv6 addresses.
pingCtlSourceAddress readonly This object is not required by implementations that
are not capable of binding the send socket with a
source address. An implementation is only required to
support IPv4 and globally unique IPv6 addresses.
pingCtlIfIndex readonly
Write access is not required. When write access is
not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingCtlDSField readonly
Write access is not required. When write access is
not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingResultsIpTargetAddressType
unknown(0), ipv4(1), ipv6(2)
An implementation is only required to
support IPv4 and IPv6 addresses.
pingResultsIpTargetAddress An implementation is only required to
support IPv4 and globally unique IPv6 addresses.

OID .1.3.6.1.2.1.80.2.1.2
The compliance statement for SNMP entities that
fully implement the DISMAN-PING-MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
pingMaxConcurrentRequests readonly
The agent is not required to support set
operations to this object.
pingCtlStorageType readonly
Write access is not required.
pingCtlType readonly
Write access is not required. In addition, the only
value that MUST be supported by an implementation is
pingIcmpEcho.
pingCtlSourceAddressType readonly
unknown(0), ipv4(1), ipv6(2)
Write access to this object is not required by
implementations that are not capable of binding the
send socket with a source address. An implementation
is only required to support IPv4 and IPv6 addresses.
pingCtlSourceAddress readonly Write access to this object is not required by
implementations that are not capable of binding the
send socket with a source address. An implementation
is only required to support IPv4 and IPv6 addresses.
pingCtlIfIndex readonly
Write access is not required. If write access is
not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingCtlByPassRouteTable readonly
Write access to this object is not required by
implementations that are not capable of its
implementation. The function represented by this
object is implementable if the setsockopt
SOL_SOCKET SO_DONTROUTE option is supported.
pingCtlDSField readonly
Write access is not required. If write access is
not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingResultsIpTargetAddressType
unknown(0), ipv4(1), ipv6(2)
An implementation is only required to

support IPv4 and IPv6 addresses.
pingResultsIpTargetAddress An implementation is only required to
support IPv4 and globally unique IPv6 addresses.
pingResultsLastGoodProbe
This object is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this object is not supported its values
be reported as '0000000000000000'H.
pingProbeHistoryTime
This object is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this object is not supported its values
be reported as '0000000000000000'H.

OID .1.3.6.1.2.1.80.2.1.3
The minimum compliance statement for SNMP entities
that implement the minimal subset of the
DISMAN-PING-MIB. Implementors might choose this
subset for small devices with limited resources.
Required groups
mandatory pingMinimumGroup
optional pingCtlRowStatusGroup A compliant implementation does not have to implement
the pingCtlRowStatusGroup.
optional pingHistoryGroup A compliant implementation does not have to implement
the pingHistoryGroup.
optional pingNotificationsGroup A compliant implementation does not have to implement

the pingNotificationsGroup.
Object refinements
ObjectAccessSyntaxDescription
pingMaxConcurrentRequests readonly
The agent is not required to support set
operations to this object.
pingCtlDataFill readonly
The agent is not required to support set
operations to this object.
pingCtlFrequency readonly
Write access is not required. If write access is
not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingCtlMaxRows readonly
Write access is not required. If the
pingHistoryGroup is not implemented, then write
access to this object MUST be disabled, and the object
MUST return a value of 0 when retrieved.
pingCtlStorageType readonly
Write access is not required.
pingCtlTrapGeneration readonly
Write access is not required. If the
pingNotificationsGroup is not implemented, then write
access to this object MUST be disabled, and the object
MUST return a value with no bit set when retrieved.
No bit set indicates that not notification is
generated.
pingCtlTrapProbeFailureFilter readonly
If write access to pingCtlTrapGeneration is not
supported, then write access to this object must also
not be supported. In this case, return 0 as the value
of this object.
pingCtlTrapTestFailureFilter readonly
If write access to pingCtlTrapGeneration is not
supported, then write access to this object must also
not be supported. In this case, return 0 as the value
of this object.
pingCtlType readonly
Write access is not required. In addition, the only
value that MUST be supported by an implementation is
pingIcmpEcho.
pingCtlDescr readonly
The agent is not required to support set
operations to this object.
pingCtlSourceAddressType readonly
unknown(0), ipv4(1), ipv6(2)
Write access to this object is not required by
implementations that are not capable of binding the
send socket with a source address. An implementation
is only required to support IPv4 and IPv6 addresses.
pingCtlSourceAddress readonly Write access to this object is not required by
implementations that are not capable of binding the
send socket with a source address. An implementation
is only required to support IPv4 and IPv6 addresses.
pingCtlIfIndex readonly
Write access is not required. If write access is

not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingCtlByPassRouteTable readonly
Write access is not required. If write access is
not supported, return false(2) as the value of this
object. A value of false(2) means that the function
represented by this option is not supported.
pingCtlDSField readonly
Write access is not required. If write access is
not supported, return a 0 as the value of this object.
A value of 0 means that the function represented by
this option is not supported.
pingResultsIpTargetAddressType
unknown(0), ipv4(1), ipv6(2)
An implementation is only required to
support IPv4 and IPv6 addresses.
pingResultsIpTargetAddress An implementation is only required to
support IPv4 and globally unique IPv6 addresses.
pingResultsLastGoodProbe
This object is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this object is not supported its values
be reported as '0000000000000000'H.
pingProbeHistoryTime
If the pingHistoryGroup is implemented, then this
object is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this object is not supported its values

be reported as '0000000000000000'H.
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.2.1.80.0.1
Generated when a probe failure is detected, when the

corresponding pingCtlTrapGeneration object is set to
probeFailure(0), subject to the value of
pingCtlTrapProbeFailureFilter. The object
pingCtlTrapProbeFailureFilter can be used to specify the
number of consecutive probe failures that are required
before this notification can be generated.
.1.3.6.1.2.1.80.0.2
Generated when a ping test is determined to have failed,
when the corresponding pingCtlTrapGeneration object is
set to testFailure(1). In this instance,
pingCtlTrapTestFailureFilter should specify the number of
probes in a test required to have failed in order to
consider the test failed.
.1.3.6.1.2.1.80.0.3
Generated at the completion of a ping test when the
corresponding pingCtlTrapGeneration object has the
testCompletion(2) bit set.