Wireless Access

Hello,

For some reason I can not provision a couple of new AP 93s that we just purchased.  We have an Aruba 2400 running 5.0.3.1 and I have other AP 93s that I am able to provision.  The new APs are working, I just can't change the name or the location.  They do reboot, but they never come up with the new name/location.  Any ideas what I'm missing?  I've tried plugging these APs directly into the 2400 and I notice no errors in AP debugging.  I haven't connected to AP console yet (I left my laptop at home).  Any help would be appreciated.

Thanks!

How many access points do you have in total?

48 access points up (46 if you remove the two new ones) 5 APs listed as down.

I would type "show log system 50" to see if there are any messages generated by those access points.  I would also type "show ap database to see if those access points have any flags that would indicate why they are not working.  From my memory, 48 access points is the limit for the 2400 platform.  Let's hope you don't have any other hidden devices that are connecting...

Ok.. now I see something interesting...

Dec 19 15:55:08 :399803:  <ERRS> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd|  An internal system error has occurred at file sapd_cfg.c function sapd_read_cached_info line 483 error apfc_read failed: Cache uninitialized.
Dec 19 15:55:08 :303022:  <WARN> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 nanny|  Reboot Reason: No reboot message found.
Dec 19 15:55:35 :311010:  <WARN> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd| AP could not boot from flash -- bad checksum
Dec 19 15:56:08 :311002:  <WARN> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd|  Rebooting: SAPD: Reboot after image upgrade
Dec 19 15:56:09 :303086:  <ERRS> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 19 15:57:10 :399803:  <ERRS> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd|  An internal system error has occurred at file sapd_cfg.c function sapd_read_cached_info line 483 error apfc_read failed: Cache uninitialized.
Dec 19 15:57:11 :303022:  <WARN> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 nanny|  Reboot Reason: No reboot message found.
Dec 19 16:05:52 :399803:  <ERRS> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_mesh_erase_domain_prof line 1776 error apfc_read failed: Cache uninitialized.
Dec 19 16:05:53 :311002:  <WARN> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd|  Rebooting: SAPD: Rebooting after provisioning
Dec 19 16:05:53 :303086:  <ERRS> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 19 16:06:32 :399803:  <ERRS> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 sapd|  An internal system error has occurred at file sapd_cfg.c function sapd_read_cached_info line 483 error apfc_read failed: Cache uninitialized.
Dec 19 16:06:33 :303022:  <WARN> |AP d8:c7:c8:cf:c5:c6@192.168.129.209 nanny|  Reboot Reason: No reboot message found.

Okay.  According to the Datasheet http://www.arubanetworks.com/pdf/products/DS_AP90Series.pdf the minimum code required is ArubaOS 5.0.4.1 for AP90 series access points.

OK... interesting... I have other 93s that I've provisioned, but I will try that, THANKS!!

A newer batch may have newer requirements...  You're not crazy ;)

Makes sense to me...  Oh, but I am crazy!  :smileyvery-happy:

I'm glad I didn't take that away from you...;)

See if your Aruba Sales Team can give you a nice deal on a shiny new 3000 series controller....

i think i have the same problem, can't provisioning my AP but on controller 3600. I'm using the power injector for the AP 93.

but i tried many times plug unplug the cable to injector, the AP still not shown on the controller (WEBGUI on AP Installation), also i check with command "show ap database" no one AP shown on the table.

The actually i want provisioning my AP with script, because i need provisioning 110 AP. But the problem i can't solved.

On the below information on my controller and AP

Aruba Operating System Software.
ArubaOS (MODEL: Aruba3600), Version 5.0.2.0
Website: http://www.arubanetworks.com
Copyright (c) 2002-2010, Aruba Networks, Inc.
Compiled on 2010-08-05 at 15:45:02 PDT (build 24926) by p4build

ROM: System Bootstrap, Version CPBoot 1.2.0.0 (build 20527)
Built: 2009-01-20 18:56:10
Built by: p4build@re_client_20527

show image version

----------------------------------
Partition : 0:0 (/dev/hda1) **Default boot**
Software Version : ArubaOS 5.0.2.0 (Digitally Signed - Production Build)
Build number : 24926
Label : 24926
Built on : Thu Aug 5 15:45:02 PDT 2010
----------------------------------
Partition : 0:1 (/dev/hda2)
Software Version : ArubaOS 5.0.2.0 (Digitally Signed - Production Build)
Build number : 24926
Label : 24926
Built on : Thu Aug 5 15:45:02 PDT 2010

==== AP 93 =====

APBoot 1.2.7.4 (build 32721)
Built: 2012-03-08 at 11:33:21

Model: AP-9x
CPU: AR7242 revision: 1
Clock: 390 MHz, DDR rate: 390 MHz, Bus clock: 195 MHz
DRAM: 64 MB
POST1: mem 0 mem 1 mem 2 mem 3 passed
Copy: ....    done
Flash: 16 MB
PCI: scanning bus 0 ...
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 002a 00002 01 10000004 00000000 00000000 00000000
Net: eth0
Radio: ar9280#0

