Hello, I have bought an AP 130 unit 01301710160029. When I start it , it stay amber fix. I have console access. I see a DHCP request and give an IP but nothing more after. Is there a way to help me?

[johan1]

U-Boot 2012.10 (Aug 05 2019 - 20:48:35)

I2C:  ready

Wait.

Done.

DEV ID= 0000cf12

REV ID= 00000000

SKU ID = 2

OTP status: eca01028

MEMC 0 DDR speed = 533MHz

Log: ddr40_phy_init.c: Configuring DDR Controller PLLs

Log: offset = 0x18010800

Log: VCO_FREQ is 1066 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: 256 MiB

WARNING: Caches not enabled

GPIO Init ... Done

NAND:  NAND_FLASH_DEVICE_ID_ADDR = 18028194

Done that

(ONFI), W29N04GV, blocks per lun: 1000 lun count: 1

*WARNING* Invalid strap options for this NAND: page=1 type=2

Overriding invalid strap options: strap_type=2

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=800MHz, axi_clk=400MHz, apb_clk=200MHz, arm_periph_clk=400MHz

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: 0x53011

bcmiproc_eth-0

MAC address is c867:5e4a:5e80

NVRAM_MAGIC found at offset 440000

nvram_init: ret 1

Reset TPM chip...

Reset AUTH chip...

Hit any key to stop autoboot: 0

Loading kernel from device 0: nand0 (offset 0x580000) ... done

Loading rootfs from device 0: nand0 (offset 0xf80000) ... done

## Booting kernel from Legacy Image at 01005000 ...

  Image Name:  Linux-3.16.36

  Image Type:  ARM Linux Kernel Image (uncompressed)

  Data Size:   2479437 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:   28565504 Bytes = 27.2 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...

Do the DB init,please wait...

jffs2: notice: (60) check_node_data: wrong data CRC in data node at 0x137927a0: read 0x7854a223, calculated 0x722a6e35.

ah_net: module license 'unspecified' taints kernel.

Disabling lock debugging due to kernel taint

Updating system config database...

System config update complete.

gmac_var_init: NAPI2_POLL mode

Jumbo disabled

Jumbo disabled

eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)

register sniffer device on interface eth0.

Jumbo disabled

Jumbo disabled

Aerohive Wireless Extension 2.0.0 ... INIT!

Aerohive Forwarding Engine module ... INIT!

Image L7 repository version 5, checking existing L7 repository... ...

Existing L7 repository version 5

Nothing to be done or verified with L7 repository version 5

kddr enable

Welcome to Aerohive Product

Learning Support login:

[ashley_finch]

Hello,

There may be a difference in which server you connect to (IP wise) but otherwise there shouldn't be a difference I don't think. Glad you got it working though.

[johan1]

Hello

Yesterday I use an IQ cloud account with no 30 days test. Just free portal.
System stop at fix amber led at each time. I test reset hardware, let 2 hours connected for upgrade, reboot, etc…
Nothing append.

Today, I have create a new portal account with 30 days testing.
And now after 5 minutes, the hardware is connected with white LED and apply my local Policy.
[cid:image004.png@01D5EBCE.97190F90]

Is there a difference between the trial cloud and free cloud (after 30 days) for onboarding ?
In the free cloud account, I have 3 AP130 with firmware 6.5. In ne new try cloud account only this unit.

For finishing my test:

* I remove AP130 from the trial cloud account
* I connect to the free cloud account, I had the unit

* It became white after 2 minutes
* I see it into the cloud console
* The system reboot 2 times
* It became white now
* It works

So I don’t understand why I have “unlock” the product by adding it to a trial cloud portal and be able to come back to standard portal.

Anyway, it works. Sorry for my question.

Best regards
Johan DEVELON

[ashley_finch]

Have you got a hivemanager/CloudIQ account? If so I'd follow this guide to get it connected:

https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG