AIR-AP3802I-E-K9 - Page 2

UPTONKEVERN · ‎07-01-2021

Hi All.

Thanks in advance for any assistance.

I picked up a second hand AIR-AP3802I-E-K9 whos serial number appears on the list of affected AP's that were manufactured Dec 2017 and January 2018 that exhibit unable to connect to wired network, spamming "awaiting IP uplink and gateway" messages in console.

Version 8_5_111_0

I ran a factory reset by holding mode in on boot, then releasing when seconds counter in console reached 20 seconds.
I had plugged in AUX cable and was able to execute ap-type capwap, capwap ap restart, capwap ap ip xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx dnsl xxx.xxx.xxx.xxx domain (took my details out on this post for security), and managed to set the static IP address.

When running a ip int brief the Wired0 and Wired1 interfaces are both up, protocol up, with IP being assigned to Wired 1 and speed on Wired 0 being n/a. I cannot ICMP.

When checking the interfaces there is receive and transmit packets, however the AP cannot icmp the connected network nor can any of the other network clients ICMP it.

I ran a uboot>> prompt dhcp command and the PoE primary interface does pull a IP address from a MS DHCP server scope and I am able to ping the network.

It seems to me as if the unit will need a IOS recovery, either Cisco Mobility image or Capwap image, however as I bought these units second hand I cannot log a TAC case to understand the recovery process for a AIR-AP3802I-E-K9.
Further, when searching for IOS recovery documents on CISCO there is reference to a 2800/3600/3800 and then it gets vauge and then references 3600 only using ***.mz image and not ap3g3-k9w8-tar.153-3.JPK1.tar that is used for archive recovery.

The challenge here is that the inherent bug that is causing the network issue rules out archive recovery under normal boot and there appears to be no documentation for recovery through uboot. Also, Cisco website does not offer images persay for tftpxx recovery.

Does anyone know or can assist (without a TAC case), how to do a recovery through uboot , dhcp, or other option?
A response would be greatly appreciated.

Leo Laohoo · ‎08-17-2023

If the AP can boot normally, force the AP to boot "part2": config boot path 2

And then reboot the AP.

adrianmihaita · ‎08-17-2023

Hi Leo,

Both APs are in a U-Boot loop.

One AP has the below behavior

I have switched the boot partition using

setenv boot path2 / path1 && saveenv

u-boot>> printenv
BOOT=path1 (part1) or path 2 (part2)

I get this result

u-boot>> boot

NAND read: device 0 offset 0x100000, size 0x100000
1048576 bytes read: OK

Checking image signing.
Image signing verification failure(-2), not allowed to run...

For the other one the behavior is

u-boot>> boot
invalid mtd device 'armada-nand'
mtdparts_init: no valid partitions
Error initializing mtdparts!
Error: Unable to ubi mount mtd device fs

Leo Laohoo · ‎08-18-2023

Contact Cisco TAC and organize for an RMA.

adrianmihaita · ‎08-18-2023

Is there any other way to fix this 2 APs?

I do not really have the option to contact TAC, I bought used APs and I do not have a valid contract with Cisco.

Thank you!

Leo Laohoo · ‎08-18-2023

@adrianmihaita wrote:
I do not really have the option to contact TAC, I bought used APs and I do not have a valid contract with Cisco.

Limited Lifetime Hardware Warranty comes with every purchase of the 3800.

The AP can be RMA without a valid Service Contract.

adrianmihaita · ‎08-18-2023

APs are 2800 series and I have found the same warranty as for 3800

https://www.cisco.com/c/en/us/products/collateral/wireless/aironet-2800-series-access-points/datasheet-c78-736497.html#Warrantyinformation

The thing is that I`m not the original end user of these 2 APs and I do not think that Cisco will agree on a RMA without a contract.

You are right, the RMA will be the easiest solution, but since I will not qualify for it I`m searching for a solution to solve my problems.

Thank you!

Leo Laohoo · ‎08-18-2023

It will not hurt to, at the very least, TRY.

The worse TAC can do is say "no".

Bertote · ‎09-03-2023

Hello adrianmihaita.

Did you solve your problem?
I'm having a similar problem with an 1832i.
If you have a solution, I appreciate you sharing it.

DRAM: 1 GiB
NAND (ONFI): Detected SPANSION S34MS02G1 [256 MiB]
SF: Detected Macronix MX25U3235F [4 MiB]
MFG data loaded
Scanning shenv data blocks
Total valid parts=4
Active shenv part[1:1], write_counter=52
PCI0 Link Intialized
PCI1 Link Intialized
Net:
PHY ID = 0x4dd074, eth0 found AR8033 PHY
PHY ID = 0x4dd074, eth1 found AR8033 PHY
Valid I2C chip addresses: 51 52
AP 1832/1852 detected...
Power Type: 802.3at POE detected...
Signature returns 0
BL signing verification success, continue to run...
Auto boot mode, use bootipq directly
Hit ESC key to stop autoboot: 0
Specified BOOT: part1

