Wireless Access

Hello all, 

I have an A7210 running AOS8.6 in Standalone mode. We purchased another A7210 for redundancy, and have set up the redundant master with a VRRP and Config Sync. That seems to be working fine, however the config that is being synced to the backup controller is NOT the config that is on the master. 

When I first moved to AOS8, I made some config changes in the GUI with the explicit device selected (not the Mobility Controller folder). The device now has some things like AP Groups and ARM Profiles that exist at the device level, but not at the folder level. Everything that is at the "Mobility Controller" folder level is synced with the backup, but the stuff that was configured at the device level isn't. 

Is there a way to "unify" these configurations in standalone mode? Or to at least discard the configs at the device level and force them to inherit the folder configs only, and then rebuild the profiles at the folder level?

You could run a "show configuration effective detail" on the device level of the controller you want the config  from to then pipe out what configuration is applied at the device level its self, and then script it for placement at the top level. There isn't a way to force a sync up the hierarchy. All configuration is inherited by parent folders.

OK, so if I take stuff on that list that's applied at the local level and config it at the /mm node, will it overwrite the stuff at the local level? wouldn't the local config "win" over the hierarchy config? Is there a way to get rid of a config at a subordinate level?

Configuration will be inheriteted from folders above, unless it is configured at the lower level. You will have a local overide flag on the config that is applied at that level and not set form a level above. You could go through and remove overrides after the config is getting inherited from above.

Also just to be clear, it is also best practice not to change settings at the top level. You want to preserve default values, and start your configuration at a level down from there. For example, TOP > (start config here) Company > Campus > Building > etc...

Gotcha, thanks. Could you point me to instructions on how to remove the local override flag on the config once the inheritance is in place?

As far as not making config changes at the top level: That's my only option in standalone mode. I don't have, nor can I create afaik, config nodes. I only have: 

/
/mm
/mm/mynode

 If I look at the backup controller, pretty much everything (except interface config, hostname, ip, and other stuff you'd expect to be unique) is: "# inherited from [/mm]"

You would want to run the "show config effective detail" command, and parse out any config that shows it inherited it form its self at the device level and not anything higher. You would then remove that configuration at that level, and it will inherit the configuration form above.

Also if you have the opportunity, you could wipe out the controller, delete it from the hierarchy, and re-add it. Then it will match what you have from the configuration above with less work. Does that make sense?

Thanks Dustin, 

Understood. I'll move everything that seems to be missing up manually at the CLI.

The second part doesn't seem to be an option unless you're on MM or MCM; on standalone, there's no where for the controller to get the upstream config from.