09-02-2010 01:46 PM
With the global level settings, I can't have the same profiles and groups with different parameters which are needed for different network designs. If I import an AOS config from a controller in Group A, I can potentially change the configuration of a controller in Group B even though I may not have access to that controller/folder if my ap groups or profiles are named the same. For a large, global, enterprise network with many users that only have access to specific folders, I don't want users with access to 1 folder being able to modify a configuration for a device in another folder. This is a problem.
I realize in 7.1 there are device level overrides, but that potentially adds quite a bit of overhead and it doesn't prohibit one user from changing a device he doesn't have access to.
I would REALLY like to see a group level only option for AOS configurations. Otherwise, I'm going to have a tough time putting AOS controllers into managed mode w/o worrying one user will mess up another (even if only accidentally). I want AMP to manage my AOS devices.
Would others be interested in Group level AOS option for config settings instead of the global level? I'm lobbying for support on this.
02-22-2011 12:57 PM
03-01-2011 08:17 AM
Otherwise, the global Aruba Configuration system gives you something similar to the old Global Groups feature.
04-19-2011 11:27 AM
For example, in most enterprises, there exists a particular SSID that is everywhere. This would fit well into the MC and kept consistent across all groups. However, some radio characteristics, IDS policies, LMS IP addressing, etc., would fit better on a per-AMP group basis.
Right now, we have to choose. I'd prefer to both have and eat the cake.
Ryan Holland, ACDX #1 ACMX #1
The Ohio State University