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
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.
Parsed from file CISCO-PING-MIB.mib
Module: CISCO-PING-MIB
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
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 OBJECT-TYPE
SYNTAX CiscoPingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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."
INDEX { ciscoPingSerialNumber }
View at oid-info.com
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
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.
Parsed from file cisco-ping.mib.txt
Company: None
Module: CISCO-PING-MIB
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
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 OBJECT-TYPE SYNTAX CiscoPingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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 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." INDEX { ciscoPingSerialNumber } ::= { ciscoPingTable 1 }
ciscoPingEntry OBJECT-TYPE SYNTAX CiscoPingEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "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 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." INDEX { ciscoPingSerialNumber } ::= { ciscoPingTable 1 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoPingEntry OBJECT-TYPE SYNTAX CiscoPingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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 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." INDEX { ciscoPingSerialNumber } ::= { ciscoPingTable 1 }
ciscoPingEntry OBJECT-TYPE SYNTAX CiscoPingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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 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." INDEX { ciscoPingSerialNumber } ::= { ciscoPingTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.16.1.1.1.1 | ciscoPingSerialNumber | 0 | 0 | Object which specifies a unique entry in the ciscoPingTable. A management station wishing to initiate a ping operation should us… |
| 1.3.6.1.4.1.9.9.16.1.1.1.2 | ciscoPingProtocol | 0 | 0 | The protocol to use. Once an instance of this object is created, its value can not be changed. |
| 1.3.6.1.4.1.9.9.16.1.1.1.3 | ciscoPingAddress | 0 | 0 | The address of the device to be pinged. An instance of this object cannot be created until the associated instance of ciscoPingPr… |
| 1.3.6.1.4.1.9.9.16.1.1.1.4 | ciscoPingPacketCount | 0 | 0 | Specifies the number of ping packets to send to the target in this sequence. |
| 1.3.6.1.4.1.9.9.16.1.1.1.5 | ciscoPingPacketSize | 0 | 0 | Specifies the size of ping packets to send to the target in this sequence. The lower and upper boundaries of this object are pro… |
| 1.3.6.1.4.1.9.9.16.1.1.1.6 | ciscoPingPacketTimeout | 0 | 0 | Specifies the amount of time to wait for a response to a transmitted packet before declaring the packet 'dropped.' |
| 1.3.6.1.4.1.9.9.16.1.1.1.7 | ciscoPingDelay | 0 | 0 | Specifies the minimum amount of time to wait before sending the next packet in a sequence after receiving a response or declaring… |
| 1.3.6.1.4.1.9.9.16.1.1.1.8 | ciscoPingTrapOnCompletion | 0 | 0 | Specifies whether or not a ciscoPingCompletion trap should be issued on completion of the sequence of pings. If such a trap is d… |
| 1.3.6.1.4.1.9.9.16.1.1.1.9 | ciscoPingSentPackets | 0 | 0 | The number of ping packets that have been sent to the target in this sequence. |
| 1.3.6.1.4.1.9.9.16.1.1.1.10 | ciscoPingReceivedPackets | 0 | 0 | The number of ping packets that have been received from the target in this sequence. |
| 1.3.6.1.4.1.9.9.16.1.1.1.11 | ciscoPingMinRtt | 0 | 0 | The minimum round trip time of all the packets that have been sent in this sequence. This object will not be created until the fi… |
| 1.3.6.1.4.1.9.9.16.1.1.1.12 | ciscoPingAvgRtt | 0 | 0 | The average round trip time of all the packets that have been sent in this sequence. This object will not be created until the fi… |
| 1.3.6.1.4.1.9.9.16.1.1.1.13 | ciscoPingMaxRtt | 0 | 0 | The maximum round trip time of all the packets that have been sent in this sequence. This object will not be created until the fi… |
| 1.3.6.1.4.1.9.9.16.1.1.1.14 | ciscoPingCompleted | 0 | 0 | Set to true when all the packets in this sequence have been either responded to or timed out. |
| 1.3.6.1.4.1.9.9.16.1.1.1.15 | ciscoPingEntryOwner | 0 | 0 | The entity that configured this entry. |
| 1.3.6.1.4.1.9.9.16.1.1.1.16 | ciscoPingEntryStatus | 0 | 0 | The status of this table entry. Once the entry status is set to active, the associate entry cannot be modified until the sequenc… |
| 1.3.6.1.4.1.9.9.16.1.1.1.17 | ciscoPingVrfName | 0 | 0 | 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. … |