Wireless Access

I have one brand new aruba AP-207, I want to work with our controller 7024,but we get the followed information, are there anybody can tell me the reason ? Thanks

 

 

APBoot 2.1.4.11 (build 59208)
Built: 2017-04-13 at 18:41:18

Model: AP-207
CPU: BCM47452 revision: 3
Clock: 900 MHz, DDR rate: 533 MHz
DRAM: 255 MiB
Flash: Detected W25Q32FV: total 4 MiB
NAND: No NAND flash type found
NAND chip could not be initialized
0 MiB
PCIe0: RC, link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 aa31 00002 02 00000004 00000000 00000004 00000000
Power: POE
Device nand0 not found!
Error initializing mtdparts!
Net: eth0
Radio: bcm43570#0, bcm47452#1
Reset: warm
FIPS: passed

Hit <Enter> to stop autoboot: 0
Checking image @ 0x0
Device nand0 not found!
Error initializing mtdparts!
Error, no UBI device/partition selected!
Invalid image format version: 0x801c0140
Checking image @ 0x2000000
Device nand0 not found!
Error initializing mtdparts!
Error, no UBI device/partition selected!
Invalid image format version: 0x143c8ab2
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 192.168.100.195
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.100.222
DHCP DNS server: 192.168.100.222
DHCP DNS domain:
ADP multicast 1
Controller address: 192.168.100.60
Using eth0 device
TFTP from server 192.168.100.60; our IP address is 192.168.100.195
Filename 'armv7ns.ari'.
Load address: 0x4100000
Loading: #################################################################
#################################################################
##################################################
743.2 KiB/s
done
Bytes transferred = 11516548 (afba84 hex)