Booting from part1

Volume part1 not found!
Volume part1 not found!

Booting failed, try boot on part2

Volume part2 not found!
Volume part2 not found!
(RNAQ-C7) # bootipq tftp
Specified BOOT: part1

Booting from tftp

No such device:
No such device:
Full duplex link
Port:2 speed 1000Mbps
Using eth0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'part.bin'.
Load address: 0x45000000
Loading: T #######....etc....

After booting via tftp, I try to flash the firmware, but it's not possible.

I performed the process of creating the flash partition, but it was not 100%, it returns an error in part2 and it is not possible to efficiently write the firmware.

Starting download AP image tftp://172.30.10.100/ap1g4 ...
It may take a few minutes. If longer, please abort command, check network and try again.
# # # # -=O=-
Image download completed.
Upgrading ...
upgrade.sh: Script called with args:[NO_UPGRADE]
do NO_UPGRADE, part1 is active part
upgrade.sh: Script called with args:[-c PREDOWNLOAD]
do PREDOWNLOAD, part1 is active part
upgrade.sh: Start doing upgrade arg1=PREDOWNLOAD arg2=,from_cli arg3= ...
upgrade.sh: Using image /tmp/cli_part.tar on corsica ...
sh: duplo: unknown operand
Image signing verify success.
upgrade.sh: btldr version: AP ver 41, image ver 31
Verify returns 0
Unlocking /dev/mtd4 ...
Erasing /dev/mtd4 ...
23+0 records in
23+0 records out
upgrade.sh: btldr is updated successfully!
upgrade.sh: Copying to /storage/boot_part2: info
upgrade.sh: Copying to /storage/boot_part2: final_hash
upgrade.sh: Copying to /storage/boot_part2: file_hashes
upgrade.sh: Copying to /storage/boot_part2: btldr_md5
upgrade.sh: Copying to /storage/boot_part2: btldr.bin.lzma
upgrade.sh: Copying to /storage/boot_part2: info.ver
upgrade.sh: Done with copying corsica btldr to /storage/boot_part2
upgrade.sh: part to upgrade is part2
upgrade.sh: AP version1: part2 , img 8.5.182.0
upgrade.sh: Updating UBI device...
libubi: error!: cannot get information about "/dev/ubivol/part2"
error 2 (No such file or directory)
ubiupdatevol: error!: error while probing "/dev/ubivol/part2"
error 2 (No such file or directory)
upgrade.sh: AP version2: part2 8.5.182.0, img 8.5.182.0
upgrade.sh: AP backup version: 8.5.182.0
upgrade.sh: Finished upgrade task.
upgrade.sh: Cleanup for do_upgrade...
upgrade.sh: /tmp/upgrade_in_progress cleaned
upgrade.sh: Cleanup tmp files ...
upgrade.sh: Script called with args:[ACTIVATE]
do ACTIVATE, part1 is active part
upgrade.sh: activate part2, set BOOT to part2
upgrade.sh: AP primary version after reload: 8.5.182.0
upgrade.sh: AP backup version after reload: 8.10.183.0
Successfully setup AP image.
Archive done.
APF8B7.E2C0.34F0#
Read timed out

Found new boot image.
Validating new image integrity ...New boot image blocked to keep compatibility
Clean up invalid new boot image ...
Erasing at 0x33f000 -- 100% complete.
Signature returns 0
BL signing verification success, continue to run...
Auto boot mode, use bootipq directly
Hit ESC key to stop autoboot: 0
Specified BOOT: part2

Booting from part2

Volume part2 not found!
Volume part2 not found!

Booting failed, try boot on part1

Read 1024 bytes from volume part1 to 45000000
(RNAQ-C7) #

If you or someone else can help me, I will be very grateful, because it is not possible to RMA with the TAC.

Leo Laohoo · ‎09-03-2023

@Bertote wrote:
because it is not possible to RMA with the TAC.

Why not?

Every 1832 purchased comes with Limited Lifetime Hardware Warranty included every purchase. There is no need for a valid Service Contract.

Bertote · ‎09-03-2023

Hello Leo, I think it will not be possible, because I bought the Ap on a site similar to ebay, called OLX. I bought it from a seller who does not offer the origin of the equipment. I believe that RMA is only valid for purchases from official stores.
But if you inform that it is possible, what are the steps to request?

Leo Laohoo · ‎09-04-2023

@Bertote wrote:
I think it will not be possible

Try.

Worse case scenario: TAC says no but at the very least, you tried.

Bertote · ‎09-04-2023

Well... In the beginning I had the answer...

Leo Laohoo · ‎09-04-2023

Show that to the TAC agent so they can manually fill in the details.