A configuration 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 arubaWiredConfigurationCopySourceFileType and arubaWiredConfigurationCopyDestFileType. Only one of the source or destination file types can be 'externalFile'. If one of the file types is a 'externalFile', the following values are expected as well: - arubaWiredConfigurationCopyProtocol - arubaWiredConfigurationCopyFileName - arubaWiredConfigurationCopyServerAddressType - arubaWiredConfigurationCopyServerAddress If the 'externalFile' is the destination, then a valid arubaWiredConfigurationCopyFileFormat is required as well. If authentication is required, then both arubaWiredConfigurationCopyUserName and arubaWiredConfigurationCopyUserPassword are necessary. 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 configuration copy request has been created (i.e. the arubaWiredConfigurationCopyEntryRowStatus 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.