AP541N returns to default config

[John Kellen]

Hello,

one of my ap541n access points behaves strangly.

It returns out of the blue to the default config.

This is what the log tells me:

Oct 3 05:36:10	err	mDNSResponder	mDNSPlatformRawTime went backwards by 2138801570 ticks;  setting correction factor to 862212335
Dec 31 16:00:26	info	syslog	managed_ap.c:399:map_init_sub_components - Created the  MAP Switch Comm Control Block
Dec 31 16:00:26	info	syslog	managed_ap.c:1518:map_vpd_init - Done parsing VPD. Size =  0
Dec 31 16:00:24	info	syslog	managed_ap.c:1486:map_vpd_init - Default Configuration is  applied to the running config
Dec 31 16:00:21	notice	mini_httpd-ssl[411]	mini_httpd/1.19 19dec2003 starting on AP541N-A-K9, port  80
Dec 31 16:00:21	warn	mini_httpd-ssl[411]	started as root without requesting chroot(), warning only
Dec 31 16:00:20	notice	mini_httpd-ssl[412]	mini_httpd/1.19 19dec2003 starting on AP541N-A-K9, port  443
Dec 31 16:00:20	warn	mini_httpd-ssl[412]	started as root without requesting chroot(), warning only

Any idea what can cause this issue?

I have to add that once rebooted into default config, the webinterface responds really slow.

John

[John Kellen]

argh, whatever I do... it keeps rebooting into default config.

I guess this is a harware issue.

J

[John Kellen]

Hardware issue is ruled out. I replaced the access point with another one.

Same behaviour.

I get the idea that the problem starts when joining the cluster.

[John Kellen]

For anyone who experiences the same problem => CHECK THE MAX PoE OUTPUT OF PoE SWITCH!!

When you are on the limit of the switch PoE power output you may see that the switch seems to receive enough voltage becaus it starts when plugin in the utp cable. well, 7.2V is not the required 8V!! T

That triggers the configuration reset on the access point.

John