topic Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea? in Aerohive Migrated Content

AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

dragosadrianant — Thu, 31 Jan 2019 16:50:35 GMT

AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

samantha_lynn — Thu, 31 Jan 2019 21:51:25 GMT

The orange/amber light means broadcasting (assuming it has a configuration) but not connected to the HiveManager. Depending on which HiveManager platform you are using, these guides will help you manually connect the AP to the HiveManager and diagnose why it wouldn't connect automatically.

HiveManager Classic (myhive.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/CAPWAP-HiveManager-Classic

HiveManager (formerly NG, cloud.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG

Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

dragosadrianant — Fri, 01 Feb 2019 02:01:23 GMT

Hi Sam,

I tried to connect manually using Putty and a console connection. The AP starts to boot and after that is stuck, without any ethernet connection. The reset button is useless as the AP do not react when I push it for at least 10 seconds (waited 1 minute)

This is what the console reports until it get stuck:

U-Boot 2012.10 (Aug 21 2018 - 20:22:25)

I2C: ready
Wait.
Done.
DEV ID= 0000cf12
REV ID= 00000000
SKU ID = 0
OTP status: eca00018
MEMC 0 DDR speed = 800MHz
Log: ddr40_phy_init.c: Configuring DDR Controller PLLs
Log: offset = 0x18010800
Log: VCO_FREQ is 1600 which is greater than 1Ghz.
Log: DDR Phy PLL polling for lock
Log: DDR Phy PLL locked.
Log: ddr40_phy_init::DDR PHY step size calibration complete.
Log: ddr40_phy_init:: Virtual VttSetup onm CONNECT=0x01CF7FFF, OVERRIDE=0x00077FFF
Log: ddr40_phy_init:: Virtual Vtt Enabled
Log: DDR Controller PLL Configuration Complete
PHY register dump after DDR PHY init
PHY register dump after mode register write
DRAM: 512 MiB
WARNING: Caches not enabled
GPIO Init ... Done
Power Input Detection: POE AT, Drive GPIO17(USB 5V enable) success
NAND: NAND_FLASH_DEVICE_ID_ADDR = 18028194
Done that
(ONFI), S34ML04G2, blocks per lun: 1000 lun count: 1
128 KiB blocks, 2 KiB pages, 16B OOB, 8-bit
NAND: chipsize
total 0 bad blocks,LIST:
now the up level will see a good flash chip no bad block which size is 20000000
before nvram partition, there are 0 bad blocks
512 MiB
Using default environment

In: serial
Out: serial
Err: serial
Unlocking L2 Cache ...Done
arm_clk=1000MHz, axi_clk=500MHz, apb_clk=250MHz, arm_periph_clk=500MHz
Net: Registering eth
Broadcom BCM IPROC Ethernet driver 0.1
Using GMAC1 (0x18025000)
et0: ethHw_chipAttach: Chip ID: 0xcf12; phyaddr: 0x1e
bcm_robo_attach: devid: 0x53012
bcmiproc_eth-0
MAC address is c413:e244:9f80

NVRAM_MAGIC found at offset 700000
nvram_init: ret 1
Reset TPM chip...
Reset AUTH chip...
Hit any key to stop autoboot: 0
Hit any key to interrupt boot from flash: 0

Loading kernel from device 0: nand0 (offset 0x800000) ... done
Loading rootfs from device 0: nand0 (offset 0x1600000) ... done
## Booting kernel from Legacy Image at 01005000 ...
Image Name: Linux-3.16.36
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2474169 Bytes = 2.4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02005000 ...
Image Name: uboot initramfs rootfs
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 30732288 Bytes = 29.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Power off two PHY...
Loading Kernel Image ... OK
OK
boot_prep_linux commandline: root=/dev/ram console=ttyS0,9600 ramdisk_size=70000 cache-sram-size=0x10000

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
L2C: platform provided aux values match the hardware, so have no effect. Please remove them.
L2C: platform provided aux values permit register corruption.
Mounting local file systems...
UBI device number 0, total 3256 LEBs (413433856 bytes, 394.3 MiB), available 75 LEBs (9523200 bytes, 9.1 MiB), LEB size 126976 bytes (124.0 KiB)
ah_net: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
Updating system config database...
System POE Input Detection -> confAT
ig update complete.
gmac_var_init: NAPI2_POLL mode
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)
register sniffer device on interface eth0.
eth1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)
register sniffer device on interface eth1.

I tried to stop from auto boot but it is asking me for a password and I tried "aerohive", "Aerohive1" and "Aerohive" but didnt work.
Please advice.

Regards,
Dragos ANTON

Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

samantha_lynn — Fri, 01 Feb 2019 04:34:22 GMT

We'll need to try a TFTP flash to see if we can end the boot loop the AP is stuck in. Unfortunately that password isn't something we can share, we'll need to make a technical support case and schedule a call with a technician so they can enter it for you. If you don't have the ability to open a case via Hive Community, please email me directly and we'll discuss our options from there.

Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

dragosadrianant — Fri, 01 Feb 2019 04:37:19 GMT

Hi Sam,

I don't have the ability to open a case. Please advise.

Regards
Dragos

On Thu, 31 Jan 2019, 20:34 Aerohive

Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

AnonymousM — Thu, 18 Jul 2019 04:30:29 GMT

I have struck the same problem on 2x AP250s running 10.0r5

atatc could not resolve over a remote session, and arranged an RMA.

Re: AP 250 stuck with orange light. Tried to hard rest it but without succes. Any ideea?

denisphan2k17 — Thu, 28 Nov 2019 17:09:28 GMT

Hi,

I think some lots of AP250 having this problem.IMO, maybe module wifi1 was damaged then hangs up the device booting process.

Thank