At times i am losing one of my teen APs and 30 minutes later it will be ok, but
in this days this problem happens more and more

Question

I received the follwing logs:

Mar 20 20:11:45 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO11@8c:0c:90:33:8b:10] heartbeats lost

Mar 20 19:27:12 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO5@c0:8a:de:35:df:50] detects interference on radio [11g/n] and switches from channel [11] to channel [5].

Mar 20 21:46:48 SOLID-WIFI syslog: eventd_to_syslog():AP[8c:0c:90:33:d4:90] is online.

Mar 20 21:46:48 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO10@8c:0c:90:33:d4:90] joins with uptime [186937] s and last disconnected reason [Configuration Message Broken]

Mar 20 21:46:22 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO10@8c:0c:90:33:d4:90] heartbeats lost

Mar 20 21:46:14 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO10@8c:0c:90:33:d4:90] detects interference on radio [11g/n] and switches from channel [1] to channel [11].

Mar 20 21:37:16 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO5@c0:8a:de:35:df:50] detects interference on radio [11g/n] and switches from channel [5] to channel [11].

Mar 20 21:37:16 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO6@8c:0c:90:34:d5:20] detects interference on radio [11g/n] and switches from channel [11] to channel [4].

Mar 20 20:57:15 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO8@8c:0c:90:33:d3:e0] detects interference on radio [11g/n] and switches from channel [1] to channel [9].

Mar 20 20:31:48 SOLID-WIFI syslog: eventd_to_syslog():Lost contact with AP[AP_PISO11@8c:0c:90:33:8b:10]

Mar 20 20:27:14 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO4@8c:0c:90:34:d5:a0] detects interference on radio [11g/n] and switches from channel [11] to channel [4].

Mar 20 20:17:14 SOLID-WIFI syslog: eventd_to_syslog():AP[AP_PISO6@8c:0c:90:34:d5:20] detects interference on radio [11g/n] and switches from channel [4] to channel [11].

keith_redfield · Answer

No, I don't think an upgrade will do anything*. From your further description, the issue is either specific to that AP or the ethernet segment it is on. When you can plan some downtime, swapping another AP in it's place should tell you which is the problem (if the new AP works..it's the other AP). (Pick an AP from a less critical location if you can, so that if you do end up having to RMA the unit it won't be so painful)

*There is one situation where very high PHY errors can cause the AP to re-boot. This would suggest a lot of noise in the area around that AP.  More recent firmware such as 9.5.3 handles this better.

Further diagnosis will probably require that you open a support case, so that's my best advise..

unknown · Answer

Hi Keith, and fist thanks for your help and time.

About the isssue:

What version of ZoneFlex software are you running? .5.1.0 build 50

What model of AP is it? All APs are 7363

Have you tried to factory reset that AP? If not, try that.   no, it is in production environmenet, i will do it like a last solution only

Is the AP directly connected to the ZoneDirector, or is it going through a routed network? All APs are in each floor of the building, connected directly to the floor switch. All floor switch are connected to the data center switch so it is like all APs and Zone Director are connected to the same switch

Please your help, maybe i should upgrade my zd to the last version??

keith_redfield · Answer

Hi Pablo,

What version of ZoneFlex software are you running?

What model of AP is it?

Have you tried to factory reset that AP? If not, try that.

Is the AP directly connected to the ZoneDirector, or is it going through a routed network?

It's possible the AP is just failing, so if it's critical to your network I would recommend you open a support case.