- The configuration is not really useful, because it says how a network *should* perform, and not how it is performing.
- The tech-support is the most useful, but it is (1) too hard to sanitize (2) sanitizing removes crucial information needed to get to the bottom of your issue
- There are many things that could cause disconnects and multicast key rotation is disabled by default, so that is normally not the issue
- If the customer had the problem before the upgrade, then the ArubaOS code is not to blame
Here are the reasons for disconnects, in order:
- Too much AP density, which creates alot of co-channel interference (power needs to be lowered on access points)
- Using the wrong channel-bonding configuration (40 and 80 mhz channel bonding typically should not be used in high density areas)
- Not turning on Broadcast filtering (broadcasts are useless, but they cause congestion and disconnects).
- Broadcasting too many SSIDs (broadcasting SSIDs increases contention and co-channel interference. More than 4 SSIDs is too much)
- If the problem occurs with only specific clients, those clients might need to have their wireless drivers updated.
You should open a TAC case, if you have not already because it can be a single complicated issue, or a combination of complicated issues. Key rotation is normally not the culprit.