Cisco IOS upgrade for C9124AXD-B failing

[griffitd904]

Good Morning-

After completing a factory reset, we're now forced to upgrade our iOS back to its previous version. Any assistance would be greatly appreciated.

I have a Windows 10 client connected to a Cataylst 9300 switch behaving like a TFTP server using Solar winds. In addition, I have a 9800 Wireless Controller, which is unable to provision the AP. I can ping the AP from not only the switch but the rest of the devices as well.

Client (TFTP): 192.168.101.10

AP: 192.168.101.202

AP60B9.C088.14C0#archive download-sw /reload tftp://192.168.101.10/ap1g6a-k9w8-tar.17_15_3_28.tar
Download script called with args:[-l tftp://192.168.101.10/ap1g6a-k9w8-tar.17_15_3_28.tar -m 0]
Starting download AP image tftp://192.168.101.10/ap1g6a-k9w8-tar.17_15_3_28.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 axel-qca ...'
status 'upgrade.sh: ERROR: Image type mismatch. Expected: Got:ap1g6a'
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

Cisco AP Software, (ap1g6a), C9124, RELEASE SOFTWARE
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2025 by Cisco Systems, Inc.
Compiled Thu Mar 28 14:16:02 GMT 2024

ROM: Bootstrap program is U-Boot boot loader
BOOTLDR: U-Boot boot loader Version U-Boot REL 2016.01 (btldr release 42) (Nov 1
7 2023 - 14:11:13 -0800)
TZ: Trustzone Version CRM-TZ.BF.4.0.8-00180

AP60B9.C088.14C0 uptime is 0 days, 0 hours, 28 minutes
Last reload time : Sat Sep 28 00:25:27 UTC 2024
Last reload reason : unknown

cisco C9124AXD-B ARMv8 Processor rev 4 (v8l) with 1798808/1154824K bytes of memo
ry.
Processor board ID FJC28391UEF
AP Running Image : 8.2.20.16
Primary Boot Image : 8.2.20.16
Backup Boot Image : 0.0.0.0
Primary Boot Image Hash:
Backup Boot Image Hash:
3 Multigigabit Ethernet interfaces
2 802.11 Radios
Radio FW version : QC_IMAGE_VERSION_STRING=WLAN.HK.2.7-04674-QCAHKSWPL_SILICONZ-
1
NSS FW version : NSS.FW.12.0-custom-HK.E_custC

Base ethernet MAC Address : 60:B9:C0:88:14:C0
Part Number : 0-0000-00
PCA Assembly Number : 074-125083-01
PCA Revision Number : C0
PCB Serial Number : FOC282406CB
Top Assembly Part Number : 068-102440-01
Top Assembly Serial Number : FJC28391UEF
Top Revision Number : A0
Product/Model Number : C9124AXD-B

I am aware that I am operating on an old image, do I need to upgrade to 8.10.x.x.x before upgrading to 17.15 or later?

Thank you

Cam

[Scott Fella]

I would lokk here as this will show the upgrade path from an earlier version to the version you want to go with.

https://www.cisco.com/c/en/us/td/docs/wireless/controller/ewc/17-15/rel-notes/ewc-rn-17-15-x.html#upgrade-path-to-cisco-ios-xe-dublin-17.11.x
It doesn't hurt to try to download other images to see if ithe upgrade works.  Download ap1g6a-k9w8-tar.153-3.JPQ4.tar and see if that works.  You have a controller, so once it joins, then you are fine.

This matrix will show you the compatibility for the 9800 controller you have and the code you are running with the ap you have.

https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

[griffitd904]

Thank you, Scott! I'll check it out here momentarily.

You

[griffitd904]

I've downloaded the image ap1g6a-k9w8-tar.153-3.JPQ4.tar to set up for a manual upload via TFTP; however, commands like copy, tar, set and debug capwap console cli are not available--seems like bootloader is restricted. 

I confirmed that I can ping the AP from the SWITCH

I confirmed that I can ping the AP from the WLC

If I can't move forward with the tar command, what other options do I have? Your time is very appreciative. 

[muhammadshafqat2a]

If commands like copy, tar, and debug capwap aren't available, your AP is likely in ROMMON/recovery mode.

Try this:

1. TFTP Recovery via Mode Button:

   • Hold Mode button while powering on the AP.

   • Release when LED turns amber/red (~20 sec).

   • Rename image to ap1g6a-k9w8-tar.default.

   • Set your TFTP server IP to 10.0.0.2.

2. Check TFTP Server:

   • Same subnet as AP.

   • No firewall blocking.

   • Monitor for file request logs.

Let me know if you need help with TFTP setup!

[Leo Laohoo]

---

@griffitd904 wrote:

AP Running Image : 8.2.20.16
Primary Boot Image : 8.2.20.16

---

Where did this AP come from? 

If is running an special engineering software and the certificate to validate the new image may have expired.

Try using 17.12.5 firmware (ap1g6a-k9w8-tar.153-3.JPQ4.tar).

[griffitd904]

Hi Leo-

I've downloaded the image ap1g6a-k9w8-tar.153-3.JPQ4.tar to set up for a manual upload via TFTP; however, commands like copy, tar, set and debug capwap console cli are not available--seems like bootloader is restricted. 

I confirmed that I can ping the AP from the SWITCH

I confirmed that I can ping the AP from the WLC

If I can't move forward with the tar command, what other options do I have? Your time is very appreciative. 

[muhammadshafqat2a]

If commands like copy, tar, and debug capwap aren't available, your AP is likely in ROMMON/recovery mode.

Try this: TFTP Recovery via Mode Button:

Hold Mode button while powering on the AP.

Release when LED turns amber/red (~20 sec).

Rename image to ap1g6a-k9w8-tar.default.

Set your TFTP server IP to 10.0.0.2.

Check TFTP Server:

Same subnet as AP.

No firewall blocking.

Monitor for file request logs.

Let me know if you need help with TFTP setup!

[griffitd904]

Thank you... I forgot to mention that I already have a TFTP server (Solarwinds) on a Windows PC. That PC can successfully ping the AP, SW, and the WLC. I've already tried "copy tftp://192.168.1.100/ap1g6a-k9w8-tar.default flash:" and it still didn't work considering ap1g6a-k9w8-tar.default was in the TFTP root directory. Was I missing something? Was I supposed to type tftp_init first?

[griffitd904]

Hi Muhammad-- please confirm if this direction is one right way to move forward.

• Rename your .tar file to c9124axd-b.default

• For example: ap1g6a-k9w8-tar.default

• Place it in your TFTP root directory

• Boot the AP while holding the Mode button

• The AP will auto-initiate TFTP without needing to run tftp_init

[Rich R]

@griffitd904 @muhammadshafqat2a 

Those commands and instructions are for older End of Support AP models which used to run Cisco IOS.

The newer AP models run a completely different operating system called AP-COS (ClickOS for Cisco APs).
If the AP is able to boot an existing image (from primary or backup partition) then the command to use is:
AP#archive download-sw /reload <tftp|sftp|http>://<server_ip>/<file_path>

If the AP is not able to boot from either primary or backup partition then you would need a u-boot recovery image which Cisco have never published for 9124 models so in that case RMA would be required.

[griffitd904]

Overall, I sincerely appreciate everyone's responses. I've searched extensively for documentation on how to restore this access point to its original state, but I honestly feel like I've hit a roadblock.

Rich, you've mentioned earlier "try the 17.12.5 image first and if that takes then upgrade from that to 17.15.3. You could even try an earlier one like 15.3.3-JPN6 (17.9.7) ap1g6a-k9w8-tar.153-3.JPN6.tar" I've ready that "ap1g6a" image is designed for older Cisco AP models, such as the 1600, 2600, and 3600 series, which are built on the AP1G6 chipset platform; which therefore is not compatiblewith the 9124AXD-B model due to differences in hardware architecture and firmware requirements. Do need to use the AP1G8 Platform?

And that you are using a TFTP server which supports larger files? Would Solarwinds restrict me from transferring larger files? I've used this for upgrading all of my existing C9300 switches. 

[Rich R]

ap1g6a is the correct image for C9124AXI, C9124AXD, C9124AXE APs.
Not to be confused with the version number which is what I meant by an earlier one.
FYI: 1600 is ap1g2 and 2600/3600 are ap3g2
You can use "sh ap image file summ" on the 9800 WLC so see the list of AP images.

If your TFTP server works with 9300 switch images then file size likely is not a problem.

[griffitd904]

Hi Rich-

This is what I got. 

Here's my existing topology.

AP60B9.C088.14C0#archive download-sw /reload tftp://192.168.101.204/ap1g6a-k9w8-tar.153-3.JPQ4.tar
Download script called with args:[-l tftp://192.168.101.204/ap1g6a-k9w8-tar.153-3.JPQ4.tar -m 0]
Starting download AP image tftp://192.168.101.204/ap1g6a-k9w8-tar.153-3.JPQ4.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 axel-qca ...'
status 'upgrade.sh: ERROR: Image type mismatch. Expected: Got:ap1g6a'
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

Not sure what the problem is. Did the AP reject it because it was too old?

[Rich R]

The only other thing you can try is an older version of software as @Saikat Nandy suggested.
https://software.cisco.com/download/home/286326663/type/286288051/release/15.3.3-JPJ11 (which corresponds to 17.3.8).

If that doesn't work then your only option is RMA because your EFT/beta software clearly isn't recognising the images correctly.