Restoring LAP1522AG Access Points to Factory Defaults without WLC.

Unanswered Question
Jul 23rd, 2009

I have inherited 2 LAP1522s, and I am having difficulty trying to join them to my WLC2100.

My guess is that they were used previously by someone in my company, primarily because I can not manually clear the private-config or issue any 'lwapp ap ip' commands. All result in the 'ERROR!!! Command is disabled' response.

If this is the case, and I have no access to the controller that was used previously, how can I return these APs to a point where I can join my WLC2100?

LAP1522AG's are running version 4.1.192.17, and the WLC2100 is running 4.2.130.0.

This is as far as I can get when trying to join them to my network:

5.255.0, hostname AP001f.2777.4800

Translating "CISCO-LWAPP-CONTROLLER.sit.com"...domain server (172.30.49.44) [OK]

examining image...

*Mar 1 00:01:12.063: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Jul 23 12:56:32.463: %LWAPP-5-CHANGED: LWAPP changed state to IMAGE

%Error opening (OK)archive download: takes 20 seconds

*Jul 23 12:56:52.463: LWAPP_CLIENT_ERROR: not receive read response(0)

*Jul 23 12:56:52.467: lwapp_image_proc: unable to open tar file

Any help appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Leo Laohoo Fri, 07/24/2009 - 01:37

Hi Steve,

I'm not familiar with this model of AP but see if you could try this method:

1. Check the file directory of your AP for 2 IOS: One LWAP image and the other the "RCV" image.

2. If you have them, delete the LWAP image (delete /f /r flash:lwapp image directory).

3. Boot the AP using the RCV image. You may now use the "clear lwapp" commands.

Hope this helps.

stevederie Fri, 07/24/2009 - 05:08

I have seen references to the deletion of that file as a remedy. However, the 1522 does not use similar file names.

For fear of doing the wrong thing and killing the AP, I have not wanted to delete anything without knowing for sure.

The files I have on my AP are:

ap#dir

Directory of flash:/

2 -rwx 4515840 Jan 01 1970 00:01:47 +00:00 c1520-img-tar

3 -rwx 393216 Jan 01 1970 00:01:13 +00:00 c1520-boot-m.124-3g.JMC

4 -rwx 63 Mar 01 2002 00:00:08 +00:00 mesh_cfg.txt

6 drwx 512 Jan 01 1970 00:03:42 +00:00 c1520-k9w9-mx.124-3g.JMC

16 -rwx 790 Jul 23 2009 12:14:03 +00:00 env_vars

31868928 bytes total (22455296 bytes free)

ap#

Will deleting one of these accomplish the same thing?

Leo Laohoo Fri, 07/24/2009 - 18:27

Hi Steve,

Thanks for the dir output. I am suspecting the LWAP image is " c1520-k9w9-mx.124-3g.JMC" but I am uncertain of the function of the "c1520-boot-m.124-3g.JMC". I am suspecting that the 1520 does not support Autonomous IOS.

I hope someone will correct me on this.

stevederie Mon, 07/27/2009 - 10:40

Thanks for the response Leolaohoo, I appreciate the assist.

Maybe my failure to join is for some other reason, although I highly suspect it is for reason I had mentioned.

When the AP reports the following:

examining image...

*Mar 1 00:01:12.063: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Jul 23 12:56:32.463: %LWAPP-5-CHANGED: LWAPP changed state to IMAGE

%Error opening (OK)archive download: takes 20 seconds

*Jul 23 12:56:52.463: LWAPP_CLIENT_ERROR: not receive read response(0)

*Jul 23 12:56:52.467: lwapp_image_proc: unable to open tar file

My assumption is that it does not have the ability to open the tar file because of the previous relationship with an unknown WLC.

This should be easier than this. We own 1 WLC2100 and 2 LAP1522's, and we do not have any service contract or rep to call....so I am not sure of the best way to get these operational.

Leo Laohoo Mon, 07/27/2009 - 14:32

I think I know what the problem is ...

You said that the WLC2100 is "running 4.2.130.0" and you have Mesh AP.

I've checked the download page and this version is not available for Mesh AP but standard LWAP. I believe you need to get the Mesh AP firmware. The only 4.2.X is the 4.2.176.51M MESH.

This is why the AP won't join and won't download the firmware because the controller is running the wrong firmware.

Hope this helps.

stevederie Thu, 07/30/2009 - 03:14

Hi Leo,

Sorry for the delay.

Thanks for picking up on that detail regarding the version required for mesh APs. This is definitely not going to work without the correct version.

Moving forward, we need a SmartNet contract to be able to download that version of firmware.

That process may take a few days, but I will let you know how this works out.

Thanks,

Steve

Leo Laohoo Thu, 07/30/2009 - 19:13

Hi Steve,

Thanks for the update. You can contact your authorized Cisco reseller for the service contract. Alternatively, your reseller should be able to provide you with the file too.

Actions

This Discussion

 

 

Trending Topics - Security & Network