Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

2602i fail to boot after joining controller

I have two 2602i that are no longer booting after they joined the controller and pulled the updated image.

from the console this is what I see during the boot process.

IOS Bootloader - Starting system.

flash is writable

FLASH CHIP:  Numonyx Mirrorbit (0089)

Xmodem file system is available.

flashfs[0]: 43 files, 8 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 31997952

flashfs[0]: Bytes used: 11590656

flashfs[0]: Bytes available: 20407296

flashfs[0]: flashfs fsck took 19 seconds.

Reading cookie from SEEPROM

Base Ethernet MAC address: 4c:00:82:b9:84:f6

Ethernet speed is 1000 Mb - FULL Duplex

Loading "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-mx.152-4.JA1"...###########################

File "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-mx.152-4.JA1" uncompressed and installed, entry point: 0x2003000

executing...

Secondary Bootloader - Starting system.

Xmodem file system is available.

flashfs[0]: 43 files, 8 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 31997952

flashfs[0]: Bytes used: 11590656

flashfs[0]: Bytes available: 20407296

flashfs[0]: flashfs fsck took 12 seconds.

Base Ethernet MAC address: 4c:00:82:b9:84:f6

Boot CMD: 'boot  flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-xx.152-4.JA1'

Loading "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-xx.152-4.JA1"...################


At that point right there it just hangs. I let it sit overnight with no change.

Any ideas?

My controller is running software version 7.5.102.0

Everyone's tags (3)
2 ACCEPTED SOLUTIONS

Accepted Solutions
VIP Purple

Re: 2602i fail to boot after joining controller

Hi Gary ,

Your AP have autonomous image ap3g2-k9w7-tar.default.

You must convert this image to Lightweight image(k9w8) then try to join with WLC.

  • k9w7 – autonomous IOS
  • k9w8 – full lightweight IOS (this is what is bundled in the WLC .aes image, and is factory installed on “mesh” APs)
  • rcvk9w8 – lightweight recovery image – this is factory installed on lightweight APs, unless a “mesh” image is specified; it lacks radio firmware

How to convert:

http://mrncciew.com/2012/10/20/lightweight-to-autonomous-conversion/

https://supportforums.cisco.com/docs/DOC-14960

Regards

Hall of Fame Super Silver

Re: 2602i fail to boot after joining controller

Just to add... make sure you download one of these images to upload to your 2602i.  I usually still use the 12.4 rcv image, but you can try either one:

ap3g2-rcvk9w8-tar.124-25e.JA1.tar

http://software.cisco.com/download/release.html?mdfid=284362257&flowid=34153&softwareid=280775090&release=15.2.4-JB3&relind=AVAILABLE&rellifecycle=ED&reltype=latest

ap3g2-rcvk9w8-tar.152-4.JB3.tar

http://software.cisco.com/download/release.html?mdfid=284362257&flowid=34153&softwareid=280775090&release=15.2.4-JB3&relind=AVAILABLE&rellifecycle=ED&reltype=latest

Your AP did have the correct image on it initially, but either the WLC image is corrupt or the transfer corrupted the AP image.  I usually would go in to ROMMON mode and delete the images and various other files, like error log's, to clean up the AP.

Example:

ap:delete flash:private-config

ap:delete flash:private-multiple-fs

The set command will also let you see what image the AP will boot from.

When you upload the new image, you should capture the output from the console as this helps figure out whats wrong.

Thanks,


Scott

Help out other by using the rating system and marking answered questions as "Answered"

-Scott
*** Please rate helpful posts ***
9 REPLIES
VIP Purple

2602i fail to boot after joining controller

Hi gary,

Paste the output of the command:

WLC: sh sysinfo

AP: sh inventory

also paste the boot process from AP.

Reagrds

New Member

2602i fail to boot after joining controller

I pasted the boot process for the AP in my original post.

The AP won't complete boot so there is no way for me to issue the "show inventory" command to it.

Here is the output of "show sysinfo" from the WLC:

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 7.5.102.0

Bootloader Version............................... 1.0.16

Field Recovery Image Version..................... 7.0.112.21

Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2

Build Type....................................... DATA + WPS

System Name...................................... mng-dc-wlc1

System Location..................................

System Contact...................................

System ObjectID.................................. 1.3.6.1.4.1.9.1.1069

Redundancy Mode.................................. Disabled

IP Address....................................... 10.147.76.4

Last Reset....................................... Software reset

System Up Time................................... 0 days 22 hrs 14 mins 59 secs

System Timezone Location......................... (GMT -7:00) Mountain Time (US and Canada)

System Stats Realtime Interval................... 5

System Stats Normal Interval..................... 180

Configured Country............................... US  - United States

Operating Environment............................ Commercial (0 to 40 C)

--More-- or (q)uit

Internal Temp Alarm Limits....................... 0 to 65 C

Internal Temperature............................. +37 C

External Temperature............................. +26 C

Fan Status....................................... OK

State of 802.11b Network......................... Disabled

State of 802.11a Network......................... Disabled

