10-22-2014 11:33 AM
I've been testing with Airwave's config audit report. Currently we are pointing all our APs master discovery to "aruba-master". The issue is that some APs have a combination of Master/Local IP address/es instead.
I'm trying to run a config audit report against all the current APs to see which APs don't have the settings that I want. The problem is that the report comes back with a lot of different settings, basically it's inconsistent on a per AP basis.
I've contacted Aruba TAC and they just kept telling me that in order to fix the mismatch config of the AP I need to import the current AP settings. I don't want to do this because I could be importing a current config that I don't want to be correct.
So, my question, is there a way to set a global config in Airwave to check against all the APs? That way it will flag any AP that does not have the global config that I set?
I've looked all over Airwave and do not see this setting.
10-22-2014 11:41 AM
1. So are you wanting a suggested best config to compare to?
2. Could you specifically correctly set one up and import that config?(If you answer to #1 is no)
10-22-2014 12:48 PM
Right, a base config on Airwave to compare to all APs.
According to TAC, each mismatched APs config need to be imported to resolve that mismatch. But that's useless since it could be importing a config not wanted from such AP.
If I import a good known AP, can I make that the default config that Airwave uses to check every other AP?
10-22-2014 01:11 PM
Sent from my iPhone
10-22-2014 01:17 PM
Hmm...I'm just trying to audit the config on the APs, not the controllers. If I'm getting this right, you are saying to find an AP per each folder that has the current config that I want. Import that config from that AP. Do this for every folder and I should have the config I want for all APs? Then I can run the report and get the appropriate info that I want? If so, this is way too much work and for doing this. I don't see why one template can't be created and added as a global template that all folders should match against.
10-22-2014 01:21 PM
Sent from my iPhone
10-22-2014 03:28 PM
Here's how I would do this:
create a new group
in the group -> move a single Aruba AP that has the config that you're looking for into the group
import that AP's config as the group's defaults
then temporarily move APs into that group and run report based on that group
and then afterwards move the APs back into their desired group
not ideal, but it's a workaround method to achieve what you're looking for.
It'd currently be a feature request to try to run an audit report of 1 group against another groups config.
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
10-22-2014 03:44 PM
We have 2,500+ APs, this would take all day.
I don't understand why Airwave is taking the config the AP first reports as the config to verify against. It should be an import global option per folder or group and it should be configurable.
What's the process of important an APs config as the default for a Group?
Currently we have all the APs under one group. We then have them in different folders within that group.