| 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 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. |