MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 375 (ciscoFiconMIB). 1 (ciscoFiconMIBObjects). 1 (ciscoFiconConfig). 14 (cficonConfigCopyTable). 1 (cficonConfigCopyEntry)
OID : 1.3.6.1.4.1.9.9.375.1.1.14.1
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoFiconMIB. ciscoFiconMIBObjects. ciscoFiconConfig. cficonConfigCopyTable. cficonConfigCopyEntry
Enfants
Détails
OID1.3.6.1.4.1.9.9.375.1.1.14.1
Module CISCO-FICON-MIB (CISCO)
NomcficonConfigCopyEntry
Statuscurrent
DescriptionA config-copy request. A management station wishing to create an entry should first generate a 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. This config-copy operation is only to copy the running configuration to startup configuration for FICON. 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. Once the config-copy request has been created (i.e. the cfCopyEntryRowStatus has been made active), the entry cannot be modified - the only operation possible after this is to delete the row. Once the request completes, the management station should retrieve the value of the status object 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.