For about half a year now, I've had (2) IAPs in a clsuter running stably in a multi-family home. Previously, I had broadcast filtering set to disabled. Wanting to take advantage of best practices, I enabled broadcast filtering and turned on AirGroup. The cluster was running smoothly for the first day or so until I ran into problems.
The cluster is completely unstable in this configuration when I'm running the master controller on the IAP115. Every few hours, CPU usage spikes to 100% and stays there causing pings and packet loss everywhere. This persists until it's reboot.
If I move the master controller from the IAP115 to the 225, I see much more stability. Though occasionally stability will fall off the cliff (albeit without the CPU spikes I was seeing on the 115) and the cluster again needs to be reboot.
After opening a case with TAC, they advised that I upgrade to yesterday's firmware (6.4.2.3-4.1.1.2_48114). So far the cluster has been stable on the 225 (I haven't tried the 115 yet) but the newest firmware presents a huge bug:
112117 Symptom: When the 80 MHz support is enabled on an IAP, ARM chooses only 36E as a valid
channel.
Scenario: This issue occurrs when ARM is enabled on an IAP to allocate 80 MHz channels. This issue
is observed in the IAP-22x and IAP-27x devices running 6.4.2.3-4.1.1.2 release.
Woraround: None
It seems I'm caught between an unstable cluster and limited 80Mhz channel availability.
Can anyone from Aruba shed some light on this or when I might expect to see a fix? Does anyone have any other suggestions for this type of setup?
This doesn't even address the fact that I would like to run the cluster on the IAP115 so that I can test reboots/configuration changes safely on the 225. I feel like the firmware has gone from bad to worse (still waiting on mesh support).
#AP225