CISCO-CONFIG-COPY-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-CONFIG-COPY-MIB and use it to monitor vendor specific OID's.

CISCO-CONFIG-COPY-MIB file content

Object view of CISCO-CONFIG-COPY-MIB:

Scalar Object
ccCopyEntry	.1.3.6.1.4.1.9.9.96.1.1.1.1
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 FileTypes must be an agent-config file type (i.e. startupConfig or runningConfig). If one of the file types is a networkFile, a valid ccCopyServerAddress and ccCopyFileName must be created as well. For a file type of iosFile, only a valid fileName 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 never be deleted within 5 minutes of completing.
Tabular Object
ccCopyIndex	.1.3.6.1.4.1.9.9.96.1.1.1.1.1
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.
ccCopyProtocol	.1.3.6.1.4.1.9.9.96.1.1.1.1.2
The protocol to be used for any copy. Will default to tftp if not specified. If the copy operation occurs locally on the SNMP agent (e.g. runningCOnfigToStartupConfig), this object may be ignored by the implementation.
ccCopySourceFileType	.1.3.6.1.4.1.9.9.96.1.1.1.1.3
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 and ccCopyFileName must also be created, and these 3 objects together (ccCopySourceFileType, ccCopyServerAddress, ccCopyFileName) will uniquely identify the source file. If the ccCopySourceFileType is iosFile, the ccCopyFileName must also be created, and the 2 objects together (ccCopySourceFileType, ccCopyFileName) will uniquely identify the source file.
ccCopyDestFileType	.1.3.6.1.4.1.9.9.96.1.1.1.1.4
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 and ccCopyFileName must also be created, and these 3 objects together (ccCopyDestFileType, ccCopyServerAddress, ccCopyFileName) will uniquely identify the destination file. If the ccCopyDestFileType is iosFile, the ccCopyFileName must also be created, and the 2 objects together (ccCopyDestFileType, ccCopyFileName) will uniquely identify the destination file.
ccCopyServerAddress	.1.3.6.1.4.1.9.9.96.1.1.1.1.5
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.
ccCopyFileName	.1.3.6.1.4.1.9.9.96.1.1.1.1.6
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.
ccCopyUserName	.1.3.6.1.4.1.9.9.96.1.1.1.1.7
Remote user name 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 user-name configured through the rcmd remote-username <username> configuration command. The remote user-name is sent as the server user-name in an rcp command request sent by the system to a remote rcp server.
ccCopyUserPassword	.1.3.6.1.4.1.9.9.96.1.1.1.1.8
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.
ccCopyNotificationOnCompletion	.1.3.6.1.4.1.9.9.96.1.1.1.1.9
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.
ccCopyState	.1.3.6.1.4.1.9.9.96.1.1.1.1.10
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.
ccCopyTimeStarted	.1.3.6.1.4.1.9.9.96.1.1.1.1.11
Specifies the time the ccCopyState last transitioned to running, or 0 if the state has never transitioned to running (for e.g., stuck in waiting state). This object is instantiated only after the row has been instantiated.
ccCopyTimeCompleted	.1.3.6.1.4.1.9.9.96.1.1.1.1.12
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 he request has completed.
ccCopyFailCause	.1.3.6.1.4.1.9.9.96.1.1.1.1.13
The reason why the config-copy operation failed. This object is instantiated only when the ccCopyState for this entry is in the failed state.
ccCopyEntryRowStatus	.1.3.6.1.4.1.9.9.96.1.1.1.1.14
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).
Table
ccCopyTable	.1.3.6.1.4.1.9.9.96.1.1.1
A table of config-copy requests.
Trap
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.
Object Identifier
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
ciscoConfigCopyMIBTrapPrefix	.1.3.6.1.4.1.9.9.96.2
ccCopyMIBTraps	.1.3.6.1.4.1.9.9.96.2.1
ciscoConfigCopyMIBConformance	.1.3.6.1.4.1.9.9.96.3
ccCopyMIBCompliances	.1.3.6.1.4.1.9.9.96.3.1
ccCopyMIBGroups	.1.3.6.1.4.1.9.9.96.3.2
Group
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.
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.