Controller Based WLANs

How to troubleshoot? Change made from MMS not showing up in the controller configuration after config push.

Aruba Employee

Product and Software: This article applies to all Aruba MMS versions.

 

Symptoms

 

  1.  Able to commit configuration change and push the configuration from MMS, but the controller shows old configuration.
  2.  When change is committed, no controller shows up under the commit window and the automatic push does not happen.
  3.  If you have auto config disabled, the expected controller group does not appear in the list of affected controller groups when you commit the change, and a manual push does not push the newly modified configuration to the controller.

Root Cause

 

The profile that the change is made under is not referenced (either directly or indirectly) from the controller group that the controller belongs to. Follow up the parent hierarchy of the new/modified profile(s) to make sure that it ends at the controller group that the controller belongs to. Remember, configuration in Aruba 3.x and beyond is all about profiles and hierarchies.

 

Remedy

 

It is not enough that the profile is referenced by some other profile. It has to be referenced directly or indirectly by a controller group: Apply the leaf profile to its parent profile, for example, SSID profile to virtual AP profile or AP SNMP profile to an AP group. Make sure the profile is in the hierarchy of the controller group profile. In other words, make sure the profile is referenced directly or indirectly from the controller group. One quick way to verify which profile is referencing a given profile is to click the Used By tab at the bottom of the profile. Follow the references up the hierarchy to make sure the relevant profile is in the controller group's hierarchy.

 

To verify the changes, follow these troubleshooting steps:

 

  1. Make sure you clicked Apply in the window you made the change to.
  2. Follow the reference hierarchy up to the controller group by using the Used By tab.
  3. Verify that the changes are reflected in the Changes tab.
  4. When you proceed to commit a change, the expected controller (if you are using auto-config updates) or controller group (if you are using manual updates) should be displayed in the window that pops up. If not, repeat steps 1 to 3.
  5. If the controller is not in auto-config update mode, trigger manual config push.
  6. From the Dashboard, confirm that the controller configuration is in synch.
  7. Verify that the change was applied on the controller using the controller CLI.
Version history
Revision #:
1 of 1
Last update:
‎07-01-2014 02:51 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.