MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 16 (ciscoPingMIB). 1 (ciscoPingMIBObjects). 1 (ciscoPingTable). 1 (ciscoPingEntry)
OID : 1.3.6.1.4.1.9.9.16.1.1.1
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoPingMIB. ciscoPingMIBObjects. ciscoPingTable. ciscoPingEntry
Enfants
D├ętails
OID1.3.6.1.4.1.9.9.16.1.1.1
Module CISCO-PING-MIB (CISCO)
NomciscoPingEntry
Statuscurrent
DescriptionA 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.