Number of WLANs.................................. 0

Number of Active Clients......................... 0

Burned-in MAC Address............................ F8:72:EA:EE:EF:60

Power Supply 1................................... Present, OK

Power Supply 2................................... Absent

Maximum number of APs supported.................. 50

VIP Purple

Re: 2602i fail to boot after joining controller

Hi Garry

Please also update FUS on WLC.

Try to Reset the Device to Default Settings and then try again.

If you need to start over during the initial setup process, you can reset the access point to factory default settings.

##Resetting to Default Settings Using the MODE Button

#Follow these steps to reset the access point to factory default settings using the access point MODE button:

#Step 1 Disconnect power (the power jack for external power or the Ethernet cable for in-line power) from the access point.

#Step 2 Press and hold the MODE button while you reconnect power to the access point.

#Step 3 Hold the MODE button until the Status LED turns amber (approximately 1 to 2 seconds), and release the button. All access point settings return to factory defaults.

http://www.cisco.com/en/US/docs/wireless/access_point/12.4.25d.JA/Configuration/guide/scg12.4.25d.JA-chap4-first.html#wp1034993

or

https://supportforums.cisco.com/thread/2045805

Regards.

Sandeep

New Member

2602i fail to boot after joining controller

Hi Sandeep,

I updated FUS on the WLC and attempted the reset as described and this is the output I am getting from the AP now.

IOS Bootloader - Starting system.

flash is writable

FLASH CHIP:  Numonyx Mirrorbit (0089)

Xmodem file system is available.

flashfs[0]: 43 files, 8 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 31997952

flashfs[0]: Bytes used: 11590656

flashfs[0]: Bytes available: 20407296

flashfs[0]: flashfs fsck took 21 seconds.

Reading cookie from SEEPROM

Base Ethernet MAC address: 4c:00:82:b9:84:f6

Ethernet speed is 1000 Mb - FULL Duplex

button is pressed, wait for button to be released...

button pressed for 28 seconds

process_config_recovery: set IP address and config to default 10.0.0.1

process_config_recovery: image recovery

image_recovery: Download default IOS tar image tftp://255.255.255.255/ap3g2-k9w7-tar.default

examining image...

DPAA Set for Independent Mode

DPAA_INIT = 0x0

%Error opening tftp://255.255.255.255/ap3g2-k9w7-tar.default (connection timed out)ap:

VIP Purple

Re: 2602i fail to boot after joining controller

Hi Gary ,

Your AP have autonomous image ap3g2-k9w7-tar.default.

You must convert this image to Lightweight image(k9w8) then try to join with WLC.

  • k9w7 – autonomous IOS
  • k9w8 – full lightweight IOS (this is what is bundled in the WLC .aes image, and is factory installed on “mesh” APs)
  • rcvk9w8 – lightweight recovery image – this is factory installed on lightweight APs, unless a “mesh” image is specified; it lacks radio firmware

How to convert:

http://mrncciew.com/2012/10/20/lightweight-to-autonomous-conversion/

https://supportforums.cisco.com/docs/DOC-14960

Regards

Hall of Fame Super Silver

Re: 2602i fail to boot after joining controller

Just to add... make sure you download one of these images to upload to your 2602i.  I usually still use the 12.4 rcv image, but you can try either one:

ap3g2-rcvk9w8-tar.124-25e.JA1.tar

http://software.cisco.com/download/release.html?mdfid=284362257&flowid=34153&softwareid=280775090&release=15.2.4-JB3&relind=AVAILABLE&rellifecycle=ED&reltype=latest

ap3g2-rcvk9w8-tar.152-4.JB3.tar

http://software.cisco.com/download/release.html?mdfid=284362257&flowid=34153&softwareid=280775090&release=15.2.4-JB3&relind=AVAILABLE&rellifecycle=ED&reltype=latest

Your AP did have the correct image on it initially, but either the WLC image is corrupt or the transfer corrupted the AP image.  I usually would go in to ROMMON mode and delete the images and various other files, like error log's, to clean up the AP.

Example:

ap:delete flash:private-config

ap:delete flash:private-multiple-fs

The set command will also let you see what image the AP will boot from.

When you upload the new image, you should capture the output from the console as this helps figure out whats wrong.

Thanks,


Scott

Help out other by using the rating system and marking answered questions as "Answered"

-Scott
*** Please rate helpful posts ***
New Member

Re: 2602i fail to boot after joining controller

Thank you both for your assistance. This seems to have done the trick for one of them. I am going through the process for the other one that was giving me issues.

Is there a way I can tell from the part number or serial number as to how these shipped?

The part number showing up on the box is AIR-CAP2602I-A-K9 and all of the serial numbers start with FGL.

Hall of Fame Super Silver

Re: 2602i fail to boot after joining controller

Part number is what you look at.

CAP = capwap
SAP = Standalone Autonomous

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: 2602i fail to boot after joining controller

Excellent!

Thank you both again for your assistance.

1962
Views
0
Helpful
9
Replies
CreatePlease to create content