Hit <Enter> to stop autoboot: 2  1  0
Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0x0
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP broadcast 2
DHCP broadcast 3
DHCP broadcast 4
DHCP broadcast 5

Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 172.16.0.249
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 172.16.0.253
DHCP DNS server: 0.0.0.0
DHCP DNS domain: aruba.com
Controller address: 172.16.0.254
Using eth0 device
TFTP from server 172.16.0.254; our IP address is 172.16.0.249
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: *####################################################
done
Bytes transferred = 3355916 (33350c hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Automatic boot of image at addr 0x02000000 ...
ELF file is 32 bit
Loading .text @ 0x80e00000 (3287048 bytes)
Clearing .bss @ 0x81122810 (16 bytes)
Loading .data @ 0x81122820 (32 bytes)
## Starting application at 0x80e00000 ...
Uncompressing..............................

Ëbø
Aruba Networks
ArubaOS Version 5.0.2.0 (build 24926 / label #24926)
Built by p4build@cyprus on 2010-08-05 at 15:21:46 PDT (gcc version 3.4.3)
CPU Rev: 1101
72x CPU
Cache parity protection disabled
Using 195.000 MHz high precision timer. cycles_per_jiffy=390000
Memory: 58624k/65536k available (1633k kernel code, 6848k reserved, 682k data, 2568k init, 0k highmem)
available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13542400
LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ...............................................................................................................................................................................................................
Returning IRQ 48
AR7240 GPIOC major 0
wdt: registered with refresh
Enabling Watchdog
Creating 1 MTD partitions on "ar7240-nor0":
0x00000000-0x01000000 : "flash"
i2c /dev entries driver
i2c-talisker: using default base 0x18040000

Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
Starting Kernel DES KAT ...Completed Kernel DES KAT
Starting Kernel AES KAT ...Completed Kernel AES KAT

Domain Name: aru banetworks.com
No panic info available
cat: /tmp/boardname: No such file or directory
[: Talisker: unknown operand
[: Muscat: unknown operand
[: Chuck: unknown operand
[: Delfresco: unknown operand
[: Palomino: unknown operand
[: Talisker: unknown operand
[: Scapa: unknown operand
[: Muscat: unknown operand
<6>AP xml model 43, num_radios 1 (jiffies 2708)
init_asap_mod: installation:0
radio 0: band 2 ant 0 max_ssid 8
asap_gre_init: ADDED GRE protocol c009ae10
setting gre0 as split child
USB not provisioned
Starting watchdog process...
[: closing paren expected
[: closing paren expected
Getting an IP address...
Kernel watchdog refresh ended.
ifconfig: br0: error fetching interface information: Device not found

[: closing paren expected
[: closing paren expected
ifconfig: br0: error fetching interface information: Device not found

[: closing paren expected
[: closing paren expected
ifconfig: br0: error fetching interface information: Device not found

any advice with my problem on the above.?

You need to upgrade to ArubOS 5.0.4.0 and above.

Hi guys..

need some help too..

I have aruba 3600 controller ---- > firmware 5.0.3.3

current AP i use - AP 125  and it working well

now I want to add new ap (AP 135 )

I do the privisioning, but controller can't found the new AP

1) Do I need to upgrade the Aruba3600 Firmware ?

2) After i upgrade, what happen for the current AP125, its that will functioning like usual ?

You need to upgrade to at least 6.1.1.0 http://www.arubanetworks.com/pdf/products/DS_AP130Series.pdf

The AP125s will work just fine with 6.1.1.0 and above.

---

@cjoseph wrote:

You need to upgrade to at least 6.1.1.0 http://www.arubanetworks.com/pdf/products/DS_AP130Series.pdf

 

The AP125s will work just fine with 6.1.1.0 and above.

 

---

Hi cjoseph..

1) can u give me a link for version 6.1.1.0 firmware or latest version..

2) Are there any guidelines for me to follow during the upgrading process ?

   my firmware

   Partition 0 : 5.3.3

   Partion 1   : 3.x.x

TQ.

You need a support account to download new software.

---

@cjoseph wrote:

You need a support account to download new software.

---

TQ cjoseph..

Hi cjoseph...

i already get the firmware...

i have 2 controller..

master & local..

which one i need to upgrade firmware first...

can u guide me, step to upgrade the firmware..

what i need to do 1st ?

Upgrade both, but do not reboot.  After they are upgraded, reboot both of them at the same time.

Hi cjoseph

AP135 have been recognized after I upgrade firmware (6.1.3.5)

but the controller cannot detect the new AP

how can I solve this prob ?

from the output it seems the AP can't reach its own network, have you manually configured IP information, is that all still correct, any reason for now using DHCP?

---

@blackdevilhollow wrote:

Hi cjoseph

 

 

AP135 have been recognized after I upgrade firmware (6.1.3.5)

but the controller cannot detect the new AP

 

 

how can I solve this prob ?

---

You have a static ip address configured.

I would stop the AP at the apboot> prompt and type "purge" then "save" and then "boot"