CISCO-PING-MIB

        Modified description of ciscoPingAddress object.
    
Source file
CISCO-PING-MIB
Last revised
Identity
ciscoPingMIB
Base OID
1.3.6.1.4.1.9.9.16
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-TC CiscoNetworkAddress CiscoNetworkProtocol
IF-MIB OwnerString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC RowStatus TruthValue
Net-SNMP examples using the cisco 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 'CISCO-PING-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-PING-MIB::ciscoPingMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-PING-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-PING-MIB::ciscoPingMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (26)
.1.3.6.1.4.1.9.9.16
.1.3.6.1.4.1.9.9.16.1
.1.3.6.1.4.1.9.9.16.1.1
.1.3.6.1.4.1.9.9.16.1.1.1
Integer32
.1.3.6.1.4.1.9.9.16.1.1.1.1
.1.3.6.1.4.1.9.9.16.1.1.1.10
.1.3.6.1.4.1.9.9.16.1.1.1.11
.1.3.6.1.4.1.9.9.16.1.1.1.12
.1.3.6.1.4.1.9.9.16.1.1.1.13
.1.3.6.1.4.1.9.9.16.1.1.1.14
.1.3.6.1.4.1.9.9.16.1.1.1.15
.1.3.6.1.4.1.9.9.16.1.1.1.16
OctetString
.1.3.6.1.4.1.9.9.16.1.1.1.17
.1.3.6.1.4.1.9.9.16.1.1.1.2
.1.3.6.1.4.1.9.9.16.1.1.1.3
Integer32
.1.3.6.1.4.1.9.9.16.1.1.1.4
.1.3.6.1.4.1.9.9.16.1.1.1.5
millisecondsInteger32
.1.3.6.1.4.1.9.9.16.1.1.1.6
millisecondsInteger32
.1.3.6.1.4.1.9.9.16.1.1.1.7
.1.3.6.1.4.1.9.9.16.1.1.1.8
.1.3.6.1.4.1.9.9.16.1.1.1.9
.1.3.6.1.4.1.9.9.16.2
.1.3.6.1.4.1.9.9.16.2.0
.1.3.6.1.4.1.9.9.16.3
.1.3.6.1.4.1.9.9.16.3.1
.1.3.6.1.4.1.9.9.16.3.2
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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. CISCO-TCcisco
  5. IANAifType-MIBrfc
  6. SNMPv2-CONFrfc
  7. SNMPv2-MIBrfc
  8. IF-MIBrfc
  9. CISCO-PING-MIBciscoselected
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.16.3.1.1
The compliance statement for entities which implement
the Cisco Ping MIB
Required groups

OID .1.3.6.1.4.1.9.9.16.3.1.2
The compliance statement for entities which implement
the Cisco Ping MIB
Required groups
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.16.2.0.1
A ciscoPingCompleted trap is sent at the completion
of a sequence of pings if such a trap was requested
when the sequence was initiated. In addition to the
above listed objects (which are always present),
the message will contain the following objects if
any responses were received:
ciscoPingMinRtt
ciscoPingAvgRtt
ciscoPingMaxRtt
It will also contain the following object if the ping
is to a VPN address:
ciscoPingVrfName