09-29-2011 11:42 AM
Frequently, it's the "Module WMS is busy. Please try later" error, but I would be curious what other reasons are seen when people are unable to view or write their configuration? If there aren't any APs on the master (which is what we've had recommended to us) and there aren't any critical processes on the master controller ... then *NOTHING* should prevent you from ever writing your configuration as you could theoretically turn the master off without impacting service. And, if you could do *THAT*, you should be able to replace the config that it reboots with ... no??
I'm not sure what to do in this case, but it seems like there should be a way to possibly "/force" a save ... or it would seem like management of the wireless approximates what you'd get from a purchasing a turnkey system.
09-29-2011 12:02 PM
10-04-2011 07:18 AM
We're also seeing numerous instances of not being able to do a write mem due to "Module WMS is busy." We have five locals (M3s), with 3 in one of our cores, and the other 2 in our other core (plus a backup M3). We have about 2400 APs (roughly 2/3rds are AP-125s and most of the rest are AP-61s).