Wireless Access

Hello,

I have a problem with ap 125, where it obtains an IP address, but does not appear on the provisioning screen, which is in Wireless> AP Installation> Provisioning

Is that AP able to reach the master via one of the Master Discovery options? Is the Master running a suitable firmware which the AP125 supports? Is there sufficient licenses for the AP125 on the controller? Is basic network connectivity between the master and AP125 in place?

Answer 1: I do not know how to do this master discovery. Would it be in the POST of the AP?

Answer 2: I have 324 AP's of the same model and firmware installed and running on the network.

Answer 3: Yes, the equipment has licenses for installing new APs.

Answer 4: There is basic connectivity yes, because the AP gets the IP via DHCP and in the POST it is possible to ping the controller.

The AP will discover the controller via one of the following methods:

http://community.arubanetworks.com/t5/tkb/articleprintpage/tkb-id/ControllerBasedWLANs/article-id/1933

Do you see anything in the controllers logs?

#show log all | include XXXX (where XXX is the MAC of the AP)

Also if you can provide the full console output of when the AP is booting up :)

here the full console output when AP is booting up:

APBoot 1.0.8.3 (build 20343)
Built: 2008-12-27 at 17:03:46

Model: AP-12x
CPU: OCTEON CN50XX-SCP revision: 1
Clock: 500 MHz, DDR clock: 333 MHz (666 Mhz data rate)
Power: POE
POST1: passed
POST2: passed
DRAM: 64 MB
Flash: 16 MB
Clear: done
BIST: passed
PCI: PCI 32-bit; scanning bus 0 ...
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
03 00 160c ff1d 00000 01 80000000 00000000 00000000 00000000
04 00 168c ff1d 00002 01 80010000 00000000 00000000 00000000
Net: en0, en1
Radio: ar9160#0

