Prev: AQuA Powered Asterisk Voice Quality Monitoring Solution
Next: Quick Best Practices question on VLANs
From: bod43 on 24 May 2010 09:53
On 24 May, 10:57, "terry...(a)o2.ie" <terry...(a)o2.ie> wrote:
> On 21 May, 13:40, Doug McIntyre <mer...(a)geeks.org> wrote:
>
>
>
> > "terry...(a)o2.ie" <terry...(a)o2.ie> writes:
> > >I appear to be totally stuck with a 3725. My compact flash is missing
> > >- there is no image in flash and ROMMON doesn't have a TFTPDNLD
> > >command.
> > >I tried to boot from tftp - that failed as well...
> > >rommon 9 > DEFAULT_GATEWAY=10.1.1.1
> > >rommon 10 > TFTP_SERVER=10.1.1.1
> > >rommon 11 > TFTP_FILE=c3725-advipservicesk9-mz.124-11.XW7.bin
> > >rommon 12 > tftpdnld -r
> > >monitor: command "tftpdnld" not found
>
> > Right, the 3725 doesn't have tftpdnld.. It has xmodem though!
> > If all else fails, jack the console baud rate up to 115,200, and
> > xmodem in the smallest IOS image you can find. It might complete
> > in 4-5 hours for you... Depending on size of course. This is not
> > going to complete quickly.
>
> > There's been way too many 36xx routers I've had to recover for people
> > using xmodem boot. I honestly don't know why they didn't fix that for
> > the 37xx routers. :(
>
> > The TFTP boot line here is probably your best bet to troubleshoot..
>
> > >rommon 13 > boot c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1
> > >program load complete, entry point: 0x80008000, size: 0xb2a0
> > >an alternate boot helper program is not specified
> > >(monitor variable "BOOTLDR" is not set)
> > >and unable to determine first file in bootflash
> > >loadprog: error - on file open
> > >boot: cannot load "c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1"
>
> > Maybe throw a '-v' on the end of the line to see verbose error
> > messages to see what is going on?
>
> > Hmm, reading up on the process here..
>
> >http://www.ciscopowerednetwork.net/en/US/docs/routers/access/3700/har...
>
> > It seems a TFTP boot always needs to have something in CompactFlash to
> > start booting from and then loads the real IOS you want via TFTP.
>
> > I'd have to say that xmodem'ing in the smallest IOS in is your best bet..
>
> Unfortunately I'm now having trouble with XModem
>
> Firstly tried to load c3725-advipservicesk9-mz.124-11.XW7.bin
> (43948KB) but kept getting "BB0
> ERR:File not a valid executable" erors. Then tried a smaller IOS image
> c3725-ipbasek9-mz.124-15.T13.bin (20527KB)
> but it is also throwing up the same message but also the error says it
> is still expecting the original advipservicesk9-mz.124-11.XW7.bin
> image...
>
> rommon 16 >
> rommon 16 > xmodem -r  c3725-ipbasek9-mz.124-15.T13.bin
> Do not start the sending program yet...
>
> Invoke this application only for disaster recovery.
> Do you wish to continue? y/n  [n]:  y
> Ready to receive file c3725-advipservicesk9-mz.124-11.XW7.bin ...
> BB0
> ERR:File not a valid executable
> rommon 17 > confreg

Are the files valid? A common problem is using ftp ascii mode
to transfer the files. Use binary mode always. Just to be clear
I am not taling about the xmodem transfer but a possible
earlier ftp, perhaps from the cisco web site.

cidco publish md5 'checksums' of files. You can check your
files if you have an md5 utility. There is one for windows on
fourmilab.ch in case you are having trouble.
From: terrydoc on 24 May 2010 10:32
On 24 May, 14:53, bod43 <Bo...(a)hotmail.co.uk> wrote:
> On 24 May, 10:57, "terry...(a)o2.ie" <terry...(a)o2.ie> wrote:
>
>
>
>
>
> > On 21 May, 13:40, Doug McIntyre <mer...(a)geeks.org> wrote:
>
> > > "terry...(a)o2.ie" <terry...(a)o2.ie> writes:
> > > >I appear to be totally stuck with a 3725. My compact flash is missing
> > > >- there is no image in flash and ROMMON doesn't have a TFTPDNLD
> > > >command.
> > > >I tried to boot from tftp - that failed as well...
> > > >rommon 9 > DEFAULT_GATEWAY=10.1.1.1
> > > >rommon 10 > TFTP_SERVER=10.1.1.1
> > > >rommon 11 > TFTP_FILE=c3725-advipservicesk9-mz.124-11.XW7.bin
> > > >rommon 12 > tftpdnld -r
> > > >monitor: command "tftpdnld" not found
>
> > > Right, the 3725 doesn't have tftpdnld.. It has xmodem though!
> > > If all else fails, jack the console baud rate up to 115,200, and
> > > xmodem in the smallest IOS image you can find. It might complete
> > > in 4-5 hours for you... Depending on size of course. This is not
> > > going to complete quickly.
>
> > > There's been way too many 36xx routers I've had to recover for people
> > > using xmodem boot. I honestly don't know why they didn't fix that for
> > > the 37xx routers. :(
>
> > > The TFTP boot line here is probably your best bet to troubleshoot..
>
> > > >rommon 13 > boot c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1
> > > >program load complete, entry point: 0x80008000, size: 0xb2a0
> > > >an alternate boot helper program is not specified
> > > >(monitor variable "BOOTLDR" is not set)
> > > >and unable to determine first file in bootflash
> > > >loadprog: error - on file open
> > > >boot: cannot load "c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1"
>
> > > Maybe throw a '-v' on the end of the line to see verbose error
> > > messages to see what is going on?
>
> > > Hmm, reading up on the process here..
>
> > >http://www.ciscopowerednetwork.net/en/US/docs/routers/access/3700/har....
>
> > > It seems a TFTP boot always needs to have something in CompactFlash to
> > > start booting from and then loads the real IOS you want via TFTP.
>
> > > I'd have to say that xmodem'ing in the smallest IOS in is your best bet.
>
> > Unfortunately I'm now having trouble with XModem
>
> > Firstly tried to load c3725-advipservicesk9-mz.124-11.XW7.bin
> > (43948KB) but kept getting "BB0
> > ERR:File not a valid executable" erors. Then tried a smaller IOS image
> > c3725-ipbasek9-mz.124-15.T13.bin (20527KB)
> > but it is also throwing up the same message but also the error says it
> > is still expecting the original advipservicesk9-mz.124-11.XW7.bin
> > image...
>
> > rommon 16 >
> > rommon 16 > xmodem -r  c3725-ipbasek9-mz.124-15.T13.bin
> > Do not start the sending program yet...
>
> > Invoke this application only for disaster recovery.
> > Do you wish to continue? y/n  [n]:  y
> > Ready to receive file c3725-advipservicesk9-mz.124-11.XW7.bin ...
> > BB0
> > ERR:File not a valid executable
> > rommon 17 > confreg
>
> Are the files valid? A common problem is using ftp ascii mode
> to transfer the files. Use binary mode always. Just to be clear
> I am not taling about the xmodem transfer but a possible
> earlier ftp, perhaps from the cisco web site.
>
> cidco publish md5 'checksums' of files. You can check your
> files if  you have an md5 utility. There is one for windows on
> fourmilab.ch in case you are having trouble.- Hide quoted text -
>
> - Show quoted text -

I found my problem - it was in fact a 3745 - i now have the router up
& running with c3745-ipbasek9-mz.124-11.XW7.bin. However, when I try
to tftp: the IOS to flash: or slot0: (compact flash) the tftp always
times out at the same point... I need to get this version into flash:
or onto the compact flash so I can boot as normal.

Router#copy tftp: flash:
Address or name of remote host [10.1.1.2]?
Source filename [c3745-ipbasek9-mz.124-25c.bin]?
Destination filename [c3745-ipbasek9-mz.124-25c.bin]?
Accessing tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin...Router#dir
all
Directory of archive:/

No files in directory

Error getting file system status (Unknown error 0)
Directory of system:/

2 -r-- 0 <no date> default-running-
config
4 dr-x 0 <no date> memory
1 -rw- 596 <no date> running-config
3 dr-x 0 <no date> vfiles

Error getting file system status (Bad file number)
Directory of tmpsys:/

No files in directory

Error getting file system status (Bad file number)
Directory of nvram:/

150 -rw- 596 <no date> startup-config
151 ---- 5 <no date> private-config
1 -rw- 0 <no date> ifIndex-table
2 ---- 13 <no date> persistent-data
155640 bytes total (152939 bytes free)
Directory of flash:/
1 -rw- 611 Mar 1 2002 01:50:34 +00:00 running-config
32296960 bytes total (32292864 bytes free)
Directory of slot0:/
No files in directory
64057344 bytes total (64057344 bytes free)
Router#
Loading c3745-ipbasek9-mz.124-25c.bin from 10.1.1.2 (via
FastEthernet0/0): !!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.O.O.O
[timed out]

%Error reading tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin (Timed
out)
Router#
From: bod43 on 24 May 2010 11:02
On 24 May, 15:32, "terry...(a)o2.ie" <terry...(a)o2.ie> wrote:
> On 24 May, 14:53, bod43 <Bo...(a)hotmail.co.uk> wrote:
>
>
>
> > On 24 May, 10:57, "terry...(a)o2.ie" <terry...(a)o2.ie> wrote:
>
> > > On 21 May, 13:40, Doug McIntyre <mer...(a)geeks.org> wrote:
>
> > > > "terry...(a)o2.ie" <terry...(a)o2.ie> writes:
> > > > >I appear to be totally stuck with a 3725. My compact flash is missing
> > > > >- there is no image in flash and ROMMON doesn't have a TFTPDNLD
> > > > >command.
> > > > >I tried to boot from tftp - that failed as well...
> > > > >rommon 9 > DEFAULT_GATEWAY=10.1.1.1
> > > > >rommon 10 > TFTP_SERVER=10.1.1.1
> > > > >rommon 11 > TFTP_FILE=c3725-advipservicesk9-mz.124-11.XW7.bin
> > > > >rommon 12 > tftpdnld -r
> > > > >monitor: command "tftpdnld" not found
>
> > > > Right, the 3725 doesn't have tftpdnld.. It has xmodem though!
> > > > If all else fails, jack the console baud rate up to 115,200, and
> > > > xmodem in the smallest IOS image you can find. It might complete
> > > > in 4-5 hours for you... Depending on size of course. This is not
> > > > going to complete quickly.
>
> > > > There's been way too many 36xx routers I've had to recover for people
> > > > using xmodem boot. I honestly don't know why they didn't fix that for
> > > > the 37xx routers. :(
>
> > > > The TFTP boot line here is probably your best bet to troubleshoot..
>
> > > > >rommon 13 > boot c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1
> > > > >program load complete, entry point: 0x80008000, size: 0xb2a0
> > > > >an alternate boot helper program is not specified
> > > > >(monitor variable "BOOTLDR" is not set)
> > > > >and unable to determine first file in bootflash
> > > > >loadprog: error - on file open
> > > > >boot: cannot load "c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1"
>
> > > > Maybe throw a '-v' on the end of the line to see verbose error
> > > > messages to see what is going on?
>
> > > > Hmm, reading up on the process here..
>
> > > >http://www.ciscopowerednetwork.net/en/US/docs/routers/access/3700/har...
>
> > > > It seems a TFTP boot always needs to have something in CompactFlash to
> > > > start booting from and then loads the real IOS you want via TFTP.
>
> > > > I'd have to say that xmodem'ing in the smallest IOS in is your best bet.
>
> > > Unfortunately I'm now having trouble with XModem
>
> > > Firstly tried to load c3725-advipservicesk9-mz.124-11.XW7.bin
> > > (43948KB) but kept getting "BB0
> > > ERR:File not a valid executable" erors. Then tried a smaller IOS image
> > > c3725-ipbasek9-mz.124-15.T13.bin (20527KB)
> > > but it is also throwing up the same message but also the error says it
> > > is still expecting the original advipservicesk9-mz.124-11.XW7.bin
> > > image...
>
> > > rommon 16 >
> > > rommon 16 > xmodem -r  c3725-ipbasek9-mz.124-15.T13.bin
> > > Do not start the sending program yet...
>
> > > Invoke this application only for disaster recovery.
> > > Do you wish to continue? y/n  [n]:  y
> > > Ready to receive file c3725-advipservicesk9-mz.124-11.XW7.bin ...
> > > BB0
> > > ERR:File not a valid executable
> > > rommon 17 > confreg
>
> > Are the files valid? A common problem is using ftp ascii mode
> > to transfer the files. Use binary mode always. Just to be clear
> > I am not taling about the xmodem transfer but a possible
> > earlier ftp, perhaps from the cisco web site.
>
> > cidco publish md5 'checksums' of files. You can check your
> > files if  you have an md5 utility. There is one for windows on
> > fourmilab.ch in case you are having trouble.- Hide quoted text -
>
> > - Show quoted text -
>
> I found my problem - it was in fact a 3745 - i now have the router up
> & running with c3745-ipbasek9-mz.124-11.XW7.bin. However, when I try
> to tftp: the IOS to flash: or slot0: (compact flash) the tftp always
> times out at the same point... I need to get this version into flash:
> or onto the compact flash so I can boot as normal.
>
> Router#copy tftp: flash:
> Address or name of remote host [10.1.1.2]?
> Source filename [c3745-ipbasek9-mz.124-25c.bin]?
> Destination filename [c3745-ipbasek9-mz.124-25c.bin]?
> Accessing tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin...Router#dir
> all
> Directory of archive:/
>
> No files in directory
>
> Error getting file system status (Unknown error 0)
> Directory of system:/
>
>     2  -r--           0                    <no date>  default-running-
> config
>     4  dr-x           0                    <no date>  memory
>     1  -rw-         596                    <no date>  running-config
>     3  dr-x           0                    <no date>  vfiles
>
> Error getting file system status (Bad file number)
> Directory of tmpsys:/
>
> No files in directory
>
> Error getting file system status (Bad file number)
> Directory of nvram:/
>
>   150  -rw-         596                    <no date>  startup-config
>   151  ----           5                    <no date>  private-config
>     1  -rw-           0                    <no date>  ifIndex-table
>     2  ----          13                    <no date>  persistent-data
> 155640 bytes total (152939 bytes free)
> Directory of flash:/
>     1  -rw-         611   Mar 1 2002 01:50:34 +00:00  running-config
> 32296960 bytes total (32292864 bytes free)
> Directory of slot0:/
> No files in directory
> 64057344 bytes total (64057344 bytes free)
> Router#
> Loading c3745-ipbasek9-mz.124-25c.bin from 10.1.1.2 (via
> FastEthernet0/0): !!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.O.O.O
> [timed out]
>
> %Error reading tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin(Timed
> out)
> Router#

"O" is out of order packet. Make sure that you don't
have a duplex mismatch between the client and the server.
tftp is not good at recovering from errors.
Start with everything at auto-speed/auto-dup.

Some old tftp clients has bugs. I forget the details now.
Use tftpd32.exe if you are on Windows but make sure that it's
dhcp server does not cause problems on your network.
tftpd32.exe is a perfect tftp server - except that if now comes
with unwanted baggage:-)


Run a packet capture on your PC.

From: Daniel-G on 24 May 2010 19:10
terrydoc(a)o2.ie said the following on 05/24/2010 04:32 PM:
> On 24 May, 14:53, bod43 <Bo...(a)hotmail.co.uk> wrote:
>> On 24 May, 10:57, "terry...(a)o2.ie" <terry...(a)o2.ie> wrote:
>>
>>
>>
>>
>>
>>> On 21 May, 13:40, Doug McIntyre <mer...(a)geeks.org> wrote:
>>
>>>> "terry...(a)o2.ie" <terry...(a)o2.ie> writes:
>>>>> I appear to be totally stuck with a 3725. My compact flash is missing
>>>>> - there is no image in flash and ROMMON doesn't have a TFTPDNLD
>>>>> command.
>>>>> I tried to boot from tftp - that failed as well...
>>>>> rommon 9 > DEFAULT_GATEWAY=10.1.1.1
>>>>> rommon 10 > TFTP_SERVER=10.1.1.1
>>>>> rommon 11 > TFTP_FILE=c3725-advipservicesk9-mz.124-11.XW7.bin
>>>>> rommon 12 > tftpdnld -r
>>>>> monitor: command "tftpdnld" not found
>>
>>>> Right, the 3725 doesn't have tftpdnld.. It has xmodem though!
>>>> If all else fails, jack the console baud rate up to 115,200, and
>>>> xmodem in the smallest IOS image you can find. It might complete
>>>> in 4-5 hours for you... Depending on size of course. This is not
>>>> going to complete quickly.
>>
>>>> There's been way too many 36xx routers I've had to recover for people
>>>> using xmodem boot. I honestly don't know why they didn't fix that for
>>>> the 37xx routers. :(
>>
>>>> The TFTP boot line here is probably your best bet to troubleshoot..
>>
>>>>> rommon 13 > boot c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1
>>>>> program load complete, entry point: 0x80008000, size: 0xb2a0
>>>>> an alternate boot helper program is not specified
>>>>> (monitor variable "BOOTLDR" is not set)
>>>>> and unable to determine first file in bootflash
>>>>> loadprog: error - on file open
>>>>> boot: cannot load "c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1"
>>
>>>> Maybe throw a '-v' on the end of the line to see verbose error
>>>> messages to see what is going on?
>>
>>>> Hmm, reading up on the process here..
>>
>>>> http://www.ciscopowerednetwork.net/en/US/docs/routers/access/3700/har...
>>
>>>> It seems a TFTP boot always needs to have something in CompactFlash to
>>>> start booting from and then loads the real IOS you want via TFTP.
>>
>>>> I'd have to say that xmodem'ing in the smallest IOS in is your best bet.
>>
>>> Unfortunately I'm now having trouble with XModem
>>
>>> Firstly tried to load c3725-advipservicesk9-mz.124-11.XW7.bin
>>> (43948KB) but kept getting "BB0
>>> ERR:File not a valid executable" erors. Then tried a smaller IOS image
>>> c3725-ipbasek9-mz.124-15.T13.bin (20527KB)
>>> but it is also throwing up the same message but also the error says it
>>> is still expecting the original advipservicesk9-mz.124-11.XW7.bin
>>> image...
>>
>>> rommon 16 >
>>> rommon 16 > xmodem -r c3725-ipbasek9-mz.124-15.T13.bin
>>> Do not start the sending program yet...
>>
>>> Invoke this application only for disaster recovery.
>>> Do you wish to continue? y/n [n]: y
>>> Ready to receive file c3725-advipservicesk9-mz.124-11.XW7.bin ...
>>> BB0
>>> ERR:File not a valid executable
>>> rommon 17 > confreg
>>
>> Are the files valid? A common problem is using ftp ascii mode
>> to transfer the files. Use binary mode always. Just to be clear
>> I am not taling about the xmodem transfer but a possible
>> earlier ftp, perhaps from the cisco web site.
>>
>> cidco publish md5 'checksums' of files. You can check your
>> files if you have an md5 utility. There is one for windows on
>> fourmilab.ch in case you are having trouble.- Hide quoted text -
>>
>> - Show quoted text -
>
> I found my problem - it was in fact a 3745 - i now have the router up
> & running with c3745-ipbasek9-mz.124-11.XW7.bin. However, when I try
> to tftp: the IOS to flash: or slot0: (compact flash) the tftp always
> times out at the same point... I need to get this version into flash:
> or onto the compact flash so I can boot as normal.
>
> Router#copy tftp: flash:
> Address or name of remote host [10.1.1.2]?
> Source filename [c3745-ipbasek9-mz.124-25c.bin]?
> Destination filename [c3745-ipbasek9-mz.124-25c.bin]?
> Accessing tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin...Router#dir
> all
> Directory of archive:/
>
> No files in directory
>
> Error getting file system status (Unknown error 0)
> Directory of system:/
>
> 2 -r-- 0 <no date> default-running-
> config
> 4 dr-x 0 <no date> memory
> 1 -rw- 596 <no date> running-config
> 3 dr-x 0 <no date> vfiles
>
> Error getting file system status (Bad file number)
> Directory of tmpsys:/
>
> No files in directory
>
> Error getting file system status (Bad file number)
> Directory of nvram:/
>
> 150 -rw- 596 <no date> startup-config
> 151 ---- 5 <no date> private-config
> 1 -rw- 0 <no date> ifIndex-table
> 2 ---- 13 <no date> persistent-data
> 155640 bytes total (152939 bytes free)
> Directory of flash:/
> 1 -rw- 611 Mar 1 2002 01:50:34 +00:00 running-config
> 32296960 bytes total (32292864 bytes free)
> Directory of slot0:/
> No files in directory
> 64057344 bytes total (64057344 bytes free)
> Router#
> Loading c3745-ipbasek9-mz.124-25c.bin from 10.1.1.2 (via
> FastEthernet0/0): !!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.O.O.O
> [timed out]
>
> %Error reading tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin (Timed
> out)
> Router#
I had this once with a tftp server : the image got stuck at the same
point during transfers (I always check CRC before uploading)
I changed the tftp server to tftp32 (from Jounin) and it ran fine (the
upload)
As the problem was fixed I did not take time to look for the exact
reason why (interactions with Antivirus, mem corruption on my laptop,
anything more strange ..)



From: bod43 on 25 May 2010 05:03
On 25 May, 00:10, Daniel-G <free-news_no-replyATcasylde.fr> wrote:
> terry...(a)o2.ie said the following on 05/24/2010 04:32 PM:
>
> > On 24 May, 14:53, bod43 <Bo...(a)hotmail.co.uk> wrote:
> >> On 24 May, 10:57, "terry...(a)o2.ie" <terry...(a)o2.ie> wrote:
>
> >>> On 21 May, 13:40, Doug McIntyre <mer...(a)geeks.org> wrote:
>
> >>>> "terry...(a)o2.ie" <terry...(a)o2.ie> writes:
> >>>>> I appear to be totally stuck with a 3725. My compact flash is missing
> >>>>> - there is no image in flash and ROMMON doesn't have a TFTPDNLD
> >>>>> command.
> >>>>> I tried to boot from tftp - that failed as well...
> >>>>> rommon 9 > DEFAULT_GATEWAY=10.1.1.1
> >>>>> rommon 10 > TFTP_SERVER=10.1.1.1
> >>>>> rommon 11 > TFTP_FILE=c3725-advipservicesk9-mz.124-11.XW7.bin
> >>>>> rommon 12 > tftpdnld -r
> >>>>> monitor: command "tftpdnld" not found
>
> >>>> Right, the 3725 doesn't have tftpdnld.. It has xmodem though!
> >>>> If all else fails, jack the console baud rate up to 115,200, and
> >>>> xmodem in the smallest IOS image you can find. It might complete
> >>>> in 4-5 hours for you... Depending on size of course. This is not
> >>>> going to complete quickly.
>
> >>>> There's been way too many 36xx routers I've had to recover for people
> >>>> using xmodem boot. I honestly don't know why they didn't fix that for
> >>>> the 37xx routers. :(
>
> >>>> The TFTP boot line here is probably your best bet to troubleshoot..
>
> >>>>> rommon 13 > boot c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1
> >>>>> program load complete, entry point: 0x80008000, size: 0xb2a0
> >>>>> an alternate boot helper program is not specified
> >>>>> (monitor variable "BOOTLDR" is not set)
> >>>>> and unable to determine first file in bootflash
> >>>>> loadprog: error - on file open
> >>>>> boot: cannot load "c3725-advipservicesk9-mz.124-11.XW7.bin 10.1.1.1"
>
> >>>> Maybe throw a '-v' on the end of the line to see verbose error
> >>>> messages to see what is going on?
>
> >>>> Hmm, reading up on the process here..
>
> >>>>http://www.ciscopowerednetwork.net/en/US/docs/routers/access/3700/har....
>
> >>>> It seems a TFTP boot always needs to have something in CompactFlash to
> >>>> start booting from and then loads the real IOS you want via TFTP.
>
> >>>> I'd have to say that xmodem'ing in the smallest IOS in is your best bet.
>
> >>> Unfortunately I'm now having trouble with XModem
>
> >>> Firstly tried to load c3725-advipservicesk9-mz.124-11.XW7.bin
> >>> (43948KB) but kept getting "BB0
> >>> ERR:File not a valid executable" erors. Then tried a smaller IOS image
> >>> c3725-ipbasek9-mz.124-15.T13.bin (20527KB)
> >>> but it is also throwing up the same message but also the error says it
> >>> is still expecting the original advipservicesk9-mz.124-11.XW7.bin
> >>> image...
>
> >>> rommon 16 >
> >>> rommon 16 > xmodem -r  c3725-ipbasek9-mz.124-15.T13.bin
> >>> Do not start the sending program yet...
>
> >>> Invoke this application only for disaster recovery.
> >>> Do you wish to continue? y/n  [n]:  y
> >>> Ready to receive file c3725-advipservicesk9-mz.124-11.XW7.bin ...
> >>> BB0
> >>> ERR:File not a valid executable
> >>> rommon 17 > confreg
>
> >> Are the files valid? A common problem is using ftp ascii mode
> >> to transfer the files. Use binary mode always. Just to be clear
> >> I am not taling about the xmodem transfer but a possible
> >> earlier ftp, perhaps from the cisco web site.
>
> >> cidco publish md5 'checksums' of files. You can check your
> >> files if  you have an md5 utility. There is one for windows on
> >> fourmilab.ch in case you are having trouble.- Hide quoted text -
>
> >> - Show quoted text -
>
> > I found my problem - it was in fact a 3745 - i now have the router up
> > & running with c3745-ipbasek9-mz.124-11.XW7.bin. However, when I try
> > to tftp: the IOS to flash: or slot0: (compact flash) the tftp always
> > times out at the same point... I need to get this version into flash:
> > or onto the compact flash so I can boot as normal.
>
> > Router#copy tftp: flash:
> > Address or name of remote host [10.1.1.2]?
> > Source filename [c3745-ipbasek9-mz.124-25c.bin]?
> > Destination filename [c3745-ipbasek9-mz.124-25c.bin]?
> > Accessing tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin...Router#dir
> > all
> > Directory of archive:/
>
> > No files in directory
>
> > Error getting file system status (Unknown error 0)
> > Directory of system:/
>
> >     2  -r--           0                    <no date>  default-running-
> > config
> >     4  dr-x           0                    <no date>  memory
> >     1  -rw-         596                    <no date>  running-config
> >     3  dr-x           0                    <no date>  vfiles
>
> > Error getting file system status (Bad file number)
> > Directory of tmpsys:/
>
> > No files in directory
>
> > Error getting file system status (Bad file number)
> > Directory of nvram:/
>
> >   150  -rw-         596                    <no date>  startup-config
> >   151  ----           5                    <no date>  private-config
> >     1  -rw-           0                    <no date>  ifIndex-table
> >     2  ----          13                    <no date>  persistent-data
> > 155640 bytes total (152939 bytes free)
> > Directory of flash:/
> >     1  -rw-         611   Mar 1 2002 01:50:34 +00:00  running-config
> > 32296960 bytes total (32292864 bytes free)
> > Directory of slot0:/
> > No files in directory
> > 64057344 bytes total (64057344 bytes free)
> > Router#
> > Loading c3745-ipbasek9-mz.124-25c.bin from 10.1.1.2 (via
> > FastEthernet0/0): !!!!!
> > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.O.O.O
> > [timed out]
>
> > %Error reading tftp://10.1.1.2/c3745-ipbasek9-mz.124-25c.bin(Timed
> > out)
> > Router#
>
> I had this once with a tftp server : the image got stuck at the same
> point during transfers (I always check CRC before uploading)
> I changed the tftp server to tftp32 (from Jounin) and it ran fine (the
> upload)
> As the problem was fixed I did not take time to look for the exact
> reason why (interactions with Antivirus, mem corruption on my laptop,
> anything more strange ..)

As Dan has mentioned on the other thread you started,
use ftp instead if problems persist. If you use Windows
Serv-U is easy to get going. If the server insists on a
username/password they look like this on the cisco
command line.

copy ftp://user:pass(a)1.2.3.4/filename flash

It's a standard URL format.


First  |  Prev  | 
Pages: 1 2
Prev: AQuA Powered Asterisk Voice Quality Monitoring Solution
Next: Quick Best Practices question on VLANs