Wireless Access

So I am trying to set up a new 93H on my network. I have a 7210 controller, and Aruba mobility switches. I have appropriate licensing to add more APs. As well, this would be around our 50th or so AP-93H. 

When booting the AP I see the below details. It doesn't seem to recognize the cable (powering it via PoE) as a link. I would guess this has to do with the invalid image error I receive. Is there anything I can do to solve this or would this be resolved by RMA?

APBoot 1.3.9.7 (build 37301)
Built: 2013-02-20 at 21:26:34

Model: AP-9x
CPU:   AR7242 revision: 1
Clock: 390 MHz, DDR rate: 390 MHz, Bus clock: 195 MHz
DRAM:  64 MB
POST1: 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:  0
Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0x0
eth0 down
DHCP broadcast 1
eth0 down
DHCP broadcast 2
eth0 down
DHCP broadcast 3
eth0 down
DHCP broadcast 4
eth0 down
DHCP broadcast 5
eth0 down

Retry count exceeded; starting again

Yes. 

I can also plug in a laptop and I recieve a DHCP address.

Is anything plugged into the other ethernet ports?  We found that can cause boot problems.  Couldn't hurt to try a different port on a different model of switch, just to quickly eliminate a lot of variables.

Alright so further testing. It is definitely the AP.

So I tried the AP in another switch. Same store, it powers on and fails to recieve DHCP.

However, I have 'borrowed' a work AP and plugged it in to my test port at my desk (the original port) and can confirm that it works.

So I guess my quesiton becomes, is there a way to flash these APs? I would assume based on the message that the image is the problem. 

hi ereader22

based on your tests, the enet port may be damaged. Connect AP to known working port and interrupt the boot process from the console and try the following (and capture it, since this will probably end up being in the RMA ticket, and someone will ask for it)

apboot>  dhcp

... wait...

does it eventually get an IP address? if so, it can be fixed.

If not, rule out DHCP - again since you will likely be asked for it in the RMA, so easier to get all info just once:

apboot> setenv ipaddr 1.2.3.4

apboot> setenv netmask 255.255.255.0

apboot> setenv gatewayip  1.2.3.254

apboot> ping 1.2.3.100

where: 1.2.3.4 is the AP ip address, assumes /24, def gw not used but configure it anyhow and 1.2.3.100 is controller or any other reachable host.

If the above two tests fail, the enet port is likely damaged and you can RMA it under LLW terms and conditions unless you have a better support contract on it.

regards

-jeff

Thank you, I will test this out. But I suspect it will indeed need to be RMA'd. It does not receive DHCP in a known working port. 

What is the process for RMA? Do I contact support for that, or do I go through my reseller? 

ereader22 wrote:

Thank you, I will test this out. But I suspect it will indeed need to be RMA'd. It does not receive DHCP in a known working port. 

[-jeff] yep, I agree with you - quite literally the only reason I mention to run through it one more time is so that you don't get any back and forward when you log the RMA. If you answer all the questions right off the bat (tested known working ap, tested static ip, still not working etc.) the RMA will proceed quickly.

ereader22 wrote:

What is the process for RMA? Do I contact support for that, or do I go through my reseller? 

[-jeff] if you plan to claim limited life time warranty (LLW, i.e. return to factory first) or Arubacare (advance shipment) you can claim it yourself, but if the part has Partnercare then you would need to get it back to the reseller/distributor.

Perhaps the easiest thing is to just send an email to support@arubanetworks.com, state the problem, testing done and the AP serial number; this will get the ball will get rolling and if you need to work via reseller/disty they will let you know.

regards

-jeff

i have the same problem 

but when i'm connected to normal port i get IP

but when i conected to the power injector replys 

Retry count exceeded; starting again
eth0 down
DHCP broadcast 1
eth0 down
DHCP broadcast 2
eth0 down
DHCP broadcast 3
eth0 down
DHCP broadcast 4
eth0 down
DHCP broadcast 5
eth0 down

apboot> osinfo
Partition 0 does not contain a valid OS image

Partition 1 does not contain a valid OS image

From the details provided, what you're experiencing is a different issue and needs to be troubleshot as a physical connectivity issue. Since it is not related to the original thread, please start a new thread to avoid confusion with the two issues.