A table containing information about the failure
cause of the config copy operation. An entry is
created only when the value of ccCopyState changes
to 'failed' for a config copy operation.
Not all combinations of ccCopySourceFileType and
ccCopyDestFileType need to be supported. For
example, an implementation may choose to support
only the following combination:
ccCopySourceFileType = 'runningConfig'
ccCopyDestFileType = 'fabricStartupConfig'.
In the case where a fabric wide config copy
operation is being performed, for example by
selecting ccCopyDestFileType value to be
'fabricStartupConfig', it is possible that the
fabric could have more than one device. In such
cases this table would have one entry for each
device in the fabric. In this case even if the
operation succeeded in one device and failed in
another, the operation as such has failed, so the
global state represented by ccCopyState 'failed',
but for the device on which it was success,
ccCopyErrorDescription would have the
distinguished value, 'success'.
Once the config copy operation completes and if an
entry gets instantiated, the management station
should retrieve the values of the status objects of
interest. Once an entry in ccCopyTable is deleted
by management station, all the corresponding entries
with the same ccCopyIndex in this table are also
deleted.
In order to prevent old entries from clogging the
table, entries age out at the same time as the
corresponding entry with same ccCopyIndex in
ccCopyTable ages out.
Parsed from file CISCO-CONFIG-COPY-MIB.mib
Module: CISCO-CONFIG-COPY-MIB
A table containing information about the failure
cause of the config copy operation. An entry is
created only when the value of ccCopyState changes
to 'failed' for a config copy operation.
Not all combinations of ccCopySourceFileType and
ccCopyDestFileType need to be supported. For
example, an implementation may choose to support
only the following combination:
ccCopySourceFileType = 'runningConfig'
ccCopyDestFileType = 'fabricStartupConfig'.
In the case where a fabric wide config copy
operation is being performed, for example by
selecting ccCopyDestFileType value to be
'fabricStartupConfig', it is possible that the
fabric could have more than one device. In such
cases this table would have one entry for each
device in the fabric. In this case even if the
operation succeeded in one device and failed in
another, the operation as such has failed, so the
global state represented by ccCopyState 'failed',
but for the device on which it was success,
ccCopyErrorDescription would have the
distinguished value, 'success'.
Once the config copy operation completes and if an
entry gets instantiated, the management station
should retrieve the values of the status objects of
interest. Once an entry in ccCopyTable is deleted
by management station, all the corresponding entries
with the same ccCopyIndex in this table are also
deleted.
In order to prevent old entries from clogging the
table, entries age out at the same time as the
corresponding entry with same ccCopyIndex in
ccCopyTable ages out.
A table containing information about the failure
cause of the config copy operation. An entry is
created only when the value of ccCopyState changes
to 'failed' for a config copy operation.
Not all combinations of ccCopySourceFileType and
ccCopyDestFileType need to be supported. For
example, an implementation may choose to support
only the following combination:
ccCopySourceFileType = 'runningConfig'
ccCopyDestFileType = 'fabricStartupConfig'.
In the case where a fabric wide config copy
operation is being performed, for example by
selecting ccCopyDestFileType value to be
'fabricStartupConfig', it is possible that the
fabric could have more than one device. In such
cases this table would have one entry for each
device in the fabric. In this case even if the
operation succeeded in one device and failed in
another, the operation as such has failed, so the
global state represented by ccCopyState 'failed',
but for the device on which it was success,
ccCopyErrorDescription would have the
distinguished value, 'success'.
Once the config copy operation completes and if an
entry gets instantiated, the management station
should retrieve the values of the status objects of
interest. Once an entry in ccCopyTable is deleted
by management station, all the corresponding entries
with the same ccCopyIndex in this table are also
deleted.
In order to prevent old entries from clogging the
table, entries age out at the same time as the
corresponding entry with same ccCopyIndex in
ccCopyTable ages out.
Parsed from file cisco-config-copy.mib.txt
Company: None
Module: CISCO-CONFIG-COPY-MIB
A table containing information about the failure
cause of the config copy operation. An entry is
created only when the value of ccCopyState changes
to 'failed' for a config copy operation.
Not all combinations of ccCopySourceFileType and
ccCopyDestFileType need to be supported. For
example, an implementation may choose to support
only the following combination:
ccCopySourceFileType = 'runningConfig'
ccCopyDestFileType = 'fabricStartupConfig'.
In the case where a fabric wide config copy
operation is being performed, for example by
selecting ccCopyDestFileType value to be
'fabricStartupConfig', it is possible that the
fabric could have more than one device. In such
cases this table would have one entry for each
device in the fabric. In this case even if the
operation succeeded in one device and failed in
another, the operation as such has failed, so the
global state represented by ccCopyState 'failed',
but for the device on which it was success,
ccCopyErrorDescription would have the
distinguished value, 'success'.
Once the config copy operation completes and if an
entry gets instantiated, the management station
should retrieve the values of the status objects of
interest. Once an entry in ccCopyTable is deleted
by management station, all the corresponding entries
with the same ccCopyIndex in this table are also
deleted.
In order to prevent old entries from clogging the
table, entries age out at the same time as the
corresponding entry with same ccCopyIndex in
ccCopyTable ages out.
ccCopyErrorTable OBJECT-TYPE SYNTAX SEQUENCE OF CcCopyErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to 'failed' for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = 'runningConfig' ccCopyDestFileType = 'fabricStartupConfig'. In the case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be 'fabricStartupConfig', it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState 'failed', but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, 'success'. Once the config copy operation completes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. Once an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. In order to prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out." ::= { ccCopy 2 }
ccCopyErrorTable OBJECT-TYPE SYNTAX SEQUENCE OF CcCopyErrorEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table containing information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to 'failed' for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = 'runningConfig' ccCopyDestFileType = 'fabricStartupConfig'. In the case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be 'fabricStartupConfig', it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState 'failed', but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, 'success'. Once the config copy operation completes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. Once an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. In order to prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out." ::= { ccCopy 2 }
Vendor: Cisco
Module: CISCO-CONFIG-COPY-MIB
[Automatically extracted from oidview.com]
ccCopyErrorTable OBJECT-TYPE SYNTAX SEQUENCE OF CcCopyErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to 'failed' for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = 'runningConfig' ccCopyDestFileType = 'fabricStartupConfig'. In the case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be 'fabricStartupConfig', it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState 'failed', but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, 'success'. Once the config copy operation completes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. Once an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. In order to prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out." ::= { ccCopy 2 }
ccCopyErrorTable OBJECT-TYPE SYNTAX SEQUENCE OF CcCopyErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to 'failed' for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = 'runningConfig' ccCopyDestFileType = 'fabricStartupConfig'. In the case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be 'fabricStartupConfig', it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState 'failed', but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, 'success'. Once the config copy operation completes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. Once an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. In order to prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out." ::= { ccCopy 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.96.1.1.2.1 | ccCopyErrorEntry | 5 | 5 | An entry containing information about the outcome at one destination of a failed config copy operation. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.96.1.1.1 | ccCopyTable | 1 | 17 | A table of config-copy requests. |