12-17-2008 10:16 AM - edited 03-06-2019 03:01 AM
When you execute a 'copy tftp flash' command on a device that has different forms of flash, like sup-bootdisk: or bootflash:, where will the file land?
chgsw002-PVT6506#copy tftp flash ?
<cr>
chgsw002-PVT6506#
chgsw002-PVT6506#
chgsw002-PVT6506#
chgsw002-PVT6506#
chgsw002-PVT6506#copy tftp ?
bootflash: Copy to bootflash: file system
const_nvram: Copy to const_nvram: file system
disk0: Copy to disk0: file system
ftp: Copy to ftp: file system
null: Copy to null: file system
nvram: Copy to nvram: file system
rcp: Copy to rcp: file system
running-config Update (merge with) current system configuration
scp: Copy to scp: file system
startup-config Copy to startup configuration
sup-bootdisk: Copy to sup-bootdisk: file system
sup-image: Copy to sup-image: file system
syslog: Copy to syslog: file system
system: Copy to system: file system
tftp: Copy to tftp: file system
tmpsys: Copy to tmpsys: file system
chgsw002-PVT6506#copy tftp
12-17-2008 04:03 PM
Hi Victor,
In my test, it defaulted to disk0:
Rack3-6509#copy tftp flash
Address or name of remote host []? 1.1.1.1
Source filename []? s72033-adventerprisek9_wan-mz.122-18.SXF8.bin
Destination filename [flash]? s72033-adventerprisek9_wan-mz.122-18.SXF8.bin
%Warning:There is a file already existing with this name
Do you want to over write? [confirm]n
Rack3-6509#dir /all
Directory of disk0:/
1 -rw- 80680004 Mar 28 2008 09:06:54 +00:00 s72033-adventerprisek9_wan-mz.122-18.SXF11.bin
2 -rw- 82558532 Jun 30 2008 12:13:48 +00:00 s72033-adventerprisek9_wan-mz.122-18.SXF8.bin
BTW, further testing reveals that the 'flash' is treated as filename and not the destination file system. The option is not valid.
See this example:
Rack3-6509#copy tftp test
Address or name of remote host [1.1.1.1]?
Source filename [s72033-adventerprisek9_wan-mz.122-18.SXF8.bin]?
Destination filename [test]? s72033-adventerprisek9_wan-mz.122-18.SXF8.bin
%Warning:There is a file already existing with this name
Do you want to over write? [confirm]n
__
Edison.
12-18-2008 12:07 PM
"In my test, it defaulted to disk0:"
So I guess the word "flash" in the command is not what directs the device where to place the incoming file.
Interesting. Im wondering what it would default to if a flash card was not in place.
12-18-2008 12:17 PM
Hmm..
Let me try to explain again :)
Flash was not listed as an option in my 6500 switch. It took the word flash in the command as a destination filename.
If I were to use flash: (which is the correct syntax), I get
Rack3-6509#copy tftp: flash:
^
% Invalid input detected at '^' marker.
12-18-2008 03:25 PM
Edison:
I did understand you.
The word 'flash' was taken by the router to be the destination file name, not the destination file system.
If you use the word "flash:" which is the true way to refer to the file system, the router rejects the command -- it isnt an option.
That having been said, you did download a file from the tftp server and the router did send it to disk0: Why? Why not sup-bootdisk: or bootflash: etc?
Thanks
12-19-2008 06:14 AM
On the hardware I tested, the dir /all only presented disk 0: as the only file system available,.
Remember bootdisk is the same as disk 0:. Disk 0: is the reference for file system > 32MB
HTH,
__
Edison.
12-19-2008 07:38 AM
OK, thanks Edison. I am going to investigate further. My switch has sup-bootdisk: bootflash:, etc.
Rated your help
Victor
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: