AP3802I not booting up to new version or joining network.

[jgarriso@robinsonmfg.com]

Good morning.   We have a mix of AP's on our Mobility Express Network,  1852's 1832's 2702's  and now i have a set of 3802i's that i need to get to join.   Currently the MOblity express networks at my company are at 8.10.151.0  The 3802's came with 8.5.161.0.  I know that there is an issue making the jump automatically. But i can do the ap-type command and load the version with the tftp server and it shows it as the primary Boot version (see below),  but no matter what i do i cannot get it to actually boot to or join to the 8.10.151.0  can someone provide a suggestion for me.   Thanks.  about to start beating my head against a wall.

AP7872.5D4F.2572 uptime is 0 days, 18 hours, 01 minutes
Last reload time : Thu Sep 29 13:49:59 UTC 2022
Last reload reason : unknown

cisco AIR-AP3802I-B-K9 ARMv7 Processor rev 1 (v7l) with 1028704/649352K bytes of memory.
Processor board ID FCW2229NQGF
AP Running Image : 8.5.161.0
Primary Boot Image : 8.10.151.0
Backup Boot Image : 0.0.0.0
1 Multigigabit Ethernet interfaces
1 Gigabit Ethernet interfaces
2 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version : 2.4.26

Base ethernet MAC Address : 78:72:5D:4F:25:72
Part Number : 73-018550-02
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC22276Q6Q
Top Assembly Part Number : 068-100730-02
Top Assembly Serial Number : FCW2229NQGF
Top Revision Number : E0
Product/Model Number : AIR-AP3802I-B-K9

[Dustin Anderson]

How does the AP find the WLC? Do you have the DHCP option, or are you priming them? What do you see with a console cable connected to the AP?

[jgarriso@robinsonmfg.com]

The unit is on the network and is sending join request to the ME Controller,  but i know that it is not able to jump from 10.5 to 10.10.   Although i can do a ap-type mobility-express tftp upload and it says it has installed the 10.10.151.0  but it will not boot to it.

CAPWAP State: Discovery
[*09/29/2022 13:51:58.2463] IP DNS query for CISCO-CAPWAP-CONTROLLER.robinson.local
[*09/29/2022 13:51:58.2506] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2022 13:51:58.2506]
[*09/29/2022 13:51:58.2506] CAPWAP State: Discovery
[*09/29/2022 13:51:58.2534] Discovery Response from 10.1.0.251
[*09/29/2022 13:51:58.2609] Unsupported vendor spec payload TLV_VENDOR_SPECIFIC_PAYLOAD(215) for msgtype 2
[*09/30/2022 17:52:02.0000] can't find the Ip from discoveryRequest array
[*09/30/2022 17:52:02.0000]
[*09/30/2022 17:52:02.0001]
[*09/30/2022 17:52:02.0001] CAPWAP State: DTLS Setup
[*09/30/2022 17:52:02.6909]
[*09/30/2022 17:52:02.6909] CAPWAP State: Join
[*09/30/2022 17:52:02.6926] Sending Join request to 10.1.0.251 through port 5272
[*09/30/2022 17:52:02.7025] Join Response from 10.1.0.251
[*09/30/2022 17:52:02.7829] HW CAPWAP tunnel is ADDED
[*09/30/2022 17:52:02.7998]
[*09/30/2022 17:52:02.7998] CAPWAP State: Image Data
[*09/30/2022 17:52:02.8366] do PRECHECK, part2 is active part
[*09/30/2022 17:52:02.9767] Image Data Request sent to 10.1.0.251

[jgarriso@robinsonmfg.com]

