I had some really strange problem when trying to boot from tftp server for a
7200 running 12.1(5). Just curious whether anyone has seen this or not.

1. Here's the original config which doesn't work:
boot system tftp c7200-js-mz.121-6.bin 10.0.0.248
boot system flash c7200-is-mz.121-5.bin

I also have a tcpdump running on the 10.0.0.248 server and did not see any
packet coming in for tftp at all.

2. Although I am pretty certain that I don't have to put the path tftpboot
since that's the default dir on my server, we decided to add one line with
path for test:

boot system tftp tftpboot/c7200-js-mz.121-6.bin 10.0.0.248
boot system tftp c7200-js-mz.121-6.bin 10.0.0.248
boot system flash c7200-is-mz.121-5.bin

surprisingly, after the first line fails, the seond line kicks in this time
and I saw the reqeust from tcpdump(note the second line is the same as one I
had in step 1):

%Error opening tftp://10.0.0.248/tftpboot/c7200-js-mz.121-6.bin (Timed out)
Loading c7200-js-mz.121-6.bin from 10.0.0.248 (via FastEthernet1/0): !!!!!!!

3. Since this doesn't make sense as why I can't use the "boot system tftp
c7200-js-mz.121-6.bin 10.0.0.248" directly. I decided to try even more crazy
things and it works:

boot system tftp c7200-js-mz.121-4.bin 10.0.0.249
boot system tftp c7200-js-mz.121-6.bin 10.0.0.248
boot system flash c7200-is-mz.121-5.bin

That there aren't even a tftp server at 10.0.0.249 at all. The only reason
why we added this line was that we thought that there was a bug in the Cisco
so that you have to trigger the tftp process first before it starts working.

Note that in both step2,3 , we did not see any request for the first line of
boot system config while we see the second line.

I know this doesn't make too much sense, just curious whether anyone has
seen this.

Thanks.

Richard


_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to