topic Re: AP2800 - Mobility Express conversion no space on device in Wireless

AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 20:23:43 GMT

Hi all,

I've picked up a few AP2802 access points. My plan is to convert one to ME software and have the rest as regular CAPWAP access points subordinate to it.

I can't get the conversion process to work though. I've done a MODE button 20s factory reset. Software running below:

AP Running Image : 8.5.135.0
Primary Boot Image : 8.5.135.0
Backup Boot Image : 0.0.0.0

If I do the ap-type mobility-express tftp://172.16.10.10/AIR-AP2800-K9-ME-8-8-130-0.tar I get:

AP6C8B.1234.1234#ap-type mobility-express tftp://172.16.10.10/AIR-AP2800-K9-ME-8-8-130-0.tar
Starting the ME image download...
It may take a few minutes to finish download.
If it is longer, please abort command, check network connection and try again
######################################################################## 100.0%
Image transfer complete.
Image downloaded, writing to flash...
do CHECK_ME, part2 is active part
Image signing verify success.
upgrade.sh: part to upgrade is part1
tar: write error: No space left on device
upgrade.sh: Command "tar -xf /tmp/part.tar -C /bootpart/part1" failed.
upgrade.sh: df /bootpart/part1
upgrade.sh: du -h /bootpart/part1
upgrade.sh: Writing image to disk...
sh: 1K-blocks: unknown operand
upgrade.sh: activate part1, set BOOT to part1
upgrade.sh: AP primary version: 8.8.130.0
Archive done.

I've tried 8.10.196 also. Same thing, except 8.10 gives some messages about a seemingly successful Master being upgraded. The MD5 checksum of both .tars matches that on Cisco downloads. When I reload the AP, the software version shown is back to 8.5.135 despite it suggesting at least some of the upgrade worked.