Image is signed; verifying checksum... passed
SHA2 Signature available
Signer Cert OK
Policy Cert OK
RSA signature verified using SHA2.
Automatic boot of image at addr 0x04100000 ...
Uncompressing... done
[ 0.000000]
[ 0.000000] Aruba Networks
[ 0.000000] ArubaOS Version 8.3.0.0 (build 64659 / label #64659)
[ 0.000000] Built by p4build@pr-hpn-build09 on 2018-04-27 at 22:00:09 UTC (gcc version 4.7.2)
[ 0.000000]
[ 0.000000] Flash variant: default
[ 0.000000] MPCORE found at 18310000, SCTLR 0x10c53c7f ACTLR 0x00006040 CPSR 0x600001d3 SPSR 0x000001d3 PRRR 0xff0a81a8 NMRR 0x40e040e0
[ 0.000000] Memory: 256MB = 256MB total
[ 0.000000] Memory: 245812k/245812k available, 16332k reserved, 0K highmem
[ 0.000000] External imprecise Data abort at addr=0xde0daa4a, fsr=0xc06 ignored.
[ 0.000000] Found ST compatible serial flash with 64 64KB blocks; total size 4MB
[ 0.000000] MPCORE Global Timer Clock 34714Hz
[ 0.046000] CCA UART Clock Config: Sel=1 Ovr=1 Div=88
[ 0.046000] CCA UART Clock rate 40000000Hz
[ 0.048000] ACP (Accelerator Coherence Port) disabled
[ 7.102000] PCI: no core
[ 7.102000] PCI: no core
[ 7.306000] PCI: scanning bus 0
[ 7.306000] PCI: Fixing up bus 0
[ 7.560000] PCIE1 link=1
[ 7.560000] PCIE1 switching to GEN2
[ 7.810000] PCIE1 link=1
[ 7.810000] PCI: Fixing up bus 0
[ 7.810000] PCI: Fixing up bus 1
[ 7.812000] pci 0001:00:00.0: BAR 8: assigned [mem 0x10000000-0x105fffff]
[ 7.812000] pci 0001:01:00.0: BAR 2: assigned [mem 0x10000000-0x103fffff 64bit]
[ 7.812000] pci 0001:01:00.0: BAR 2: set to [mem 0x10000000-0x103fffff 64bit] (PCI address [0x10000000-0x103fffff]
[ 7.812000] pci 0001:01:00.0: BAR 0: assigned [mem 0x10400000-0x10407fff 64bit]
[ 7.812000] pci 0001:01:00.0: BAR 0: set to [mem 0x10400000-0x10407fff 64bit] (PCI address [0x10400000-0x10407fff]
[ 7.868000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 7.980000] Creating 1 MTD partitions on "bcmsflash":
[ 7.982000] 0x000000000000-0x000000400000 : "nor"
[ 7.984000] Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
[ 7.986000] brcmnand: found no supported devices
[ 7.988000] UBI error: ubi_init: UBI error: cannot initialize UBI, error -2
[ 7.990000] i2c-springbank: using remapped base d0874060
[ 7.992000] mpcore_wdt mpcore_wdt: enabling watchdog.
[ 7.994000] ramzswap: num_devices not specified. Using default: 1
[ 7.996000] ramzswap: Creating 1 devices ...
[ 8.120000]
[ 8.120000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[ 8.124000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[ 8.218000] Starting Kernel DES KAT ...Completed Kernel DES KAT
[ 8.222000] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 8.224000]
[ 8.226000] Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT
Populate AP type info
AP-type has_ble_support: BRCM_ONBOARD.
Domain Name: arubanetworks.com
[ 10.504000] UBIFS error (pid 300): ubifs_get_sb: cannot open "ubi2:ubifs", error -19
mount: Mounting ubi2:ubifs on /aruba/fs failed: No such device
Mounting ubifs failed
apfcutil: apfc_read failed: Cache uninitialized
Will reboot to mount ubifs
killall: nanny: no process killed
killall: sapd: no process killed
apfcutil: apfc_write failed: Cache uninitialized
SIOCSIFADDR: No such device
Sending SIGKILL to all processes.
Unmounting UBIFS failed. Please report this error (Invalid argument).

Please stand by while rebooting the system.
[ 20.014000] Restarting system.

APBoot 2.1.4.11 (build 59208)
Built: 2017-04-13 at 18:41:18

Model: AP-207
CPU: BCM47452 revision: 3
Clock: 900 MHz, DDR rate: 533 MHz
DRAM: 255 MiB
Flash: Detected W25Q32FV: total 4 MiB
NAND: No NAND flash type found
NAND chip could not be initialized
0 MiB
PCIe0: RC, link up
dev fn venID devID c

I suspect this will probably require an RMA, have you spoken to TAC?

---

@Craig Syme wrote:

I suspect this will probably require an RMA, have you spoken to TAC?

---

no suspicion required, this is 100% an RMA :)

Hi !

I had exactly the same problem.
Even though it sounds incredible, the incompatible console cable was the cause.
First I tested the cable with the CP2102 USB chip.
Then I tested the cable with the USB chip CH340G.
Both cables behaved equally (badly).
The original "AP-CBL-SER" cable contains only the MAX3232 voltage converter.
So, you need to use some USB / serial adapter (if you do not have a real serial port on your computer).

 

I hope this will help.

Lubos

Please note that using "random cables" on your APs serial port might damage your hardware. So if you don't really know what you are doing or if you are afraid of damaging your hardware and having to buy a new AP, please just use the cable supplied by Aruba instead. As already mentioned before, the problem here is the serial cable or USB to serial adapter. I had the very same problem with my CP2102 adapter. So if you are willing to risk destroying your AP, here is what helped me out: For some reason, the problem exists on the RX line (PC in) on my adapter. I managed to solve it adding a 100k pull down resistor between the data lines (RX/TX) and the GND. This solved the problem for me. Again: I have no real clue why the adapter breaks the nand detection, when the USB adapter is connected. Finding out what's going wrong with the cable would normally require to measure and detect current leakage on the port. So please be careful with this solution and if in doubt, really consider buying a "certified" cable.

@hansacker
do you mean resistor connection like this
RXD > 100k > GND

TXD  ​​> 100k > GND
so I need two resistors there

Original Message:
Sent: Mar 05, 2020 06:17 AM
From: Hans Acker
Subject: How to make Aruba AP-207 work ? Only APboot no nand flash ?

Please note that using "random cables" on your APs serial port might damage your hardware. So if you don't really know what you are doing or if you are afraid of damaging your hardware and having to buy a new AP, please just use the cable supplied by Aruba instead. As already mentioned before, the problem here is the serial cable or USB to serial adapter. I had the very same problem with my CP2102 adapter. So if you are willing to risk destroying your AP, here is what helped me out: For some reason, the problem exists on the RX line (PC in) on my adapter. I managed to solve it adding a 100k pull down resistor between the data lines (RX/TX) and the GND. This solved the problem for me. Again: I have no real clue why the adapter breaks the nand detection, when the USB adapter is connected. Finding out what's going wrong with the cable would normally require to measure and detect current leakage on the port. So please be careful with this solution and if in doubt, really consider buying a "certified" cable.