CISCO-PING-MIB
AI MIB Summary
The CISCO-PING-MIB enables Cisco IOS devices to execute remote ICMP echo requests and manage the associated ping session states via SNMP. It exposes specific metrics including target IP addresses, packet transmission counts, round-trip times, and current session operational status for network reachability monitoring.
Modified description of ciscoPingAddress object.
Main OID:
ciscoPingMIB.1.3.6.1.4.1.9.9.16
27
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
ciscoPingMIBModified description of ciscoPingAddress object. MODULE-IDENTITY .1.3.6.1.4.1.9.9.16 |
ciscoPingMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.16.1 |
ciscoPingTableA table of ping request entries. SEQUENCE OF CiscoPingEntry .1.3.6.1.4.1.9.9.16.1.1 |
ciscoPingEntryA 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
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. CiscoPingEntry .1.3.6.1.4.1.9.9.16.1.1.1 |
ciscoPingSerialNumberObject 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. Integer32 .1.3.6.1.4.1.9.9.16.1.1.1.1 |
ciscoPingProtocolThe protocol to use.
Once an instance of this object is created, its
value can not be changed.rw CiscoNetworkProtocol (CISCO-TC) .1.3.6.1.4.1.9.9.16.1.1.1.2 |
ciscoPingAddressThe address of the device to be pinged.
An instance of this object cannot be created until the
associated instance of ciscoPingProtocol is created.rw CiscoNetworkAddress (CISCO-TC) .1.3.6.1.4.1.9.9.16.1.1.1.3 |
ciscoPingPacketCountSpecifies the number of ping packets to send to the target
in this sequence.rw Integer32 .1.3.6.1.4.1.9.9.16.1.1.1.4 |
ciscoPingPacketSizeSpecifies 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).rw Integer32 .1.3.6.1.4.1.9.9.16.1.1.1.5 |
ciscoPingPacketTimeoutSpecifies the amount of time to wait for a response to a
transmitted packet before declaring the packet 'dropped.'rw Integer32 .1.3.6.1.4.1.9.9.16.1.1.1.6 |
ciscoPingDelaySpecifies 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.rw Integer32 .1.3.6.1.4.1.9.9.16.1.1.1.7 |
ciscoPingTrapOnCompletionSpecifies 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.16.1.1.1.8 |
ciscoPingSentPacketsThe number of ping packets that have been sent to the target
in this sequence.ro Counter32 .1.3.6.1.4.1.9.9.16.1.1.1.9 |
ciscoPingReceivedPacketsThe number of ping packets that have been received from the
target in this sequence.ro Counter32 .1.3.6.1.4.1.9.9.16.1.1.1.10 |
ciscoPingMinRttThe 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.ro Integer32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.16.1.1.1.11 |
ciscoPingAvgRttThe 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.ro Integer32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.16.1.1.1.12 |
ciscoPingMaxRttThe 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.ro Integer32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.16.1.1.1.13 |
ciscoPingCompletedSet to true when all the packets in this sequence have been
either responded to or timed out.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.16.1.1.1.14 |
ciscoPingEntryOwnerThe entity that configured this entry.rw OwnerString (IF-MIB) .1.3.6.1.4.1.9.9.16.1.1.1.15 |
ciscoPingEntryStatusThe 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).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.16.1.1.1.16 |
ciscoPingVrfNameThis 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.rw OCTET STRING .1.3.6.1.4.1.9.9.16.1.1.1.17 |
ciscoPingMIBTrapPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.16.2 |
ciscoPingMIBTraps OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.16.2.0 |
ciscoPingCompletionA 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 NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.16.2.0.1 |
ciscoPingMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.16.3 |
ciscoPingMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.16.3.1 |
ciscoPingMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.16.3.2 |