Lightweight Mode Upgrade Tool

Unanswered Question
Jun 5th, 2008

I have installed the latest version of the tool, 3.4, and installed it on an XP SP2 box. Everything looks good, but when I start it returns "C:\Program Files\Cisco Systems\Upgrade Tool\images\c1310-rcvk9w8-tar.124-10b.JA3 - LWAPP Recovery Image is not a valid one".

I have verified that the file exists and is named correctly. I have also downloaded a new copy of the application and image and installed on a different computer and got the same results. Any ideas?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.8 (4 ratings)
Loading.
rob.huffman Thu, 06/05/2008 - 15:08

Hi EMKF,

I don't think the problem is with the tool it is with this image "c1310-rcvk9w8-tar.124-10b.JA3" I don't know why they have linked this in the Software Downloads to the LWAPP Upgrade image but I'm pretty sure it is wrong.

As far as I know all recovery images are JX (not JA etc.)

I would try this image instead;

12.3(11)JX1.

Note This release must only be loaded onto access points at the factory or by using the Autonomous to Lightweight Mode upgrade tool. Your access point might become inoperable if you install this software without using the upgrade tool.

Release Notes for Cisco Aironet 1100, 1130, 1200, 1230, 1240, and 1300 Series Access Points for Cisco IOS Release 12.3(11)JX1

http://www.cisco.com/en/US/docs/wireless/access_point/ios/release/notes/b311jx1.html

c1310-rcvk9w8-tar.123-11JX1.tar

Here is the link;

http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=12.3(11)JX1&mdfid=279141937&sftType=Autonomous%20To%20Lightweight%20Mode%20Upgrade%20Image&optPlat=&nodecount=3&edesignator=null&modelName=Cisco%20Aironet%201310%20Access%20Point/Bridge&treeMdfId=278875243&treeName=Wireless&modifmdfid=null&imname=null&hybrid=Y&imst=N&lr=Y

Check out these notes (no mention of LWAPP Upgrade image)

Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(10b)JA3

http://www.cisco.com/en/US/docs/wireless/access_point/ios/release/notes/12_4_10b_JA3rn.html

Hope this helps!

Rob

emkf Mon, 06/09/2008 - 11:05

Rob,

I downloaded the previous version that was listed under the one that I was trying. It worked just fine and I now have the unit running in LW mode.

Thankd for the response, I appreciate the help.

--Rob

rob.huffman Mon, 06/09/2008 - 14:03

Hi Rob,

You are most welcome my friend :) Glad to be of some small help.

Take care,

Rob

fabian.huebner Tue, 07/01/2008 - 14:01

I have the the same problem - but with a 1250 AccessPoint!

I tried the Autonomous To Lightweight Mode Upgrade Tool 3.0, 3.2 & 3.4.

I used following "Autonomous To Lightweight Mode Upgrade"-Images:

c1250-rcvk9w8-tar.124-13d.JA.tar

c1250-rcvk9w8-tar.124-10b.JA3.tar

c1250-rcvk9w8-tar.124-10b.JA.tar

(with and without the .tar extensions)

Everytime I got "LWAPP Recovery Image is not a valid one".

I also have verified that the file exists and is named correctly.

Kind regards

Fabian

Scott Fella Tue, 07/01/2008 - 20:34

With 1252's you have to use the archive command and tftp the rcv image to the ap.

You need to have the lwapp image on your tftp server and use the archive /r /f tftp:[[//location]/directory]/image-name.tar flash: command.

The image has to be renamed to c1250-k9w7-tar.default. You can use c1250-k9w7-tar.124-10b.JA.tar image file and just rename it. Once the ap joins the wlc, the ap will get whatever code from the wlc

fabian.huebner Wed, 07/02/2008 - 12:53

Thanx for your advice. It works now! :-)

I used archive download-sw /forced-reload tftp://[ip]/c1250-k9w8-tar.default

It's a little bit confusing, that I can't use the Upgrade Tool for these new AP 1250 also. But anyway...

Now I got some unrecognized commands within bootup process:

ip ssh version 2

^

% Invalid input detected at '^' marker.

transport input ssh

^

% Invalid input detected at '^' marker.

aaa new-model

^

% Invalid input detected at '^' marker.

aaa authentication login default local

^

% Invalid input detected at '^' marker.

login authentication default

^

% Invalid input detected at '^' marker.

transport input ssh

^

% Invalid input detected at '^' marker.

logging origin-id string AP:0021.d88a.4040

^

% Invalid input detected at '^' marker.

logging 255.255.255.255

^

% Invalid input detected at '^' marker.

logging trap 3

^

% Invalid input detected at '^' marker.

Any chance to delete the command from the startup-config? Because within the recovery lwapp image I got reduced functionality and commands.

Kind regards

Fabian

Scott Fella Wed, 07/02/2008 - 13:04

When you convert to lwapp, a WLC is required to configure the access point. You can't issues a config t and set ip address etc. You need to do all that from the wlc.

fabian.huebner Wed, 07/02/2008 - 13:13

Yes I know. But hopefully I can swipe these "incorrect commands" from the ap when I'll connect the ap to the wlc.

Thanx

Scott Fella Wed, 07/02/2008 - 13:32

Are you trying to enter thoses commands, or is this what you see when you are consoled into the ap and you boot it up?

fabian.huebner Wed, 07/02/2008 - 13:42

I see this when I'm consoled into the ap and ap is booting up?

I think these are "old orphaned" commands from the "autonomous ap" configuration.

fabian.huebner Wed, 07/02/2008 - 19:54

I see this when I'm consoled into the ap and ap is booting up.

I think these are "old orphaned" commands from the "autonomous ap" configuration.

Scott Fella Thu, 07/03/2008 - 03:26

You can always do a dir on the prompt and look to see what is there. You can delete the config file and any other EXTRA stuff. I will check later, what should be ther or not. If you have another ap, you can check that also.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode