OAW-AP205 still reboot

Also known as OmniAccess Instant AP
Post Reply
djamal
Member
Posts: 3
Joined: 04 May 2016 17:01

OAW-AP205 still reboot

Post by djamal »

hi team

I have 7 OAW-AP205 ,and want to install it without using any WLAN Controller or Switch. Please let me know how i'll install and configure these 7 IAPs independently (without using any WLAN Controller or Switch)?
the first AP 205 still reboot, after connecting AP in the network, AP is assigned a valide ip @, but i can not see the INSTANT and still reboot. please find below :

Hit <Enter> to stop autoboot: 0
Checking image @ 0x1e100000
Invalid image format version: 0xffffffff
Checking image @ 0x1ef00000
Copying image from 0x1ef00000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Uncompressing... done
[ 0.000000]
[ 0.000000] Aruba Networks
[ 0.000000] ArubaOS Version 6.4.1.0 (build 43850 / label #43850)
[ 0.000000] Built by p4build@cartman on 2014-05-20 at 23:07:58 PDT (gcc version 4.7.2)
[ 0.000000]
[ 0.000000] Flash variant: variant0
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 121168k/121168k available, 9904k reserved, 0K highmem
[ 0.052000] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 3.264000] PMU: registered new PMU device of type 0
[ 3.770000] pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
[ 3.772000] pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
[ 3.774000] pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
[ 4.276000] pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
[ 4.278000] pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
[ 4.280000] pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
[ 4.626000] i2c-springbank: using remapped base c9cc8060
[ 4.630000] mpcore_wdt mpcore_wdt: enabling watchdog.
[ 4.634000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address
[ 4.638000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)
[ 4.640000] Creating 1 MTD partitions on "spi1.0":
[ 4.642000] 0x000000000000-0x000002000000 : "qspi"
[ 4.646000]
[ 4.646000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[ 4.650000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[ 4.664000] Starting Kernel DES KAT ...Completed Kernel DES KAT
[ 4.668000] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 4.670000]
Domain Name: arubanetworks.com
No panic info available
[ 6.144000] AP xml model 81, num_radios 2 (jiffies 3072)
[ 6.146000] init_asap_mod: installation:0
[ 6.148000] radio 0: band 1 ant 0 max_ssid 16
[ 6.150000] radio 1: band 0 ant 0 max_ssid 16
Starting watchdog process...
Getting an IP address...
[ 8.544000] ADDRCONF(NETDEV_UP): bond0: link is not ready
[ 10.548000] bond0: link up (1000FD)
[ 10.550000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
192.168.1.15 255.255.255.0 192.168.1.1
Running ADP...cat: /tmp/master: No such file or directory
Done. Master is
killall: nanny: no process killed
killall: sapd: no process killed
Sending SIGKILL to all processes.
Please stand by while rebooting the system.
[ 86.158000] Restarting system.


APBoot 1.5.3.14 (build 45815)
Built: 2014-09-05 at 11:23:04

Model: AP-20x
CPU: BCM53011/15, revision A0
I2C: ready
SKU: 2
OTP: 0xeca01028
Clock:
CPU: 800 MHz
DDR: 533 MHz
AXI: 400 MHz
APB: 200 MHz
PER: 400 MHz
DRAM: 128 MB
POST1: memory passed
SF: Detected MX25L25635E with page size 4 kB, total 32 MB
Flash: 32 MB
PCIe0: RC, link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 4360 00002 03 08000004 00000000 00000000 00000000
PCIe1: RC, link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 4360 00002 03 40000004 00000000 00000000 00000000
Power: POE
Net: eth0
Radio: bcm43460#0, bcm43460#1




Bests regards
dartzen
Member
Posts: 40
Joined: 27 Dec 2010 13:07

Re: OAW-AP205 still reboot

Post by dartzen »

Hi,

from the output posted I would think that this AP is either not an IAP, but a normal one or has been flashed to become a campus AP. Since it can't find a master controller it reboots and tries again. You have to look on the backside of the AP. Does it say "IAP-205" or "AP-205"? If it is AP-205 it can not be used without a controller.
An IAP-205 can be converted to be used as a campus AP (with controller) but an AP-205 can never be used without a controller.

I hope this helps.
Best regards
Daniel
HUSSAINQCS
Member
Posts: 293
Joined: 21 Jan 2017 02:57

Re: OAW-AP205 still reboot

Post by HUSSAINQCS »

I have some problem in some specific floors AP

Its a hotel where uplinks from core to access is going for each floor

2,3,4, 5th floors AP's are getting IP but 6th floor AP's not getting IP


its showing in the console DHCP timeout but in the same port I connected my laptop indeed laptop is getting IP from the DHCP of the OAW-4550

Here I attached access switch logs for AP's in 4th floor which are getting IP and AP's in the 6th floor which are not getting IP

What could be the issue ??
You do not have the required permissions to view the files attached to this post.
silvio
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 1886
Joined: 01 Jul 2008 10:51
Location: Germany

Re: OAW-AP205 still reboot

Post by silvio »

did you use ip-helper at some switch? Or is the dhcp in same vlan.
With ip-helper you need to change the following:
ip helper forward delay 0

regards
Silvio
Post Reply

Return to “OmniAccess Wireless Access Points”