Trying to wrap my head around how Airwave Groups are utilized when Airwave is used in "Monitor Only" mode. Figured I'd reach out to the community before calling TAC.
I've read through the Airwave 7.7 Users Guide & have looked at the Practical AirWave Workshop presentation.
First off... Am I correct to assume that any AMP changes or reconfiguration (when Airwave is used in "Monitor Only" mode) of APs & their respective Groups / Folders WILL NOT reboot any APs?
Thus far, I believe that Groups are used to audit specific config settings of devices based on their Group designation. I'm not entirely sure this explains why there may be configuration mis-matches for items such as Aruba AP Group settings? Perhaps I need to look more at Templates...
So, one possibility of accounting for Config Mismatches might be to create as many groups as needed to account for all of the specific setting differences in an environment; which might turn out to be too time consuming in a complex environment.
We have about 11 groups at the moment; some aren't being used. Some of them are used to differentiate deployments (physically [i.e. different campuses] & logically [production, test, & beta]). There are a few others that aren't very useful, Aruba, ArubaAPs, & (the default) Access Points. I have yet to dig though comparisons to find out which groups are needed and which ones can be deleted.
What is the best practice regarding Airwave Group creation & association? Should I create individual groups for every different config setting? Should I just stick w/ some basics? Should I create different ones for different APs (105s vs 125s vs etc. etc.)?
Specifically, if we put all of our APs in either Aruba or ArubaAPs (or other groups) however we have APs on physically connected on devices that belong to other groups (such as beta) where should those APs be assigned? Currently, we're using a mix of these types of associations; physical campus group has both controllers & all APs on that campus assigned to that Airwave Group. However in the logical Beta group, most of the APs connected to the beta controllers are in the ArubaAPs group, yet a single (non-production) AP is assigned to the Beta Group.
Apologies, I know its confusing.
Could this be an example of where Templates should be used? If I define / configure & use a template while Airwave is in Monitor Only mode, what will this accomplish?
I'm gonna re-read the Users Guide & see if I can learn more about what Group configs can be specified / monitored & what role a template may play in helping simply groups.
Thanks,