| OID symbolic | OID numeric | Type | Access | Description |
|---|
| ciscoConfigCopyMIB | 1.3.6.1.4.1.9.9.96 | | | This MIB facilitates writing of configuration files
of an SNMP Agent running Cisco's IOS in the
following ways: to and from the net, copying running
configurations to startup configurations and
vice-versa, and copying a configuration
(running or startup) to and from the local
IOS file system. |
| ciscoConfigCopyMIBObjects | 1.3.6.1.4.1.9.9.96.1 | | | |
| ccCopy | 1.3.6.1.4.1.9.9.96.1.1 | | | |
| ccCopyTable | 1.3.6.1.4.1.9.9.96.1.1.1 | | not-accessible | A table of config-copy requests. |
| ccCopyEntry | 1.3.6.1.4.1.9.9.96.1.1.1.1 | | not-accessible | 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 and row index objects. It must also,
either in the same or in successive PDUs, create an
instance of ccCopySourceFileType and
ccCopyDestFileType.
At least one of the file types defined in
ConfigFileType TC must be an agent-config file type
(i.e. 'startupConfig' or 'runningConfig').
If one of the file types is a 'networkFile', a valid
ccCopyFileName and ccCopyServerAddressType and
ccCopyServerAddressRev1 or just ccCopyServerAddress
must be created as well. If ccCopyServerAddress is
created then ccCopyServerAddressRev1 will store the
same IP address and ccCopyServerAddressType will
take the value 'ipv4'.
For a file type of 'iosFile', only
a valid ccCopyFileName needs to be created as an
extra parameter.
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 config-copy request has been created
(i.e. the ccCopyEntryRowStatus 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 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
ever be deleted within 5 minutes of completing. |
| U32 ccCopyIndex | 1.3.6.1.4.1.9.9.96.1.1.1.1.1 | Unsigned32 | not-accessible | Object which specifies a unique entry in the
ccCopyTable. A management station wishing
to initiate a config-copy operation should use a
random value for this object when creating
or modifying an instance of a ccCopyEntry.
The RowStatus semantics of the ccCopyEntryRowStatus
object will prevent access conflicts. |
| CON ccCopyProtocol | 1.3.6.1.4.1.9.9.96.1.1.1.1.2 | ConfigCopyProtocol | read-create | The protocol to be used for any copy.
If the copy operation occurs locally on the SNMP
agent (e.g. 'runningConfig' to 'startupConfig'),
this object may be ignored by the implementation. |
| CON ccCopySourceFileType | 1.3.6.1.4.1.9.9.96.1.1.1.1.3 | ConfigFileType | read-create | Specifies the type of file to copy from. Either the
ccCopySourceFileType or the ccCopyDestFileType
(or both) must be of type 'runningConfig' or
'startupConfig'. Also, the ccCopySourceFileType
must be different from the ccCopyDestFileType.
If the ccCopySourceFileType has the value of
'networkFile', the ccCopyServerAddress/
ccCopyServerAddressRev1 and ccCopyServerAddressType
and ccCopyFileName must also be created, and 3
objects together (ccCopySourceFileType,
ccCopyServerAddressRev1, ccCopyFileName) will
uniquely identify the source file. If
ccCopyServerAddress is created then
ccCopyServerAddressRev1 will store the
same IP address and ccCopyServerAddressType will
take the value 'ipv4'.
If the ccCopySourceFileType is 'iosFile', the
ccCopyFileName must also be created, and the
2 objects together (ccCopySourceFileType,
ccCopyFileName) will uniquely identify the source
file. |
| CON ccCopyDestFileType | 1.3.6.1.4.1.9.9.96.1.1.1.1.4 | ConfigFileType | read-create | specifies the type of file to copy to. Either the
ccCopySourceFileType or the ccCopyDestFileType
(or both) must be of type 'runningConfig' or
'startupConfig'. Also, the ccCopySourceFileType
must be different from the ccCopyDestFileType.
If the ccCopyDestFileType has the value of
'networkFile', the
ccCopyServerAddress/ccCopyServerAddressType and
ccCopyServerAddressRev1 and ccCopyFileName must
also be created, and 3 objects together
(ccCopyDestFileType, ccCopyServerAddressRev1,
ccCopyFileName) will uniquely identify the
destination file. If ccCopyServerAddress is created
then ccCopyServerAddressRev1 will store the same IP
address and ccCopyServerAddressType will take the
value 'ipv4'.
If the ccCopyDestFileType is 'iosFile', the
ccCopyFileName must also be created, and the 2
objects together (ccCopyDestFileType,
ccCopyFileName) will uniquely identify the
destination file. |
| IP ccCopyServerAddress | 1.3.6.1.4.1.9.9.96.1.1.1.1.5 | IpAddress | read-create | The IP address of the TFTP server from (or to)
which to copy the configuration file. This object
must be created when either the
ccCopySourceFileType or ccCopyDestFileType has the
value 'networkFile'.
Values of 0.0.0.0 or FF.FF.FF.FF for
ccCopyServerAddress are not allowed.
Since this object can just hold only IPv4 Transport
type, it is deprecated and replaced by
ccCopyServerAddressRev1. |
| STR ccCopyFileName | 1.3.6.1.4.1.9.9.96.1.1.1.1.6 | DisplayString | read-create | The file name (including the path, if applicable)
of the file. This object must be created when either
the ccCopySourceFileType or ccCopyDestFileType has
the value 'networkFile' or 'iosFile'. |
| STR ccCopyUserName | 1.3.6.1.4.1.9.9.96.1.1.1.1.7 | DisplayString | read-create | Remote username for copy via FTP, RCP, SFTP or
SCP protocol.
This object must be created when the ccCopyProtocol
is 'rcp', 'scp', 'ftp', or 'sftp'.
If the protocol is RCP, it will override the remote
username configured through the
rcmd remote-username
configuration command.
The remote username is sent as the server username
in an RCP command request sent by the system to a
remote RCP server. |
| STR ccCopyUserPassword | 1.3.6.1.4.1.9.9.96.1.1.1.1.8 | DisplayString | read-create | Password used by FTP, SFTP or SCP for copying a
file to/from an FTP/SFTP/SCP server. This object
must be created when the ccCopyProtocol is FTP or
SCP.
Reading it returns a zero-length string for security
reasons. |
| T/F ccCopyNotificationOnCompletion | 1.3.6.1.4.1.9.9.96.1.1.1.1.9 | TruthValue | read-create | Specifies whether or not a ccCopyCompletion
notification should be issued on completion of the
TFTP transfer. If such a notification is desired,
it is the responsibility of the management entity to
ensure that the SNMP administrative model is
configured in such a way as to allow the
notification to be delivered. |
| CON ccCopyState | 1.3.6.1.4.1.9.9.96.1.1.1.1.10 | ConfigCopyState | read-only | Specifies the state of this config-copy request.
This value of this object is instantiated only after
the row has been instantiated, i.e. after the
ccCopyEntryRowStatus has been made active. |
| TIM ccCopyTimeStarted | 1.3.6.1.4.1.9.9.96.1.1.1.1.11 | TimeStamp | read-only | Specifies the time the ccCopyState last
transitioned to 'running', or 0 if the state has
never transitioned to 'running'(e.g., stuck in
'waiting' state).
This object is instantiated only after the row has
been instantiated. |
| TIM ccCopyTimeCompleted | 1.3.6.1.4.1.9.9.96.1.1.1.1.12 | TimeStamp | read-only | Specifies the time the ccCopyState last
transitioned from 'running' to 'successful' or
'failed' states. This object is instantiated only
after the row has been instantiated.
Its value will remain 0 until the request has
completed. |
| CON ccCopyFailCause | 1.3.6.1.4.1.9.9.96.1.1.1.1.13 | ConfigCopyFailCause | read-only | The reason why the config-copy operation failed.
This object is instantiated only when the
ccCopyState for this entry is in the
'failed' state. |
| ROW ccCopyEntryRowStatus | 1.3.6.1.4.1.9.9.96.1.1.1.1.14 | RowStatus | read-create | The status of this table entry. Once the entry
status is set to active, the associated entry cannot
be modified until the request completes
(ccCopyState transitions to 'successful'
or 'failed' state). |
| IPt ccCopyServerAddressType | 1.3.6.1.4.1.9.9.96.1.1.1.1.15 | InetAddressType | read-create | This object indicates the transport type of the
address contained in ccCopyServerAddressRev1 object.
This must be created when either the
ccCopySourceFileType or ccCopyDestFileType has the
value 'networkFile'. |
| IP ccCopyServerAddressRev1 | 1.3.6.1.4.1.9.9.96.1.1.1.1.16 | InetAddress | read-create | The IP address of the TFTP server from (or to)
which to copy the configuration file. This object
must be created when either the
ccCopySourceFileType or ccCopyDestFileType has the
value 'networkFile'.
All bits as 0s or 1s for ccCopyServerAddressRev1 are
not allowed.
The format of this address depends on the value of
the ccCopyServerAddressType object. |
| ccCopyErrorTable | 1.3.6.1.4.1.9.9.96.1.1.2 | | not-accessible | 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. |
| ccCopyErrorEntry | 1.3.6.1.4.1.9.9.96.1.1.2.1 | | not-accessible | An entry containing information about the
outcome at one destination of a failed config
copy operation. |
| U32 ccCopyErrorIndex | 1.3.6.1.4.1.9.9.96.1.1.2.1.1 | Unsigned32 | not-accessible | A monotonically increasing integer for the sole
purpose of indexing entries in this table.
When a config copy operation has multiple
destinations, then this index value is used to
distinguish between those multiple destinations. |
| IPt ccCopyErrorDeviceIpAddressType | 1.3.6.1.4.1.9.9.96.1.1.2.1.2 | InetAddressType | read-only | The type of Internet address for this destination
device on which config copy operation is performed. |
| IP ccCopyErrorDeviceIpAddress | 1.3.6.1.4.1.9.9.96.1.1.2.1.3 | InetAddress | read-only | The IP address of this destination device on which
config copy operation is performed.
The object value has to be consistent with the type
specified in ccCopyErrorDeviceIpAddressType. |
| FCN ccCopyErrorDeviceWWN | 1.3.6.1.4.1.9.9.96.1.1.2.1.4 | FcNameIdOrZero | read-only | The World Wide Name (WWN) of this destination
device on which config copy operation is performed.
The value of this object is zero-length string if
WWN is unassigned or unknown. For example, devices
which do not support fibre channel would not
have WWN. |
| STR ccCopyErrorDescription | 1.3.6.1.4.1.9.9.96.1.1.2.1.5 | SnmpAdminString | read-only | The error description for the error happened
for this destination of this config copy
operation. |
| ciscoConfigCopyMIBTrapPrefix | 1.3.6.1.4.1.9.9.96.2 | | | |
| ccCopyMIBTraps | 1.3.6.1.4.1.9.9.96.2.1 | | | |
| NTF ccCopyCompletion | 1.3.6.1.4.1.9.9.96.2.1.1 | | | A ccCopyCompletion trap is sent at the completion
of a config-copy request. The ccCopyFailCause is not
instantiated, and hence not included in a trap, when
the ccCopyState is success. |
| ciscoConfigCopyMIBConformance | 1.3.6.1.4.1.9.9.96.3 | | | |
| ccCopyMIBCompliances | 1.3.6.1.4.1.9.9.96.3.1 | | | |
| ccCopyMIBCompliance | 1.3.6.1.4.1.9.9.96.3.1.1 | | | The compliance statement for Cisco agents which
implement the Cisco ConfigCopy MIB. This MIB should
be implemented on all Cisco agents that support
copying of configs via the CLI.
This compliance is deprecated and new compliance
ccCopyMIBComplianceRev1 is defined. |
| ccCopyMIBComplianceRev1 | 1.3.6.1.4.1.9.9.96.3.1.2 | | | The compliance statement for Cisco agents which
implement the Cisco ConfigCopy MIB. This MIB should
be implemented on all Cisco agents that support
copying of configs via the CLI.
This compliance module deprecates
ccCopyMIBCompliance. |
| ccCopyMIBComplianceRev2 | 1.3.6.1.4.1.9.9.96.3.1.3 | | | The compliance statement for Cisco agents which
implement the Cisco ConfigCopy MIB. This MIB should
be implemented on all Cisco agents that support
copying of configs via the CLI.
This compliance module deprecates
ccCopyMIBComplianceRev1. |
| ccCopyMIBGroups | 1.3.6.1.4.1.9.9.96.3.2 | | | |
| ccCopyGroup | 1.3.6.1.4.1.9.9.96.3.2.1 | | | A collection of objects providing the ability to
copy an agent-configuration file.
This Group is deprecated and new group is defined. |
| ccCopyNotificationsGroup | 1.3.6.1.4.1.9.9.96.3.2.2 | | | The notification used to indicate that a config-copy
operation to or from the agent has been completed. |
| ccCopyGroupRev1 | 1.3.6.1.4.1.9.9.96.3.2.3 | | | A collection of objects providing the ability to
copy an agent-configuration file.
This group deprecates the old group ccCopyGroup. |
| ccCopyErrorGroup | 1.3.6.1.4.1.9.9.96.3.2.4 | | | A collection of objects providing the result
of a config copy operation when the value of
ccCopyDestFileType is 'fabricStartupConfig' and
value of ccCopyState is 'failed'. |
