Tech Support > Computer Hardware > Routers > Ftp ios
Ftp ios
Posted by Bluedog12 on June 4th, 2004


Hi,

I'm trying to copy a ios image using ftp instead of tftp , ftp comes up with
this warning " this is not a valid executable for this system" closing.

How do I accomplish a ios transfer using ftp form a 3com ftp server to a
Cisco 3640 router.

The reason I'm using ftp is that the ios is larger then 16mg ..(18.4mg) when
I use tftp it stops at 16,777321 Cisco say to use ftp as a work around.


Any info much appreciated


Thanks


Posted by jt on June 4th, 2004


Binary mode ?

jt


"Bluedog12" <jkelly33@bigpond.net.au> schrieb im Newsbeitrag
news:vCUvc.5077$rz4.4622@news-server.bigpond.net.au...


Posted by AnyBody43 on June 4th, 2004


"Bluedog12" <jkelly33@bigpond.net.au> wrote in message news:<vCUvc.5077$rz4.4622@news-server.bigpond.net.au>...
The classic ftp problem that newcomers (and others make is to
fail to specify binary mode.

Usually the command "bin" in the ftp client does the trick.
(confusingly the response to the bin command is usually
something about "image mode"). Apparently we are supposed
to know that [image == binary]. Well I do _now_.

The default is usually ASCII mode which causes character
traslation to be active between the two systems. The translation
that most often catches us out is that between Unix and Windows.

IIRC, any CR characters sent from a Unix system to a windows
system are translated to a CF/LF pair. YES, this makes the file
longer. In the reverse direction the file gets shorter.

The cisco image file will almost certainly contain the relevant
characters even if it is only by chance.

Regarding tftp. I have no experience however tftp does allow
longer files. IIRC(again) the 16M limit is a BUG and the limit
should have been 32M but many implementations use signed instead of
unsigned 16bit numbers for the block counter. If you have standards
compliant tftp software it should allow 32M. Secondly (IIRC) tftp
has been EXTENDED to allow larger blocks than the original 512 bytes.
The block count is limited to 64k.

http://perso.wanadoo.fr/philippe.jounin/tftpd32.html
tftp client that supports large blocks and probably
does not suffer from the 32k blocks bug either.

Posted by Bluedog12 on June 4th, 2004


Ok Thanks for the reply
"Bluedog12" <jkelly33@bigpond.net.au> wrote in message
news:vCUvc.5077$rz4.4622@news-server.bigpond.net.au...


Posted by Katanga-Man on June 4th, 2004


I have transferred images of 32Meg and above using 3CDaemon that you mention
and it always works fine.
KM

"Bluedog12" <jkelly33@bigpond.net.au> wrote in message
news:vCUvc.5077$rz4.4622@news-server.bigpond.net.au...


Posted by Simon Marsden on June 4th, 2004



"AnyBody43" <anybody43@hotmail.com> wrote in message
news:3adc58e4.0406040227.6bb56a59@posting.google.c om...