Specifications

Application View Cisco Flash Application
Device Management Page 64 Cisco Router
Source Filename
This field lets you set the source file name, either
in Flash or on a server, depending on the type of
copy command.
For a copy from Flash: File name must be of
the form [<device>:][<partition>:]<file> where
<device> is a value obtained from
FlashDeviceName, <partition> is obtained
from FlashPartitionName and <file> is the
name of a file in Flash. A management station
could derive its own partition name as per the
description for ciscoFlashPartitionName. If
<device> is not specified, the default Flash
device will be assumed. If <partition> is not
specified, the default partition will be
assumed. If a device is not partitioned into 2
or more partitions, this value may be left out.
For a copy to Flash: File name will be as per
the file naming conventions and path to the
file on the server.
Destination Filename
The destination file name.
For a copy to Flash: File name must be of the
form [<device>:][<partition>:]<file> where
<device> is a value obtained from
FlashDeviceName, <partition> is obtained
from FlashPartitionName and <file> is any
character string that does not have embedded
colon characters. A management station
could derive its own partition name as per the
description for the ciscoFlashPartitionName
object. If <device> is not specified, the default
Flash device will be assumed. If <partition> is
not specified, the default partition will be
assumed. If a device is not partitioned into 2
or more partitions, this value may be left out.
If <file> is not specified, it will default to <file>
specified in ciscoFlashCopySourceName.
For a copy from Flash via tftp or rcp, the file
name will be as per the file naming
conventions and destination sub-directory on
the server. If not specified, <file> from the
source file name will be used.
For a copy from Flash via lex, this string will
consist of numeric characters specifying the
interface on the lex box that will receive the
source flash image.
User Name
Remote user name for copy via rcp protocol. This
will be ignored for protocols (Page 63) other than
rcp. If specified, 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.