Hi,
I have 2 WAP 361 devices running in a cluster and powered via PoE by a CISCO SG250-08HT switch. The dominant device boots at 6:30am. The non-dominant one boots at 7:30am. Both are set up correctly to obtain their system time from a set of reachable NTP servers. Althoung the non-dominant device retrieves correct time from the NTP server after boot, the time setting is damaged shortly afterwards. Here are relevant syslog entries:
2021-01-02 22:11:23 wap-schlafzimmer daemon clusterd AP with MAC Address "70:F3:5A:35:74:E0" and priority "99" is elected as Dominant AP
2021-01-02 22:11:23 wap-schlafzimmer daemon dman The AP startup configuration was updated successfully.
2021-01-03 07:32:25 wap-schlafzimmer daemon clusterd Applying received configuration
2021-01-03 07:32:25 wap-schlafzimmer daemon clusterd [proposed_channels] their(192.168.0.6) key is better than our(192.168.0.5) key, fetching their data
2021-01-03 07:32:25 wap-schlafzimmer daemon clusterd [shared_config] their(192.168.0.6) key is better than our(192.168.0.5) key, fetching their data
2021-01-03 07:31:57 wap-schlafzimmer kern sntp sntp set_time: sync system time to ntp server(194.25.134.196) time Sun Jan 3 07:31:57 2021
Wap-schlafzimmer is the non-dominant node in the cluster. After reboot, it receives the correct time from the NTP server. However, after updating the AP startup configuration based on the received cluster configuration from the dominant node (my interpretaiton of syslog entries), the system time is set to a completely wrong value, which can be recognized on the following syslog entries. The system time of the dominant node was correct at that time.
I run both devices with the latest firmware (1.1.2.4) and the cluster is actually working fine.
I am an IT expert and enthusiastic private user without service contract, therefore I can not open a ticket regarding this issue. However, I would gladly help you to improve the quality of the WAP361 product, which I really like to use.
Regards,
Miran
