Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Cisco IOS wont boot.

Denniz
 Share

Go to solution Solved by Lurick,

At this point I would verify the files are located in the sub-directory and are there and maybe try loading the software again.

Why cant i boot my cisco ap from this file?

I just get that error.

See the screenshot below.

Screenshot 2022-05-18 201837.png

Link to comment
Share on other sites

Link to post
Share on other sites

Shouldn't that be flash:// ?

Link to comment
Share on other sites

Link to post
Share on other sites

9 minutes ago, Pandur said:

Shouldn't that be flash:// ?

I will try that.

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, Denniz said:

I will try that.

 

12 minutes ago, Pandur said:

Shouldn't that be flash:// ?

Nope, that didn't work. I think it should be flash:/.

Link to comment
Share on other sites

Link to post
Share on other sites

Ok. Just noticed that it said directory of flash:// in your screenshot.

 

Some other ideas:

- Check file permissions in the folders

- Change folder or file name so they are not duplicates and/or shorter

- Move the rom file to the root instead of in a folder

 

Any embedded OS can be rather stubborn. Sadly I don't work with Cisco so I have no in depth knowledge. 🙂

Link to comment
Share on other sites

Link to post
Share on other sites

@Lurick can be of assistance. 🙂

 

CPU: AMD Ryzen 5 5600X | CPU Cooler: Stock AMD Cooler | Motherboard: Asus ROG STRIX B550-F GAMING (WI-FI) | RAM: Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 CL16 | GPU: Nvidia GTX 1060 6GB Zotac Mini | Case: K280 Case | PSU: Cooler Master B600 Power supply | SSD: 1TB  | HDDs: 1x 250GB & 1x 1TB WD Blue | Monitors: 24" Acer S240HLBID + 24" Samsung  | OS: Win 10 Pro

 

Audio: Behringer Q802USB Xenyx 8 Input Mixer |  U-PHORIA UMC204HD | Behringer XM8500 Dynamic Cardioid Vocal Microphone | Sound Blaster Audigy Fx PCI-E card

 

Home Lab:  Lenovo ThinkCenter M82 ESXi 6.7 | Lenovo M93 Tiny Exchange 2019 | TP-LINK TL-SG1024D 24-Port Gigabit | Cisco ASA 5506 firewall  | Cisco Catalyst 3750 Gigabit Switch | Cisco 2960C-LL | HP MicroServer G8 NAS | Dell PowerEdge R210 II SCCM Server

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

What's the model of the AP?

Has it booted before? Was it in lightweight or autonomous mode?

Can you boot from the k9w8 images?

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

14 minutes ago, Lurick said:

What's the model of the AP?

Has it booted before? Was it in lightweight or autonomous mode?

Can you boot from the k9w8 images?

It is an cisco aironet air-cap3502i-e-k9 (i know, its old). It can boot from the k9w8 image but when i try to boot from the k9w7 image it fails.

 

Link to comment
Share on other sites

Link to post
Share on other sites

My guess is that you mistyped the boot file and that's why it doesn't work.

 

You wrote:

set BOOT flash:/ap3g1-k9w7-mx.153-3.JF15/ap3g1-k9w7-mx.153-3.JF15

 

What you should have written is:

set BOOT flash:/ap3g1-k9w7-mx.153-3.JF15

 

 

Edit:

Also, correct me if I am wrong but shouldn't the boot image for that AP be a .tar file?

Or did you already extract the image?

 

 

 

Never mind, apparently you extract the tar file and then point to a file within the extracted directory when upgrading an autonomous AP through CLI. So it seems like you are doing things correctly. Assuming you got the right file and extracted it correctly.

Link to comment
Share on other sites

Link to post
Share on other sites

5 minutes ago, LAwLz said:

My guess is that you mistyped the boot file and that's why it doesn't work.

 

You wrote:

set BOOT flash:/ap3g1-k9w7-mx.153-3.JF15/ap3g1-k9w7-mx.153-3.JF15

 

What you should have written is:

set BOOT flash:/ap3g1-k9w7-mx.153-3.JF15

I have already tried that, it didnt work. I think it should be "set BOOT flash:/ap3g1-k9w7-mx.153-3.JF15/ap3g1-k9w7-mx.153-3.JF15"

Link to comment
Share on other sites

Link to post
Share on other sites

3 minutes ago, Denniz said:

I have already tried that, it didnt work. I think it should be "set BOOT flash:/ap3g1-k9w7-mx.153-3.JF15/ap3g1-k9w7-mx.153-3.JF15"

Yep, you are right. It should be like that.

But since the AP says it can't find the file or directory it seems like the extraction process did not go correctly.

How did you extract it? You should have used:

 

tar -xtract PATH-TO-IMAGE.tar flash

 

That extracts the .tar file to the flash properly.

 

 

Maybe look inside the directory called "ap3g1-k9w7-mx.153-3.JF15" and see if there are any files in there.

Link to comment
Share on other sites

Link to post
Share on other sites

47 minutes ago, Denniz said:

It is an cisco aironet air-cap3502i-e-k9 (i know, its old). It can boot from the k9w8 image but when i try to boot from the k9w7 image it fails.

 

I know k9w8 is the CAPWAP/controller mode and k9w7 is lightweight mode. There is a conversion process but I can't remember if you need to do anything before booting the lightweight image or not.

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

45 minutes ago, Lurick said:

I know k9w8 is the CAPWAP/controller mode and k9w7 is lightweight mode. There is a conversion process but I can't remember if you need to do anything before booting the lightweight image or not.

I followed this guide: 

https://blog.router-switch.com/2014/12/how-to-convert-a-cisco-3502i-ap-to-operate-in-an-autonomous-mode/

I did everything as they did, i just have another version.

Link to comment
Share on other sites

Link to post
Share on other sites

58 minutes ago, Denniz said:

I followed this guide: 

https://blog.router-switch.com/2014/12/how-to-convert-a-cisco-3502i-ap-to-operate-in-an-autonomous-mode/

I did everything as they did, i just have another version.

Well if you want autonomous mode you want to stay on one of the k9w8 images but you're trying to boot with a k9w7 image which is lightweight mode and requires a controller. (or at least I think I have the w8 and w7 modes right)

 

Edit:

nvm, I had them backwards

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

At this point I would verify the files are located in the sub-directory and are there and maybe try loading the software again.

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, i got it to work after formating flash and uploading it again, but now when i try to configure anything in the webgui it just says 404, not found. I googled around and found out that some versions can be buggy, i have the ap3g1-k9w7-tar.153-3.jf15.tar. Has anyone got problems with that? Or anyone that knows how to solve the problem?

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×