Since Update9.409-9 AP30 allways goes offline / inactive

I have found a workaround...

I installed a UTM Version 9.217-3.1 on my ESXI-Host in a Virtual Machine und connected the AP30 to this UTM. 

The old UTM version have sent a Firmware to the AP30 and it works!

Then i have connected back my AP30 to the latest UTM 9.409 Version and the AP30 get's the latest Firmware.

Then the AP30 works a few days until today :(

The AP30 is now again offline und when i look at the AP30 Hardware self, the are no Lights etc on... The POE Injector works, then the LED is Green (not Orange)....

When i remove the LAN Cable from the AP30 and re connect ir again, the AP30 went online. Is only the question how long this works again ?

What can i do? - Is the no FIX???

Hi Xenon,

As I suggested in my DM's to you, the old AP models losses connection with the UTM which was first experienced with AP 50 in v9.407. This is a database error related to version numbering and as per the information I have, we are hopefully fixing it in our next release which is v9.410.

Thanks

Hi, Sachin Gurung

Ok Thank you!

so i must wait :(

But are you sure this is really a Database Problem? 

Because my AP30 is totally dark... No Blue Lights are on! 

But the PoE Injector LED is Green, so i Think it is not the PoE Injector!

Hi xenon2008,

i have updated my SG310 HA Cluster this night with 9.409-9. Have 3 AP30 running for my WLAN-Infrastructure.. no problems..

All 3 AP30 are running with the new update.

deutsch:

Denke mal das es sich bei deinem Problem nicht um ein allgemeines Problem mit den AP30 handelt, sonst wären meine wohl auch ausgestiegen.
Ich hoffe das Sophos hier einen fix für dich findet.

Hi,

deutsch:

wobei es sich hier laut sachingurung: ja nur um die alten bzw. die ersten AP30 handelt die von diesem ominösen Datenbank Error betroffen sein sollen... evtl. hast du schon neuere ;)

english:

but sachingurung means, that only the old (first) Ap30 are affected from this Database Error! The Newer one not...

Meine AP30 sind alle von 2012.. also auch schon alt... naja egal. Bin froh das die bei mir Laufen ;-)

hoffe die finden etwas das dir hilft..

Hello!

Since i few days i have installed the UTM Version 9.410-6 which should fix tis BUG.

But today the AP30 went offline again!

Any Solution?

Best Regards

Mark

EDIT:
Now my AP30 is broken :/

A restart does not help *cry*

I always have this Error in my Log-File:

2017:02:09-19:33:47 xenon2008 awed[4606]: [MASTER] new connection from 192.168.XX.XXX:58478
2017:02:09-19:33:47 xenon2008 awed[11893]: [A4000XXXXXXXXX] AP30 from 192.168.XX.XXX:58478 identified as A4000B7E35AD9F2
2017:02:09-19:33:47 xenon2008 awed[11893]: [A4000XXXXXXXXX] (Re-)loaded identity and/or configuration
2017:02:09-19:33:47 xenon2008 awed[11893]: [A4000XXXXXXXXX] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2016:12:23-13:58:05 192.168.XX.XXX aweclient[716]: aweclient.c (2516) No message received. Reconnecting.
2016:12:23-13:58:05 192.168.XX.XXX aweclient[716]: aweclient.c (2591) Failed to configure device.
2016:12:23-13:58:05 192.168.XX.XXX aweclient[716]: Closing log...
2016:12:23-13:58:05 192.168.XX.XXX syslog: - shutdown -
2016:12:23-13:58:05 192.168.XX.XXX syslog:
2016:12:23-13:58:05 192.168.XX.XXX syslog:

What can i do? I am really frustrated!

Mark

Hello!

Since i few days i have installed the UTM Version 9.410-6 which should fix tis BUG.

But today the AP30 went offline again!

Any Solution?

Best Regards

Mark

EDIT:
Now my AP30 is broken :/

A restart does not help *cry*

I always have this Error in my Log-File:

2017:02:09-19:33:47 xenon2008 awed[4606]: [MASTER] new connection from 192.168.XX.XXX:58478
2017:02:09-19:33:47 xenon2008 awed[11893]: [A4000XXXXXXXXX] AP30 from 192.168.XX.XXX:58478 identified as A4000B7E35AD9F2
2017:02:09-19:33:47 xenon2008 awed[11893]: [A4000XXXXXXXXX] (Re-)loaded identity and/or configuration
2017:02:09-19:33:47 xenon2008 awed[11893]: [A4000XXXXXXXXX] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2016:12:23-13:58:05 192.168.XX.XXX aweclient[716]: aweclient.c (2516) No message received. Reconnecting.
2016:12:23-13:58:05 192.168.XX.XXX aweclient[716]: aweclient.c (2591) Failed to configure device.
2016:12:23-13:58:05 192.168.XX.XXX aweclient[716]: Closing log...
2016:12:23-13:58:05 192.168.XX.XXX syslog: - shutdown -
2016:12:23-13:58:05 192.168.XX.XXX syslog:
2016:12:23-13:58:05 192.168.XX.XXX syslog:

What can i do? I am really frustrated!

Mark

Hi Mark,

try flash the bugfixed firmware 9.411-3. hope this wakes your ap30 up again.

Hello!

I deleted the AP30 rev2  a few times, and removed the PoE Adapter a few times..

Since that the Ap30 went online... Then i have selected the WLans and all "looks" good...

I'm curious how long this works again ...

Hi,

For the record, I have a problem with the same symptoms with a "new" AP30 v2 on UTM9.411-3.  The UTM is driving two AP's, both AP30's - one v1 (badged Astaro for the retro look! :)) and a newer v2 which was acquired recently.   The newer v2 appears to be dropping offline periodically.  Deleting the AP from UTM and then resetting the device seems to bring it back for a bit but then it goes again overnight.

The AP30 v1 has been and continues to be, as good as gold.

Cheers!

i have 2 AP30 v2 running smooth since installation in year 2012.

have not updated my cluster yet.. still on 9.409-9...

We also use AP30 rev.2 on 9.411 SW- and Appliance-Version, they all run fine.