Cisco IOS wont boot.

[Denniz]

Why cant i boot my cisco ap from this file?

I just get that error.

See the screenshot below.

[Pandur]

Shouldn't that be flash:// ?

[Denniz]

9 minutes ago, Pandur said:

Shouldn't that be flash:// ?

I will try that.

[Denniz]

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:/.

[Pandur]

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.

[Sir Asvald]

@Lurick can be of assistance.

 

[Lurick]

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?

[Denniz]

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.

 

[LAwLz]

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.

[Denniz]

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"

[LAwLz]

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.

[Lurick]

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.

[Denniz]

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.

[Lurick]

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

[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.

[Denniz]

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?