02-28-2013 09:55 AM - edited 07-03-2021 11:38 PM
I've been configuring hundreds of 3602i APs via Prime without incident, but I've encountered 2 APs that get to the ap: prompt and doesn't proceed further. If I type boot, then they'll complete the boot process.
How do I configure these 2 APs so they will automatically boot fully?
Thank you,
Susanne
02-28-2013 10:06 AM
You are in ROMON because either the boot image is bad or the boot path is bad. Here is some instruction you can do:
Follow the exact procedure taking care of placing the image in the root directory or any separate folder.. use the image for 1130 not 350 as below example is for 350..
Using the CLI
Follow the steps below to reload the access point image using the CLI. When the access point begins to boot, you interrupt the boot process and use boot loader commands to load an image from a TFTP server to replace the image in the access point.
Note Your access point configuration is not changed when using the CLI to reload the image file.
Step 1 Open the CLI using a Telnet session or a connection to the access point console port.
Step 2 Reboot the access point by removing power and reapplying power.
Step 3 Let the access point boot until it begins to inflate the image. When you see these lines on the CLI, press Esc:
Loading "flash:/c350-k9w7-mx.v122_13_ja.20031010/c350-k9w7-mx.v122_13_ja.20031010"
...###########################################################################
################################################################################
################################################################################
####################
Step 4 When the ap: command prompt appears, enter the set command to assign an IP address, subnet mask, and default gateway to the access point.
Note You must use upper-case characters when you enter the IP-ADDR, NETMASK, and DEFAULT_ROUTER options with the set command.
Your entries might look like this example:
ap: set IP_ADDR 192.168.133.160
ap: set NETMASK 255.255.255.0
ap: set DEFAULT_ROUTER 192.168.133.1
Step 5 Enter the tftp_init command to prepare the access point for TFTP.
ap: tftp_init
Step 6 Enter the tar command to load and inflate the new image from your TFTP server. The command must include this information:
•the -xtract option, which inflates the image when it is loaded
•the IP address of your TFTP server
•the directory on the TFTP server that contains the image
•the name of the image
•the destination for the image (the access point Flash)
Your entry might look like this example:
ap: tar -xtract tftp://192.168.130.222/images/c350-k9w7-tar.122-13.JA1 flash:
Step 7 When the display becomes full the CLI pauses and displays --MORE--. Press the spacebar to continue.
extracting info (229 bytes)
c350-k9w7-mx.122-13.JA1/ (directory) 0 (bytes)
c350-k9w7-mx.122-13.JA1/html/ (directory) 0 (bytes)
c350-k9w7-mx.122-13.JA1/html/level1/ (directory) 0 (bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/appsui.js (558 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/back.htm (205 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/cookies.js (5027 bytes).
extracting c350-k9w7-mx.122-13.JA1/html/level1/forms.js (15704 bytes)...
extracting c350-k9w7-mx.122-13.JA1/html/level1/sitewide.js (14621 bytes)...
extracting c350-k9w7-mx.122-13.JA1/html/level1/config.js (2554 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/stylesheet.css (3215 bytes)
c350-k9w7-mx.122-13.JA1/html/level1/images/ (directory) 0 (bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/ap_title_appname.gif (1422 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_1st.gif (1171 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_cbottom.gif (318 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_current.gif (348 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_last.gif (386 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_last_filler.gif (327
bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_last_flat.gif (318
bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_nth.gif (1177 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_leftnav_dkgreen.gif (869 bytes)
-- MORE --
If you do not press the spacebar to continue, the process eventually times out and the access point stops inflating the image.
Step 8 Enter the set BOOT command to designate the new image as the image that the access point uses when it reboots. The access point creates a directory for the image that has the same name as the image, and you must include the directory in the command. Your entry might look like this example:
ap: set BOOT flash:/c350-k9w7-mx.122-13.JA1/c350-k9w7-mx.122-13.JA1
Step 9 Enter the set command to check your bootloader entries.
ap: set
BOOT=flash:/c350-k9w7-mx.122-13.JA1/c350-k9w7-mx.122-13.JA1
DEFAULT_ROUTER=192.168.133.1
IP_ADDR=192.168.133.160
NETMASK=255.255.255.0
Step 10 Enter the boot command to reboot the access point. When the access point reboots, it loads the new image.
ap: boot
To remove a set value:
ap: unset
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
02-28-2013 10:49 AM
The error was:
"The system is not configured to boot automatically. The following command will finish loading the operating system software:
boot"
Found the solution here: http://www.tek-tips.com/viewthread.cfm?qid=958691
set MANUAL_BOOT no
That solved the issue. I did not set the MANUAL_BOOT to yes, so not sure how that happened.
Thanks so much for your input, Scott!
Susanne
01-03-2014 05:35 PM
Don't forget the ether_init command!!!!
was driving me crazy...
thanks.
02-28-2014 10:56 AM
I also ran into this problem on what I believe to be new 3602E APs. Simply setting the
"set MANUAL_BOOT no" resolved it on both access points...The first of the two access points I downloaded new code, the AP successfully joined it's WLC controller, and after the reload it comes back with the "The system is not configured to boot automatically" message. After performing the "set MANUAL_BOOT no". I rebooted and it worked fine every time.
The second AP had the same syptoms, I DID NOT download new code, I just performed the "set MANUAL_BOOT no" command and the problem cleared. This leads me to believe it is not a code problem but maybe a Quality Check being performed that is not getting turned off...Does Cisco have an issue with an auto test that is leaving the AP's in this mode when they leave the factory?
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: