AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | IoT | IT Service | Network/System | NIS2 | Infra | Performance | Protocol | SaaS | Security | Service Level | Storage | Linux | VMware | VoIP | Web | Wireless | SNMP

MonitorTools.com » Technical documentation » SNMP » MIB » Cisco » cisco-ping-mib » Objects

cisco-ping-mib.mib object

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2025 can import MIB file cisco-ping-mib and use it to monitor vendor specific OID's.

cisco-ping-mib file content

Object view of cisco-ping-mib:

Scalar Object
ciscoPingEntry .1.3.6.1.4.1.9.9.16.1.1.1
A ping request entry. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row owner objects. It must also, either in the same or in successive PDUs, create the associated instance of the protocol and address objects. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.
Tabular Object
ciscoPingSerialNumber .1.3.6.1.4.1.9.9.16.1.1.1.1
Object which specifies a unique entry in the ciscoPingTable. A management station wishing to initiate a ping operation should use a pseudo-random value for this object when creating or modifying an instance of a ciscoPingEntry. The RowStatus semantics of the ciscoPingEntryStatus object will prevent access conflicts.
ciscoPingProtocol .1.3.6.1.4.1.9.9.16.1.1.1.2
The protocol to use. Once an instance of this object is created, its value can not be changed.
ciscoPingAddress .1.3.6.1.4.1.9.9.16.1.1.1.3
The address of the device to be pinged. An instance of this object cannot be created until the associated instance of ciscoPingProtocol is created.
ciscoPingPacketCount .1.3.6.1.4.1.9.9.16.1.1.1.4
Specifies the number of ping packets to send to the target in this sequence.
ciscoPingPacketSize .1.3.6.1.4.1.9.9.16.1.1.1.5
Specifies the size of ping packets to send to the target in this sequence. The lower and upper boundaries of this object are protocol-dependent. An instance of this object cannot be modified unless the associated instance of ciscoPingProtocol has been created (so as to allow protocol-specific range checking on the new value).
ciscoPingPacketTimeout .1.3.6.1.4.1.9.9.16.1.1.1.6
Specifies the amount of time to wait for a response to a transmitted packet before declaring the packet 'dropped.'
ciscoPingDelay .1.3.6.1.4.1.9.9.16.1.1.1.7
Specifies the minimum amount of time to wait before sending the next packet in a sequence after receiving a response or declaring a timeout for a previous packet. The actual delay may be greater due to internal task scheduling.
ciscoPingTrapOnCompletion .1.3.6.1.4.1.9.9.16.1.1.1.8
Specifies whether or not a ciscoPingCompletion trap should be issued on completion of the sequence of pings. If such a trap is desired, it is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the trap to be delivered.
ciscoPingSentPackets .1.3.6.1.4.1.9.9.16.1.1.1.9
The number of ping packets that have been sent to the target in this sequence.
ciscoPingReceivedPackets .1.3.6.1.4.1.9.9.16.1.1.1.10
The number of ping packets that have been received from the target in this sequence.
ciscoPingMinRtt .1.3.6.1.4.1.9.9.16.1.1.1.11
The minimum round trip time of all the packets that have been sent in this sequence. This object will not be created until the first ping response in a sequence is received.
ciscoPingAvgRtt .1.3.6.1.4.1.9.9.16.1.1.1.12
The average round trip time of all the packets that have been sent in this sequence. This object will not be created until the first ping response in a sequence is received.
ciscoPingMaxRtt .1.3.6.1.4.1.9.9.16.1.1.1.13
The maximum round trip time of all the packets that have been sent in this sequence. This object will not be created until the first ping response in a sequence is received.
ciscoPingCompleted .1.3.6.1.4.1.9.9.16.1.1.1.14
Set to true when all the packets in this sequence have been either responded to or timed out.
ciscoPingEntryOwner .1.3.6.1.4.1.9.9.16.1.1.1.15
The entity that configured this entry.
ciscoPingEntryStatus .1.3.6.1.4.1.9.9.16.1.1.1.16
The status of this table entry. Once the entry status is set to active, the associate entry cannot be modified until the sequence completes (ciscoPingCompleted is true).
ciscoPingVrfName .1.3.6.1.4.1.9.9.16.1.1.1.17
This field is used to specify the VPN name in which the ping will be used. For regular ping this field should not be configured. The agent will use this field to identify the VPN routing Table for this ping. This is the same ascii string used in the CLI to refer to this VPN.
Table
ciscoPingTable .1.3.6.1.4.1.9.9.16.1.1
A table of ping request entries.
Trap
ciscoPingCompletion .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
Object Identifier
ciscoPingMIB .1.3.6.1.4.1.9.9.16
Modified description of ciscoPingAddress object.
ciscoPingMIBObjects .1.3.6.1.4.1.9.9.16.1
ciscoPingMIBTrapPrefix .1.3.6.1.4.1.9.9.16.2
ciscoPingMIBTraps .1.3.6.1.4.1.9.9.16.2.0
ciscoPingMIBConformance .1.3.6.1.4.1.9.9.16.3
ciscoPingMIBCompliances .1.3.6.1.4.1.9.9.16.3.1
ciscoPingMIBGroups .1.3.6.1.4.1.9.9.16.3.2
Group
ciscoPingMIBGroup .1.3.6.1.4.1.9.9.16.3.2.1
A collection of objects providing ping (echo) ability to a Cisco agent.
ciscoPingMIBGroupVpn .1.3.6.1.4.1.9.9.16.3.2.2
A collection of objects providing ping (echo) ability to a Cisco agent.
ciscoPingMIBNotificationGroup .1.3.6.1.4.1.9.9.16.3.2.3
Set of notifications implemented in this module.
M