Says  Image download did not start.

Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).
[*09/30/2022 17:56:08.7943] Invalid event 50 & state 10 combination.
[*09/30/2022 17:56:08.7943] SM handler: Failed to process timer message. Event 50, state 10
[*09/30/2022 17:56:08.7944] Failed to handle timer message.
[*09/30/2022 17:56:08.7945] FSM failure while processing message with id: 1
[*09/30/2022 17:56:08.9837] Image download did not start for 120 seconds.
[*09/30/2022 17:56:08.9837]
[*09/30/2022 17:56:08.9837] Lost connection to the controller, going to restart CAPWAP (reason : image download cannot start)...
[*09/30/2022 17:56:08.9837]
[*09/30/2022 17:56:08.9838] Restarting CAPWAP State Machine.
[*09/30/2022 17:56:09.0880] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).
[*09/30/2022 17:56:09.0898]
[*09/30/2022 17:56:09.0898] CAPWAP State: DTLS Teardown
[*09/30/2022 17:56:10.0994] Dropping dtls packet since session is not established. Peer 10.1.0.251-5246, Local 10.1.5.84-5272, conn (nil)
[*09/30/2022 17:56:14.7355] do ABORT, part2 is active part
[*09/30/2022 17:56:14.8581]
[*09/30/2022 17:56:14.8581] CAPWAP State: Discovery
[*09/30/2022 17:56:14.8589] IP DNS query for CISCO-CAPWAP-CONTROLLER.robinson.local
[*09/30/2022 17:56:14.8653] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/30/2022 17:56:14.8664] Discovery Response from 10.1.0.251
[*09/30/2022 17:56:14.8735] Unsupported vendor spec payload TLV_VENDOR_SPECIFIC_PAYLOAD(215) for msgtype 2
[*09/30/2022 17:56:20.3601] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*09/30/2022 17:56:23.9801] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*09/30/2022 17:56:25.0000] can't find the Ip from discoveryRequest array
[*09/30/2022 17:56:25.0000]
[*09/30/2022 17:56:25.0001]
[*09/30/2022 17:56:25.0001] CAPWAP State: DTLS Setup
[*09/30/2022 17:56:25.6841]
[*09/30/2022 17:56:25.6841] CAPWAP State: Join
[*09/30/2022 17:56:25.6856] Sending Join request to 10.1.0.251 through port 5272
[*09/30/2022 17:56:25.6940] Join Response from 10.1.0.251
[*09/30/2022 17:56:25.7732] HW CAPWAP tunnel is ADDED
[*09/30/2022 17:56:25.7877]
[*09/30/2022 17:56:25.7877] CAPWAP State: Image Data
[*09/30/2022 17:56:25.8258] do PRECHECK, part2 is active part
[*09/30/2022 17:56:25.9776] Image Data Request sent to 10.1.0.251

[jgarriso@robinsonmfg.com]

when i do the tftp upload it says

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
upgrade.sh: Writing image to disk...
sh: 0: unknown operand
upgrade.sh: activate part1, set BOOT to part1
upgrade.sh: AP primary version: 8.10.151.0
Archive done.
[*09/30/2022 17:59:59.5095] .....No change in AP Type Configuration......

Here is where the version shows

AP Running Image : 8.5.161.0
Primary Boot Image : 8.10.151.0
Backup Boot Image : 0.0.0.0

But it will not boot to the primary

[marce1000]

                 - FYI : https://www.cisco.com/c/en/us/support/docs/field-notices/701/fn70143.html

 M.

[Dustin Anderson]

Not sure that field notice pertains to it since the error is it can't connect to the network, but his can as you see it try to join the controller.

Can you get the 8.8 code and see if you can load that? it seems like it isn't taking the new firmware for some reason. Should be able to upgrade, but sometimes may have to step through for possible firmware updates. You can try TAC for the possible field notice as they may have a forced install from the TFTP that would probably reformat the AP.

[jgarriso@robinsonmfg.com]

Thanks.

[jgarriso@robinsonmfg.com]

This might be a dumb question,  but here it goes.   Do i need the 3800 mobility express firmware,  or are all the mobility express firmware the same.  Meaning when i 'join'  the network it tries to install the firmware,  which firmware.  I have the 3800 8.10.151.0  downloaded but i don't have access yet to the  8.8.131.0 as my contract hasn't gone into the system yet.