Hit <Enter> to stop autoboot: 0
Checking image @ 0xbed00000
Invalid image format version: 0xffffffff
Checking image @ 0xbf500000
Invalid image format version: 0xffffffff
en0: Down 1Gbs Half duplex, (port 1)
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
en1: Up 1Gbs Full duplex, (port 0)
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
DHCP IP address: 10.46.14.160
DHCP subnet mask: 255.255.248.0
DHCP def gateway: 10.46.8.185
DHCP DNS server: 10.46.8.85
DHCP DNS domain: inca.local
ADP multicast 1
Controller address: 10.46.8.177
Using en1 device
TFTP from server 10.46.8.177; our IP address is 10.46.14.160
Filename 'mips64.ari'.
Load address: 0x1600000
Loading: #################################################################
################
done
Bytes transferred = 5269788 (50691c hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Automatic boot of image at addr 0x01600000 ...
ELF file is 64 bit
Allocated memory for ELF segment: addr: 0xe00000, size 0x4eeb00
Loading .MIPS.options @ 0x80e00000 (0xa0 bytes)
Loading .text @ 0x80e000a0 (0x4eea18 bytes)
Loading .data @ 0x812eeac0 (0x20 bytes)
Clearing .bss @ 0x812eeae0 (0x20 bytes)
## Loading OS kernel with entry point: 0x80e000a0 ...
Bootloader: Done loading app on coremask: 0x1
Uncompressing...

Aruba Networks
ArubaOS Version 6.4.3.7 (build 53990 / label #53990)
Built by p4build@naxos on 2016-02-27 at 12:15:56 PST (gcc version 4.3.3)
CVMSEG size: 2 cache lines (256 bytes)
Setting flash physical map for 16MB flash at 0x1ec00000
Determined physical RAM map:
Primary instruction cache 32kB, virtually tagged, 4 way, 64 sets, linesize 128 bytes.
Primary data cache 16kB, 64-way, 2 sets, linesize 128 bytes.
Using 500.000 MHz high precision timer. cycles_per_jiffy=1000000
Memory: 54272k/65536k available (2159k kernel code, 11208k reserved, 1004k data, 4264k init, 0k highmem)
Calibrating delay using timer specific routine.. 1000.30 BogoMIPS (lpj=1000309)
available.
Checking for the multiply/shift bug... no.
Checking for the daddi bug... no.
Checking for the daddiu bug... no.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=23035904
LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ................................................................................................................................................................................................................................................................................................................................................................
PCI Status: PCI 32-bit
slot 3, pin 1, dev_num 3, irq A
PCI dev 3.0 slot 3 pin 1: 160c:ff1d using irq 44
slot 4, pin 1, dev_num 4, irq B
PCI dev 4.0 slot 4 pin 1: 168c:ff1d using irq 45
/proc/octeon_perf: Octeon performace counter interface loaded
hw_random hardware driver 1.0.0 loaded
wdt: registered with refresh
Enabling Watchdog
isa bounce pool size: 16 pages
physmap flash device: 1000000 at 1ec00000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
phys_mapped_flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
Parsing the partition info
i2c /dev entries driver
i2c-palomino: using default base 0x8001070000000000
: Found DS1374 on octeon twsi
AD7416 driver probing for devices on Palomino TPM0
.AD7416 driver probing for devices on octeon twsi
.FOUND AD7416 at address: 48
Found AD7416 on bus octeon twsi.
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
PCI ERROR[DPERR]: Data parity error detected by PCX core

Starting HW SHA1 KAT ...Completed HW SHA1 KAT
Starting HW HMAC-SHA1 KAT ...Completed HW HMAC-SHA1 KAT
Starting HW DES KAT ... Completed HW TRIPLE DES KAT
Starting HW AES KAT ... Completed HW AES KAT

Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT

AP-type has_ble_support: .

Domain Name: arubanetworks.com
No panic info available
cavium_ethernet: module license 'Proprietary' taints kernel.
Octeon ethernet driver version: 1.5.0, build 187 Feb 27 2016 12:15:31
Interface 0 is RGMII
eth1: 1Gbs Full duplex, port 0, queue 0
Ethernet port 1 mode: active-standbyEthernet Channel Bonding Driver: v3.0.1 (January 9, 2006)

ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth0: link is not ready
bonding: bond0: enslaving eth0 as a backup interface with a down link.
ADDRCONF(NETDEV_UP): eth1: link is not ready
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 24, num_radios 2 (jiffies 2963)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 16
radio 1: band 0 ant 0 max_ssid 16
ethernet_device_event: dev eth0 is up
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
Starting watchdog process...
Getting an IP address...
10.46.14.160 255.255.248.0 10.46.8.185
Running ADP...Done. Master is 10.46.8.177
ath_hal: 0.9.17.1 (AR5416, REGOPS_FUNC, PRIVATE_DIAG, WRITE_EEPROM, 11D)
ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
ath_rate_atheros: Aruba Networks Rate Control Algorithm
ath_dfs: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_attach: scn a800000000620400 sc a800000003a40000 ah a800000003140000
wifi0: Base BSSID 6c:f3:7f:f3:ff:70, 16 available BSSID(s)
eth0 address=6c:f3:7f:c7:3f:f6
br0 address=6c:f3:7f:c7:3f:f6
wifi0: AP type AP-125, radio 0, max_bssids 16
wifi0: Atheros 9160: mem=0x11b00f0010000, irq=45 hw_base=0x90011b00f0010000
ath_ahb: 0.9.4.5 (Atheros/multi-bss)
ath_ahb: No devices found, driver not installed.

Starting FIPS KAT ... Completed FIPS KAT

shutting down watchdog process (nanny will restart it)...

<<<<< Welcome to the Access Point >>>>>

~ #

Here the output when i enter with command #Show log all | include 6c:f3:7f:c7:3f:f6

Nov 23 09:25:21 nanny[971]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 09:25:21 sapd[1030]: <311020> <ERRS> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 sapd| An internal system error has occurred at file sapd_sysctl.c function sapd_sysctl_write_param line 111 error Error opening /proc/sys/dev/wifi1/reg_info : No such file or directory.
Nov 23 10:31:31 nanny[747]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 10:35:52 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 11:05:24 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 11:10:52 nanny[747]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 11:14:31 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 11:20:14 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 11:29:18 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 11:43:01 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.
Nov 23 12:26:38 sapd[803]: <311002> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 sapd| Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=913 dest=10.46.8.177 tries=10 seq=0
Nov 23 12:27:48 nanny[747]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:43:51 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=913 dest=10.46.8.177 tries=10 seq=0
Nov 23 13:11:27 sapd[806]: <311002> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 sapd| Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=913 dest=10.46.8.177 tries=10 seq=0
Nov 23 13:12:37 nanny[747]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:43:54 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=913 dest=10.46.8.177 tries=10 seq=0
Nov 23 13:56:16 sapd[806]: <311002> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 sapd| Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=913 dest=10.46.8.177 tries=10 seq=0
Nov 23 13:57:26 nanny[747]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:43:54 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=913 dest=10.46.8.177 tries=10 seq=0
Nov 23 14:28:14 nanny[744]: <303022> <WARN> |AP 6c:f3:7f:c7:3f:f6@10.46.14.160 nanny| Reboot Reason: No reboot message found.

Plug it into ethernet 0, instead.

the same thing happens. there was no change of scenery.

Make sure that there is no LMS-IP in the AP system profile in the default ap-group

the ap is borked - it's failing to save its image, and its showing a h/w error. Don't know if AP125 can still be RMAed or not, but that's your next step (or bin it).

PCI ERROR[DPERR]: Data parity error detected by PCX core

In this case, is there any solution?

Do you have a support contract in place, the faulty AP maybe eligible for an RMA as the AP125 is supported until 01-Aug-18

---

@Leonardo52 wrote:

In this case, is there any solution?

---

there is no solution, the hardware has a problem. RMA it if you have a support contract, else bin it.