I've Googled.. other people seem to have run into this but don't point to a solution. This video (https://www.youtube.com/watch?v=7E5qmmb_drQ) shows the chap running into the same issue and he shows the workaround of upgrading the CAPWAP software first (he's at 8.2.111 and upgrades to 8.5.x suggesting there's an issue with CAPWAP software <8.3.xx. So he upgrades.

If I follow his instructions, (using ap3g3-k9w8-tar.153-3.JPT.tar) my AP tells me that it's expecting an ME image. He says to use the same (ap-type mobility-express) command.

So I'm stuck.... how do I get this flippin thing into ME mode?

cheers!

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Thu, 10 Oct 2024 20:48:28 GMT

@Ecky

To work with 8.8.130.0 you need the capwap version of 15.3(3)JI6, as per the Compatibility matrix. What happend when you run the command "ap-type mobility-express ap3g3-k9w8-tar.153-3.JPT.tar" ?

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 20:51:00 GMT

@Flavio Miranda As I said above, it tells me the "ap-type mobility-express" command is expecting an ME image.... which ap3g3... is not.

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 20:53:01 GMT

AP6C8B.D3FE.BE36#ap-type mobility-express tftp://172.16.10.10/ap3g3-k9w8-tar.153-3.JPT.tar
Starting the ME image download...
It may take a few minutes to finish download.
If it is longer, please abort command, check network connection and try again
######################################################################## 100.0%
Image transfer complete.
Image downloaded, writing to flash...
do CHECK_ME, part2 is active part
tar: me_image: not found in archive
upgrade.sh: Image provided does not support Mobility Express functionality, Please get the proper image and try again
Error: Image update failed.

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Thu, 10 Oct 2024 21:06:43 GMT

If you use the traditional command for capwap ?

archive download-sw /no-reload tftp://172.16.10.10/ap3g3-k9w8-tar.153-3.JPT.tar

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 21:22:16 GMT

Aahaha!!

I was playing around with "archive download-sw" earlier and it wouldnt work since it wouldn't take the TFTP bit...

I didn't do it with the /no-reload option. Okay.... that worked...

I've reloaded back into something very different!

AP Running Image : 17.15.1.6
Primary Boot Image : 17.15.1.6
Backup Boot Image : 8.5.135.0

Big thanks for getting me this far... but what state am I in now? It's not quite ME... the ap-type mobility-express doesn't work since it's already in ME .. so I try:

AP6C8B.D3FE.BE36#archive download-sw /reload tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar
Download script called with args:[-l tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar -m 0]
Starting download AP image tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar ...
It may take a few minutes. If longer, please abort command, check network and try again.
######################################################################## 100.0%
Upgrading ...
status 'upgrade.sh: Script called with args:[NO_UPGRADE]'
do NO_UPGRADE, part1 is active part
status 'upgrade.sh: Script called with args:[-c PREDOWNLOAD]'
do PREDOWNLOAD, part1 is active part
status 'upgrade.sh: Creating before-upgrade.log'
status 'upgrade.sh: Start doing upgrade arg1=PREDOWNLOAD arg2=,from_cli arg3= ...'
status 'upgrade.sh: Using image /tmp/cli_part.tar on barbados ...'
extracting /tmp/cli_part.tar was successful
hash file signature does not exist, ap version 8.10.196.0
Version 8.10.196.0 is lower than minimum version
hash signature verification succeeded
status 'upgrade.sh: signature verification of iox.tar.gz failed error code 6 ret code 10'
status 'upgrade.sh: Cleanup for do_upgrade...'
status 'upgrade.sh: /tmp/upgrade_in_progress cleaned'
status 'upgrade.sh: Cleanup tmp files ...'
Failed to update flash
Image download completed.
Image transfer failed

but as you can see failure...

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Thu, 10 Oct 2024 21:27:20 GMT

I believe you need to use archive download-sw to upgrade the capwap image to ap3g3-k9w8-tar.153-3.JPT.tar, which is the minimum required to work with AIR-AP2800-K9-ME-8-10-196-0.tar.

After you upgrade the capwap image, then you can try to install the ME image with

ap-type mobility-express tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 21:41:29 GMT

That doesn't work. The 'mobility-express' option isn't there:

AP6C8B.D3FE.BE36#ap-type ?
capwap Switch to CAPWAP AP type
workgroup-bridge Switch to Workgroup Bridge(WGB) AP type

Presumably since it's now ME (and some of the boot messages allude to presence of 'Cisco ME Service')

AP6C8B.D3FE.BE36#ap-type mobility-express tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar

ap-type mobility-express tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar
        ^
% Invalid input detected at '^' marker.

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Thu, 10 Oct 2024 22:01:15 GMT

To run the 8-10-196-0 ME image, you need the AP to have de capwap image 15.3(3)JK11 . Which is

ap3g3-k9w8-tar.153-3.JK1.tar

if necessay, run the command "ap-type capwap" to bring it back to capwap mode.

I would try to first upgrade the capwap image to this version with the command

ap-type mobility-express tftp://172.16.10.10/ap3g3-k9w8-tar.153-3.JK1.tar

of course you need to download it.

After that, try to install the ME image with

archive download-sw /reload tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 22:18:29 GMT

thanks right OK.... remember ap-type mobility-express isn't available to me so I:

AP6C8B.D3FE.BE36#archive download-sw /no-reload tftp://172.16.10.10/ap3g3-k9w8-tar.153-3.JK11.tar
Download script called with args:[-l tftp://172.16.10.10/ap3g3-k9w8-tar.153-3.JK11.tar -m 0]
Starting download AP image tftp://172.16.10.10/ap3g3-k9w8-tar.153-3.JK11.tar ...
It may take a few minutes. If longer, please abort command, check network and try again.
######################################################################## 100.0%
Upgrading ...
status 'upgrade.sh: Script called with args:[NO_UPGRADE]'
do NO_UPGRADE, part1 is active part
status 'upgrade.sh: Script called with args:[-c PREDOWNLOAD]'
do PREDOWNLOAD, part1 is active part
status 'upgrade.sh: Creating before-upgrade.log'
status 'upgrade.sh: Start doing upgrade arg1=PREDOWNLOAD arg2=,from_cli arg3= ...'
status 'upgrade.sh: Using image /tmp/cli_part.tar on barbados ...'
extracting /tmp/cli_part.tar was successful
hash file signature does not exist, ap version 8.10.196.0
Version 8.10.196.0 is lower than minimum version
hash signature verification succeeded
status 'Image signing verify success.'
status 'upgrade.sh: ***** part to upgrade is part2 *******'
status 'upgrade.sh: AP version1: part2 17.15.1.6, img 8.10.196.0'
root: Adjusting boot partition "part1" size
root: Unable to stash boot partition "part1". Resize aborted..
root: Adjusting boot partition "part2" size
[08/11/2024 06:44:07.2100] UBI error: ubi_create_volume: not enough PEBs, only 624 available
[08/11/2024 06:44:07.3200] UBI error: ubi_create_volume: cannot create volume 1, error -28
Set volume size to 79233024
Volume ID 1, size 624 LEBs (79233024 bytes, 75.6 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "part2", alignment 1
mknod: /dev/ubivol/part2: File exists
mknod: /dev/ubivol/part2: File exists
mknod: /dev/ubivol/part2: File exists
mknod: /dev/ubidev/part2: File exists
mknod: /dev/ubidev/part2: File exists
mknod: /dev/ubidev/part2: File exists
mv: setfilecon:part2/btldr.img,system_u:object_r:tmpfs_t:s0: Operation not supported
mv: setfilecon:part2/file_hashes,system_u:object_r:tmpfs_t:s0: Operation not supported
mv: setfilecon:part2/final_hash,system_u:object_r:tmpfs_t:s0: Operation not supported
mv: setfilecon:part2/info,system_u:object_r:tmpfs_t:s0: Operation not supported
mv: setfilecon:part2/info.ver,system_u:object_r:tmpfs_t:s0: Operation not supported
mv: setfilecon:part2/part.bin,system_u:object_r:tmpfs_t:s0: Operation not supported
/tmp
status 'upgrade.sh: Extracting and verifying image in part2...'
status 'upgrade.sh: BOARD generic case execute'
status 'upgrade.sh: mount ubifs /dev/ubivol/part2 as /bootpart, status=0'
status 'upgrade.sh: Untar /tmp/cli_part.tar to /bootpart/part2...'
status 'upgrade.sh: Sync image to disk...'
status 'upgrade.sh: status 'Successfully verified image in part2.''
status 'upgrade.sh: AP version2: part2 8.10.196.0, img 8.10.196.0'
status 'upgrade.sh: AP backup version: 8.10.196.0'
status 'upgrade.sh: Finished upgrade task.'
status 'upgrade.sh: Cleanup for do_upgrade...'
status 'upgrade.sh: /tmp/upgrade_in_progress cleaned'
status 'upgrade.sh: Cleanup tmp files ...'
status 'upgrade.sh: Script called with args:[ACTIVATE]'
do ACTIVATE, part1 is active part
status 'upgrade.sh: mount ubifs /dev/ubivol/part2 as /bootpart, status=0'
status 'upgrade.sh: Verifying image signature in part2'
status 'upgrade.sh: status 'Successfully verified image in part2.''
status 'upgrade.sh: activate part2, set BOOT to part2'
status 'upgrade.sh: AP primary version after reload: 8.10.196.0'
status 'upgrade.sh: AP backup version after reload: 17.15.1.6'
Successfully setup AP image.
Image download completed.
Archive done.

and that yields a 'sh ver' of:

AP Running Image : 17.15.1.6
Primary Boot Image : 17.15.1.6
Backup Boot Image : 8.10.196.0

so let's reload.....

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 22:40:04 GMT

sh ver now gives:

AP Running Image : 8.10.196.0
Primary Boot Image : 8.10.196.0
Backup Boot Image : 17.15.1.6

so I try:

AP6C8B.D3FE.BE36#ap-type mobility-express tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar
Starting download ME-AP image tftp://172.16.10.10/AIR-AP2800-K9-ME-8-10-196-0.tar ...
It may take a few minutes. If longer, please abort command, check network and try again.
######################################################################## 100.0%
Image download completed.
Upgrading ...
upgrade.sh: Script called with args:[NO_UPGRADE]
do NO_UPGRADE, part2 is active part
upgrade.sh: Script called with args:[-c CHECK_ME]
do CHECK_ME, part2 is active part
upgrade.sh: Creating before-upgrade.log
upgrade.sh: Start doing upgrade arg1=CHECK_ME arg2=,from_cli arg3= ...
upgrade.sh: Using image /tmp/cli_part.tar on barbados ...
Image signing verify success.
upgrade.sh: part to upgrade is part1
upgrade.sh: AP version1: part1 17.15.1.6, img 8.10.196.0
sh: SC4_1dbm.txt: unknown operand
root: Adjusting boot partition "part1" size
Volume ID 0, size 632 LEBs (80248832 bytes, 76.5 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "part1", alignment 1
mknod: /dev/ubivol/part1: File exists
mknod: /dev/ubivol/part1: File exists
mknod: /dev/ubivol/part1: File exists
mknod: /dev/ubidev/part1: File exists
mknod: /dev/ubidev/part1: File exists
mknod: /dev/ubidev/part1: File exists
/tmp
sh: SC4_1dbm.txt: unknown operand
upgrade.sh: Extracting and verifying image in part1...
upgrade.sh: BOARD generic case execute
upgrade.sh: mount ubifs /dev/ubivol/part1 as /bootpart, status=0
upgrade.sh: Untar /tmp/cli_part.tar to /bootpart/part1...
upgrade.sh: Sync image to disk...
upgrade.sh: status 'Successfully verified image in part1.'
upgrade.sh: activate part1, set BOOT to part1
upgrade.sh: AP version2: part1 8.10.196.0, img 8.10.196.0
upgrade.sh: AP primary version: 8.10.196.0
upgrade.sh: Finished upgrade task.
upgrade.sh: Cleanup for do_upgrade...
upgrade.sh: /tmp/upgrade_in_progress cleaned
upgrade.sh: Cleanup tmp files ...
Successfully setup ME-AP image.
Archive done.

and that kicks off a reboot which now give me:

AP Running Image : 8.10.196.0
Primary Boot Image : 8.10.196.0
Backup Boot Image : 8.10.196.0

..and I think I'm good. Huge thanks for getting me to this point...

I can't see the "CiscoAirProvision" SSID though.... show interfaces radio gives line proto down for dot0 and dot1..

Do i need to do something to kick off the initial state?

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Thu, 10 Oct 2024 23:02:56 GMT

Can you access the web interface?

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Thu, 10 Oct 2024 23:08:10 GMT

no - no SSID. I understand the way to do this is via the above named SSID but it's not there.

Apols for being dopey - I've worked with Cisco wireless stuff for years from early Aironet VxWorks 350s, WLSE, WLC but I've been out of the game for 6+ years so not familiar with this stuff!

If this helps:

AP6C8B.D3FE.BE36#show dot11 wlan
Radio Vap SSID State Auth Assoc Switching
0 0 DOWN Central Central Central
0 1 DOWN Central Central Central
0 2 DOWN Central Central Central
0 3 DOWN Central Central Central
0 4 DOWN Central Central Central
0 5 DOWN Central Central Central
0 6 DOWN Central Central Central
0 7 DOWN Central Central Central
0 8 DOWN Central Central Central
0 9 DOWN Central Central Central
0 10 DOWN Central Central Central
0 11 DOWN Central Central Central
0 12 DOWN Central Central Central
0 13 DOWN Central Central Central
0 14 DOWN Central Central Central
0 15 DOWN Central Central Central
1 0 DOWN Central Central Central
1 1 DOWN Central Central Central
1 2 DOWN Central Central Central
1 3 DOWN Central Central Central
1 4 DOWN Central Central Central
1 5 DOWN Central Central Central
1 6 DOWN Central Central Central
1 7 DOWN Central Central Central
1 8 DOWN Central Central Central
1 9 DOWN Central Central Central
1 10 DOWN Central Central Central
1 11 DOWN Central Central Central
1 12 DOWN Central Central Central
1 13 DOWN Central Central Central
1 14 DOWN Central Central Central
1 15 DOWN Central Central Central

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Thu, 10 Oct 2024 23:21:34 GMT

Yes, it should adivertise the SSID CiscoAirProvision .

On possible problem could be the power. Where it is getting power from? PoE or power injector?

Try to install teh AP bundle also.

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Fri, 11 Oct 2024 08:22:36 GMT

Right - so I got this going.

The Access Point was coming up seemingly without the controller part. It just booted up doing it's CAPWAP discovery with nothing suggesting any controller goodness (save for that service I mentioned earlier).

I thought it might be the AP image bundle also but that wouldn't install with either the ap-type or archive methods. I don't know what made me do it, but I installed the conversion image again. This time it came up with the controller wizard that asked a bunch of questions, including SSID, then I was off to the races. All working now.

I never saw CiscoAirProvision and it didn't go like the doc's suggested it should but hey... it seems to be working now. Power is coming from a 3750-X.

Thanks again Flavio helping me navigate those versions! Cheers!

Re: AP2800 - Mobility Express conversion no space on device

Flavio Miranda — Fri, 11 Oct 2024 11:24:17 GMT

@Ecky

My pleasure. Very good job and thanks for rating, this is the kind of post that can help lots of people here. Every day there are people here struggling with the very same problem.

Re: AP2800 - Mobility Express conversion no space on device

Ecky — Fri, 11 Oct 2024 11:31:47 GMT

Absolutely yes, I was deliberately verbose for that reason.