A 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.
Parsed from file CISCO-FICON-MIB.mib
Module: CISCO-FICON-MIB
A 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.
A 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.
Parsed from file CISCO-FICON-MIB.my.txt
Company: None
Module: CISCO-FICON-MIB
A 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.
cficonConfigCopyEntry OBJECT-TYPE SYNTAX CficonConfigCopyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A 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." INDEX { cficonConfigCopyIndex } ::= { cficonConfigCopyTable 1 }
cficonConfigCopyEntry OBJECT-TYPE SYNTAX CficonConfigCopyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A 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." INDEX { cficonConfigCopyIndex } ::= { cficonConfigCopyTable 1 }
Vendor: Cisco
Module: CISCO-FICON-MIB
[Automatically extracted from oidview.com]
cficonConfigCopyEntry OBJECT-TYPE SYNTAX CficonConfigCopyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A 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." INDEX { cficonConfigCopyIndex } ::= { cficonConfigCopyTable 1 }
cficonConfigCopyEntry OBJECT-TYPE SYNTAX CficonConfigCopyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A 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." INDEX { cficonConfigCopyIndex } ::= { cficonConfigCopyTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.375.1.1.14.1.1 | cficonConfigCopyIndex | 0 | 0 | Object which specifies a unique entry in the cficonConfigCopyTable. A management station wishing to initiate a config-copy opera… |
| 1.3.6.1.4.1.9.9.375.1.1.14.1.2 | cficonCopyState | 0 | 0 | Specifies the result of this config-copy request. This value of this object is instantiated only after the row has been instantia… |
| 1.3.6.1.4.1.9.9.375.1.1.14.1.3 | cficonCopyFailReason | 0 | 0 | An error string describing the reason the copy failed. |
| 1.3.6.1.4.1.9.9.375.1.1.14.1.4 | cficonCopyEntryRowStatus | 0 | 0 | The status of this table entry. Once the entry status is set to active, the associated entry cannot be modified until the reques… |