WLC code upgrade via tftp from a switch bootflash

Unanswered Question
Sep 22nd, 2010
User Badges:

Guys,


I got a replacement for a WLC.

We made the replacement and, when upgrading the code, I got an error message. This is because I am running tftp for the remote location and it gets timeout after a while due the latency.

I was not able to run ftp because of some restrictions.


I could transfer the code to a switch near from the WLC so there will not be problems with latency anymore.


The problem now, is that the WLC hits the switch but does not find the file...


Mode............................................. TFTP
Data Type........................................ Code
TFTP Server IP................................... x.x.x.x
TFTP Packet Timeout.............................. 6
TFTP Max Retries................................. 10
TFTP Path........................................ bootflash:/
TFTP Filename.................................... AIR-WLC4400-K9-3-2-215-0.aes

This may take some time.
Are you sure you want to start? (y/N) y

TFTP Code transfer starting.

Code file transfer failed - Error from server: No such file


I also tried using the path as "." only and got the same error.



The switch is a Catalyst 4500.

The code was put in the bootflash.


sh bootflash: | i AIR-WLC4400-K9-3-2-215-0.aes

5   .. ascii text   76737DBF 2BE1BB8   28 20455604 Sep 22 2010 19:01:30 +01:00 AIR-WLC4400-K9-3-2-215-0.aes

The switch configuration for tftp is as follows:


ip tftp source-interface vlan10

tftp-server bootflash:AIR-WLC4400-K9-3-2-215-0.aes



WLC model: AIR-WLC4402-50-K9

Current code version: 3.2.150.10

Intermediary code that I want to download: AIR-WLC4400-K9-3-2-215-0.aes



Thanks in advance

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ronaldobf Wed, 09/22/2010 - 16:56
User Badges:

When making the tftp, I ran a debug:


(Cisco Controller) >debug transfer tftp enable

(Cisco Controller) >Wed Sep 22 16:09:20 2010: RESULT_STRING: TFTP Code transfer starting.
Wed Sep 22 16:09:20 2010: RESULT_CODE:1
Wed Sep 22 16:09:23 2010: Still waiting!  Status = 2
Wed Sep 22 16:09:24 2010: Locking tftp semaphore, pHost=x.x.x.x pFilename=./AIR-WLC4400-K9-3-2-215-0.aes
Wed Sep 22 16:09:24 2010: Semaphore locked, now unlocking, pHost=x.x.x.x pFilename=./AIR-WLC4400-K9-3-2-215-0.aes
Wed Sep 22 16:09:24 2010: Semaphore successfully unlocked, pHost=x.x.x.x pFilename=./AIR-WLC4400-K9-3-2-215-0.aes
Wed Sep 22 16:09:24 2010: TFTP: Binding to local=0.0.0.0 remote=x.x.x.x
Wed Sep 22 16:09:26 2010: Still waiting!  Status = 1
Wed Sep 22 16:09:29 2010: Still waiting!  Status = 1
Wed Sep 22 16:09:30 2010: tftp rc=1, pHost=x.x.x.x pFilename=./AIR-WLC4400-K9-3-2-215-0.aes
                                                                                                     pLocalFilename=/mnt/download/local.tgz
Wed Sep 22 16:09:30 2010: tftp = 4, file_name=./AIR-WLC4400-K9-3-2-215-0.aes, ip_address=x.x.x.x, msg=Error from server: No such file
Wed Sep 22 16:09:30 2010: upd_get_code_via_tftp = 4 (target=297074688 msg=Error from server: No such file)
Wed Sep 22 16:09:30 2010: RESULT_STRING: Code file transfer failed - Error from server: No such file
Wed Sep 22 16:09:30 2010: RESULT_CODE:12
Wed Sep 22 16:09:30 2010: ummounting:   cwd  = /mnt/application
Wed Sep 22 16:09:30 2010: finished umounting

ronaldobf Thu, 09/23/2010 - 09:13
User Badges:

It worked now.


For some reason, the default path for the switch is different from the one I declared in the tftp-server command (bootflash)


Using "." or "bootflash:/" or any other did not work yesterday.


I remember to use also only a "/". Anyway, today we did it again using "/", and it worked fine. Maybe I did not use it.. not sure for now.


There is only the bootflash... nothing more.


Now, a question raised... What is the default directory for a catalyst 4500?

7tclark Wed, 12/11/2013 - 10:07
User Badges:

Ran into similar problem using bootdisk:filename.aes on the switch. a path of "/" did not work. When I moved the file to another switch with a flash: directory the "/" path works. Seems the TFTP will not work from the bootdisk: directory as all path options tested returned the same No such file error seen in this post.

Actions

This Discussion

 

 

Trending Topics - Security & Network