This is not going to add much, but it could save time: Containers in an ArubaOS 8 hierarchy are designed for multinational or multicampus corporations that have a unified base configuration globally but want to create exceptions to that configuration at the country level. In the vast majority of single-country situations configurations should use ap-groups in a single folder, rather than folders to provide different configurations. Keeping different configurations in different folders and navigating exceptions will make administration and troubleshooting more difficult. Folders were meant to separate administrative domains and to create country-level exceptions for a global configuration. There is also a limit for folder depth, so you certainly don't want to run into that. There is definitely a value to separating campuses by folder, for example, but again, it may or may not complicate things if you're not adept at navigating and reconciling exceptions to configurations that folder levels. If you have different campuses, it is not super hard to define things like an NTP server at the controller level for proper control.
- create a folder under MD and put your configuration there
- do not put any configuration in the MD folder, because you will not be able to undo it. You will also not be able to create a drastically different configuration that differs from any configuration in the MD folder, if you put configuration in the MD folder.
- use ap-groups for everything in the folder under MD and you should be fine. A single folder is the secret to happiness. Did you just acquire another company? Create a new folder under MD and put an entirely new configuration there.
- controllers create their own "folder" and that is essential for controller specific things like IP addresses, port configuration, host name, etc. That will be useful later if you ever wanted to migrate controller specific configuration to another device for example.
I hope this was not too complicated or wordy. There are tons of users that require help cleaning up their configuration and the short answer is many times merging configuration into a single folder simply because everything is all over the place and they can't figure out where everything is. Putting everything in a single folder and just simply doing everything based on AP groups is the answer. That is my opinion (and probably only my opinion).
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
Sent: Jan 13, 2022 10:33 AM
From: Jules Bvt
Subject: MM/MD Hierarchy : How to display AP-Groups ?
Hi everyone !
I configured a cluster with 2xMM and 4xMD devices.
I defined specific hierarchy as below :
I defined some AP-groups under /md/group1/ hierarchy.
Today, I need to display AP-groups list and configuration on CLI interface but, unfortunately, I don't found any command able to do this action !
If I'm under /md/group1/ hierarchy I've got this issue :
(MM01) *[group1] #show ap-group CAMPUS1
The commands for applications run on MM need to be executed on /mm tree.
The commands for applications run on individual devices need to be executed on the device node in 'mdconnect' mode.
However, If I execute this command on /mm tree
(MM01) *[mm] #show ap-group CAMPUS1
AP group "CAMPUS1" undefined.
On GUI interface, there is not any problem to display AP-Group by clicking on correct hierarchy level.
My question is the following : How can I display AP-Group configuration from MM CLI interface ?
Thanks a lot for your help.