Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Applying Configuration Changes
HPE Aruba Networking Central supports a two-staged configuration commit workflow for Instant APs and switches. HPE Aruba Networking Central now supports the auto commit feature at a group level. When auto commit state is enabled for a group, the configuration changes are instantly applied to all devices where auto commit state is enabled.
In the page of the group, the section allows administrators to switch their preference for committing configuration changes to the devices within the group.
- To enable auto commit, click . When auto commit state is enabled for a group, the configuration changes are instantly applied to all devices where auto commit state is enabled.
- To disable auto commit, click . When auto commit state is disabled for a group, an administrator can build a candidate configuration, save it on cloud, review it, and then commit the configuration changes to all devices within the group.
HPE Aruba Networking Central resets the auto commit state, when a device moves to another group. The device inherits the auto
commit state of the group to which the device is moved.
When auto commit
state is disabled for a group, HPE Aruba Networking Central restricts modification to the auto commit state at a device
level. When auto commit
state is enabled for a group, HPE Aruba Networking Central allows modification to the auto commit state at a device
level.
The auto commit at a group level is not applicable for HPE Aruba Networking gateways in the page. Auto commit state is always enabled for HPE Aruba Networking gateways.
For more information, see the following topics:
