for me it sounds like a problem with the network cable.
What ranges do you have between switch and ap? I have sometimes this problems with bad network cables. Do you use POE or an powersupply?
What I see with bad cables, is that the switch start work via POE (lights blinking), but becomes no ethernet connection. When I changed the cables all worked fine.
Can you check the ap with an short cable connected direct to the switch? What network speed do you use 1GB 100MB?
I haven't seen a dead AP during the beta yet so this would be the first one. Could you please explain how the power led is blinking? Is it a periodic on/off?
I haven't seen a dead AP during the beta yet so this would be the first one. Could you please explain how the power led is blinking? Is it a periodic on/off?
I haven't seen a dead AP during the beta yet so this would be the first one. Could you please explain how the power led is blinking? Is it a periodic on/off?
Thanks. The AP50 is indeed broken, the bootloader cannot start the actual firmware. Not sure why, maybe a firmware update failed?
However, please send it back to Astaro for further analysis.
And could you please attach your wireless log files starting from the day the AP didn't come up anymore (or send them via mail to me: hschaa@astaro.com) here so that I can see if a firmware update caused this?
Thanks for the log. The last communication with the AP was indeed a firmware update:
2011:12:19-16:24:31 asgbeta83 awed[5716]: send msg: ip:'192.168.12.23', id:'A40002E2A6A1A0E', type:'6', length:'2395526'
[...]
2011:12:19-16:25:32 asgbeta83 awed[5716]: AP 'A40002E2A6A1A0E': timed out after 61 seconds
I can only imagine that the AP50 somehow lost its power supply (POE) during the firmware update and hence couldn't finish it and is now stuck with the incomplete firmware.
