04-11-2007 11:02 AM - edited 07-03-2021 01:54 PM
After successfully upgrading an 1131 to LAP we tried to upgrade an 1121 to LAP. The upgrade process went fine but the AP doesn't seem to do so well. It is rebooting over and over again flashing with the red LED now and then. I've tried to reset it with the mode button, but this didn't help. Is the AP broken do you think?
Kind regards,
Rutger
Solved! Go to Solution.
04-12-2007 04:43 AM
Hi Rutger,
When you refer to trying to reset using the MODE button are you using the process listed below?
The AP can be converted back to Autonomous (IOS) using the following method;
Reverting the Access Point Back to Autonomous Mode
Converting a Lightweight Access Point Back to Autonomous Mode
You can convert an access point from lightweight mode back to autonomous mode by loading a Cisco IOS Release that supports autonomous mode (Cisco IOS release 12.3(7)JA or earlier). If the access point is associated to a controller, you can use the controller to load the Cisco IOS release. If the access point is not associated to a controller, you can load the Cisco IOS release using TFTP.
Using a TFTP Server to Return to a Previous Release
Follow these steps to revert from LWAPP mode to autonomous mode by loading a Cisco IOS release using a TFTP server:
--------------------------------------------------------------------------------
Step 1 The static IP address of the PC on which your TFTP server software runs should be between 10.0.0.2 and 10.0.0.30.
Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point) in the TFTP server folder and that the TFTP server is activated.
Step 3 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point, c1130-k9w7-tar.default for an 1130 series access point, and c1240-k9w7-tar.default for a 1240 series access point.
Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.
Step 5 Disconnect power from the access point.
Step 6 Press and hold MODE while you reconnect power to the access point.
Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds) and then release.
Step 8 Wait until the access point reboots, as indicated by all LEDs turning green followed by the Status LED blinking green.
Step 9 After the access point reboots, reconfigure it using the GUI or the CLI.
From this doc;
Hope this helps!
Rob
04-11-2007 11:29 AM
Hi Rutger,
What version of code are you running on the WLC? The support for the 1121 AP was added in 4.0.155.0, so if you are using a 3x image on the WLC you will have problems. You will need to upgrade the WLC image.
The 1310 and 1121 AP support were added to the list of AP's that can be converted from Autonomous to LWAPP. This change is supported on WLC 4404 running 4.0.155.0 (and later)and on AP's that have been upgraded to IOS 12.3(11)JA first.
From this doc;
http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_tech_note09186a00806b55ef.shtml
Hope this helps!
Rob
04-11-2007 11:31 AM
Hi!
We are running 4.0.179.11 on our controller.
I can see the AP requesting and getting an IP from our Linux DHCP, but it doesn't seem to be satisfied with that IP because some seconds after the AP reboots.
Rutger
04-12-2007 03:28 AM
Nobody has a clue? Can one break an AP with a failed upgrade to LAP? The normal reset procedure does not seem to help. Please anybody?
Kind regards,
Rutger
04-12-2007 04:41 AM
Ok, I solved it myself using the reset procedure and a TFTP server with image.
Rutger
04-12-2007 04:43 AM
Hi Rutger,
When you refer to trying to reset using the MODE button are you using the process listed below?
The AP can be converted back to Autonomous (IOS) using the following method;
Reverting the Access Point Back to Autonomous Mode
Converting a Lightweight Access Point Back to Autonomous Mode
You can convert an access point from lightweight mode back to autonomous mode by loading a Cisco IOS Release that supports autonomous mode (Cisco IOS release 12.3(7)JA or earlier). If the access point is associated to a controller, you can use the controller to load the Cisco IOS release. If the access point is not associated to a controller, you can load the Cisco IOS release using TFTP.
Using a TFTP Server to Return to a Previous Release
Follow these steps to revert from LWAPP mode to autonomous mode by loading a Cisco IOS release using a TFTP server:
--------------------------------------------------------------------------------
Step 1 The static IP address of the PC on which your TFTP server software runs should be between 10.0.0.2 and 10.0.0.30.
Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point) in the TFTP server folder and that the TFTP server is activated.
Step 3 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point, c1130-k9w7-tar.default for an 1130 series access point, and c1240-k9w7-tar.default for a 1240 series access point.
Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.
Step 5 Disconnect power from the access point.
Step 6 Press and hold MODE while you reconnect power to the access point.
Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds) and then release.
Step 8 Wait until the access point reboots, as indicated by all LEDs turning green followed by the Status LED blinking green.
Step 9 After the access point reboots, reconfigure it using the GUI or the CLI.
From this doc;
Hope this helps!
Rob
05-19-2007 08:25 AM
I follow all this instructions but I receive this message
ERROT: Failed to open archive tftp://2255.255.255.255/c1200-k9w7-tar.default
Any idea why I get this error message?
05-20-2007 04:18 AM
Hi Francisco,
This conversion back to IOS is possible (it sounds like a TFTP problem here) If the error you sent in your post is copied there is an extra digit in your IP Address "2255";
Reverting the Access Point Back to Autonomous Mode
Have a look at the details in the following threads that all have to do with TFTP. There are some great hints for troubleshooting TFTP problems from some of my favourite NetPros like ScottMac,Stephen from Cisco and Jack Young. The likely culprit may be that you need to uncheck "hide extensions for known file types" on your TFTP server;
Hope this helps! Good Luck!
Rob
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: