Controller-less WLANs

How Aruba IAP commands "commit apply", "commit apply no-save" and "commit revert" works?
Requirement:

IAP's should be running minimum 6.2.1.0-3.3.0.0 or above



Solution:

Prior to 6.2.1.0-3.3.0.0 we were allowed to make the configuration only through WebUI.

From 6.2.1.0-3.3.0.0 onwards, we are allowed to make the configuration changes through the WebUI and through Command Line Interface(CLI). When we use the Command Line Interface(CLI), configuration changes will take effect only after the “commit apply” command is executed.

When we do not save the configuration using the "commit-apply" then it is not saved to the current configuration of the IAP. 

We can see the unsaved or uncommitted configuration using the following command

"show uncommitted configuration"

We can see the current configuration using the following command

"show running-config"

Note: Configuration changes are allowed only on the Virtual Controller that is elected as Master among the other IAP's on the Cluster.



Configuration:

The "commit" command can do the following task with the following commands

1. "commit apply no-save":

The configuration with "commit apply no-save" are temporarily saved to the current configuration of IAP. When the cluster is rebooted the temporary changes are deleted from the current configuration and the IAP cluster boots up with the current configuration with out temporary changes. 

Note: The "commit apply no-save" command working only in the privilege mode and it is not available in the configuration mode.

2. "commit revert":

The commit revert command discards / delete only the uncommitted/ unsaved configuration that are listed under the below command

#show uncommitted configuration

Note: The "commit revert" command working only in the privilege mode and it is not available in the configuration mode. It doesn't revert any change in the current configuration.

3. "commit apply":

The commit apply command applies the unsaved/uncommitted changes to the current configuration of the IAP. These changes with "commit apply" are permanently saved to the current configuration until factory reset of an IAP.

To see the uncommitted/ unsaved changes:

#show uncommitted configuration

To see the current configuration:

#show running-config

Note: The "commit apply" command working only in the privilege mode and it is not available in the configuration mode.
 



Verification

Example:

Current VPN Configuration on the IAP Virtual Controller:

 

 

1. a.  Using "commit apply no-save":

 

1. b. Current configuration reverted after the reload of the cluster

 

 

2. Using "commit revert":

 

 

3. Using "commit apply":

 

 

 

 

Version history
Revision #:
2 of 2
Last update:
‎03-28-2017 09:26 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
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.