Controllerless Networks

I found a similar question here, but it did not resolve my problem.  I'm powering my 225 via POE+, power light is blinking green (roughly 1s intervals) which means "powering up", enet0 is rapid blinking as it is having activity, but the rest of the lights (namely 5ghz and 2.4ghz) are off. I remember reading in the thread someone else posted of a similar problem that it took him 45 minutes before it came up, I think I've had it for well over that.  Instant SSID is still not showing up.  Aside from a hardware fault, anything else I can look at? I will be trying to console in shortly, but I do not have the proper cable for it.  I set up in DHCP for it to be given an ip, and it is getting it and it pings, but I cannot telnet to it, or maybe I am doing it wrong. Is there another address I need to go to, or a different port I should be using in putty? Or do I just have to be patient (waited a couple of hours)?

Try to ssh instead.  Can you get to the gui via https?

If it got dhcp and the AP is out of the box(i mean new) then you should be able to see the instant SSID  and you should see 5ghz and 2.4ghz leds blinking 

Can you try consoling it? and show the output? The cisco console cable work just fine....

Cheers

Carlos

OK I apologize for the delay...I consoled in right now.  This is what I get in conosle:

APBoot 1.4.0.6 (build 38177)
Built: 2013-04-25 at 22:52:20

Model: AP-22x
CPU0: P1020E, Version: 1.1, (0x80ec0011)
Core: E500, Version: 5.1, (0x80212051)
Clock:
CPU0: 800 MHz
CPU1: 800 MHz
CCB: 400 MHz
DDR: 333.333 MHz (666.667 MT/s data rate) (Asynchronous)
LBC: 25 MHz
L1: D-cache 32KB enabled
I-cache 32KB enabled
I2C: ready
DRAM: Configuring DDR for 666.667 MT/s data rate
DDR: 512 MB (DDR3, 32-bit, CL=5, ECC off)
POST1: memory passed
Flash: 32 MB
L2: 256 KB enabled
Power: DC
PCIe1: RC, link up, x1
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 43a2 00002 03 80000004 00000000 80200004 00000000
PCIe2: RC, link up, x1
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 43a1 00002 03 a0000004 00000000 a0200004 00000000
Net: eth0, eth1
Radio: bcm43460#0, bcm43460#1

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

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.

Aruba Networks
ArubaOS Version 6.3.0.0 (build 37051 / label #37051)
Built by p4build@cyprus on 2013-02-04 at 11:16:55 PST (gcc version 4.5.1)

Memory: 510684k/524288k available (8020k kernel code, 13604k reserved, 532k data
, 352k bss, 4684k init)
Processor 1 found.
Brought up 2 CPUs
PCI: Probing PCI hardware
pci 0000:00:00.0: PCI bridge to [bus 01-ff]
pci 0001:02:00.0: PCI bridge to [bus 03-ff]
pci 0000:00:00.0: enabling device (0106 -> 0107)
pci 0001:02:00.0: enabling device (0106 -> 0107)
ee000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
Enabling watchdog on CPU 1
Enabling watchdog on CPU 0

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: arubanetworks.com
No panic info available
Ethernet port 1 mode: active-standby
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): bond0: 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 66, num_radios 2 (jiffies 3010)
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
ASAP Slowpath initialized
Starting watchdog process...
Getting an IP address...
PHY: eth0 (mdio@ffe24000:00) - Link is Up - 1000/Full
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: first active interface up!
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
192.168.1.149 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.
Restarting system.

As far as I can see, it all looks good up until the Running ADP, it is trying to find the master controller, can't then reboots...from my understanding, being the first AP to install in Instant mode, it should allow me to just connect to the SSID to set it up and then subsequent APs will connect to this one as the master. Am I mistaken?

Can you try to reset the AP using paperclip?  See the install guide for where that is located, and how to do it.

Can you confirm that this is an InstantAP ( IAP-225 )?  Take a look at the back of the AP and look for a small white sticker.  If it states " AP-225 " then it is a Campus AP and requires an external controller.

It'sAP-225. I was under the impression that they all came with the Instant setup capability.  I found the following response in anothre thread:

          It is running ADP to look for controller. Did you try to use factory_reset command? If it is not working,           reboot the AP and break the boot  process. Start TFTP and proceed the following command to put                 instant image:

          #upgrade os <tftp_server_ip>:<Instant_image_name>

          For example: #upgrade os 172.16.0.101: ArubaInstant_Orion_6.1.3.1-3.0.0.2_34479

          And reboot the AP after the process, it should be start with the instant image.

Will something like this work for me? Is the limitation hardware or software related? 

You cannot convert an AP-225 to an IAP-225.

For more info see this thread: http://community.arubanetworks.com/t5/Aruba-Instant-Cloud-Wi-Fi/Sticky-Can-I-convert-a-Campus-AP-to-an-InstantAP-IAP/td-p/142481

So, so sad.  Got a great deal for it. Aruba's page the 225s does not make it clear that IAP and AP are different. It states both methods of management for one page.  I'm guessing from looking at the console info, that the IAPs have more memory to house the entire OS, whereas the AP models don't and require the controller, thus why everywhere I read IAP can be run as AP, but APs cannot be run as IAPs. Sucks. Time to sell it off.