[jgarriso@robinsonmfg.com]

Is there a way to copy the part 1 to part 2?  or primary to backup?

Image downloaded, writing to flash...
do CHECK_ME, part2 is active part
Image signing verify success.
upgrade.sh: part to upgrade is part1
upgrade.sh: Writing image to disk...
sh: 0: unknown operand
upgrade.sh: activate part1, set BOOT to part1
upgrade.sh: AP primary version: 8.8.130.0
Archive done.
[*09/30/2022 19:14:09.2632]

I reboot and it says cannot boot from that

/22/2018 23:59:59.0063] Last reload time: Sep 30 19:15:06 2022
[*09/30/2022 19:15:06.0001] Setting system time Fri Sep 30 19:15:06 UTC 2022
[*09/30/2022 19:15:06.1152] Loading kernel crypto modules
[*09/30/2022 19:15:06.2378] GCM-128 POST passed
[*09/30/2022 19:15:06.2378] GCM-256 POST passed
[*09/30/2022 19:15:06.8594] MGIG Bundeled version 201, Tarball version 201
[*09/30/2022 19:15:06.8812] Identified Ethernet mGig PHY: mv2010
[*09/30/2022 19:15:13.0669] Unable to boot from prefered partition part1. Booted from part2.
[*09/30/2022 19:15:13.6775] Active version: 8.5.161.0
[*09/30/2022 19:15:13.6787] Backup version: 0.0.0.0
[*09/30/2022 19:[09/30/2022 19:15:13.8300] PCI: enabling device 0000:00:02.0 (0140 -> 0143)
15:13.8310] devi[09/30/2022 19:15:13.9200] PCI: enabling device 0000:02:00.0 (0140 -> 0142)

[*09/30/2022 19:14:09.2632] .....No change in AP Type Configuration......
[*09/30/2022 19:14:09.2632]

[Dustin Anderson]

On a side note, it looks like the the current image is part2 and new image is part1. When it starts to boot, see if you see it loading from part 1, if not here is the command reference to change it.

config boot path

To configure the boot path, use the config boot path command.

config boot path { 1 | 2}

Syntax Description

 

{1 | 2}

Path to be specified as Part 1 or Part 2

Command Modes

Privileged EXEC (#)

Command History

 Release Modification

8.1.111.0

This command was introduced.

Examples

The following example shows how to configure the booth path as 1:

cisco-wave2-ap# config boot path 1 

[jgarriso@robinsonmfg.com]

Just saw this.  Thanks,  i will check out.

[jgarriso@robinsonmfg.com]

No matter what i try i seem to get the "image signing verification error" and it goes to part2.

Loading file 'part1/part.bin' to addr 0x02000000 with size 62958260 (0x03c0aab4)...
Done
SF: Detected MX25L3205D with page size 64 KiB, total 4 MiB

Checking image signing.
Image signing verification failure(-20), not allowed to run...
Trying alternate partition part2
UBIFS: mounted UBI device 0, volume 1, name "part2"

[Rich R]

You haven't actually shown us what commands you're using but it sounds like you're trying to load it using the ME conversion image?
There are 2 packages on the download page - the tar file for conversion and the zip file for upgrades - which are you using?
Show exactly what commands and what image you're using?

That said there are known issues with ME manual upgrades  - a more reliable option (if you really want to do it the manual way) is to install a 8.10.151.0 lightweight (CAPWAP) image (which can be used to join the ME WLC) and then you can convert from that to ME if you want the AP to be ME capable.

Otherwise you can allow the automatic upgrade (the way it's designed to work) by extracting the images from the zip file on your TFTP server and configuring the TFTP server details on your ME WLC.  The ME WLC will then instruct that AP to download the correct image from the TFTP server automatically when it joins (which is what it's trying to do already).

[jgarriso@robinsonmfg.com]

FYI,  Thank you,  i will try the LIghtweight option.     But the second option will not work.  I have found that it will not make the jump from  8.5 to 8.10 without first being upgraded to at least a 8.8 version.