MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 10 (ciscoFlashMIB). 1 (ciscoFlashMIBObjects). 2 (ciscoFlashOps). 2 (ciscoFlashPartitioningTable). 1 (ciscoFlashPartitioningEntry)
OID : 1.3.6.1.4.1.9.9.10.1.2.2.1
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoFlashMIB. ciscoFlashMIBObjects. ciscoFlashOps. ciscoFlashPartitioningTable. ciscoFlashPartitioningEntry
Enfants
Détails
OID1.3.6.1.4.1.9.9.10.1.2.2.1
Module CISCO-FLASH-MIB (CISCO)
NomciscoFlashPartitioningEntry
Statuscurrent
DescriptionA Flash partitioning operation entry. Each entry consists of the command, the target device, the partition count, and optionally the partition sizes. 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 object. It must also, either in the same or in successive PDUs, create the associated instance of the command and parameter objects. It should also modify the default values for any of the parameter objects if the defaults are not appropriate. Once the appropriate instances of all the command 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 operation. 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 parameter objects. Once an operation has been activated, it cannot be stopped. Once the operation completes, the management station should retrieve the value of the status object (and time if desired), and 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.