WNDAP350 significant problems

I have 5 of these on various network segments over a large geographical area. All are using different wiring, different network switches, nothing in common with any of them except one thing. All are experiencing exactly the same problem.

Log excerpt

Mar 21 11:41:51 hostapd: Network Integrality: Ping Failed

Mar 21 11:41:51 hostapd: Network Integrality: Host: 10.110.255.254 is down.Bringing down all the vaps

Mar 21 11:41:51 kernel: brtrunk: port 2(wifi0vap0) entering disabled state

Mar 21 11:41:51 hostapd: wifi0vap0: STA 00:1b:63:cc:f5:40 IEEE 802.11: disassociated

Mar 21 11:41:51 hostapd: wifi0vap0: STA 00:26:4a:c1:51:26 IEEE 802.11: disassociated

Here is what I've learned:

When there are no associations at all (over a weekend for example) there are no problems; pings are always successful.

After there are a couple (two or so) associations then the above occurs maybe about once every 4 hours. You start getting more associations then the “Ping Failed” occurs more frequently. On one where there are about 30 associations the failure occurs about every 20 minutes, sometimes more frequently.

I am aware that these 350s ping their respective default gateways. Examination of the router's respective logs show the routers are working flawlessly. Indeed, everyone “wired” on the various network segments are not having any problems. Each 350 has it's own Gig/sec connection. Measured network traffic is rarely over 3% of available capacity.

So, in the 350's firmware, is it waiting a shorter and shorter amount of time for a ping return as the number of associations increase? Therefore, it is timing out waiting for the return when if it would wait just a little longer it would be satisfied?

I've got to solve this problem before I can deploy anymore 350s. I'm not replacing anymore WAP54G's which are working just fine.

Thanks for any help here.

Bob

Forum Discussion

WNDAP350's are constantly rebooting