Using Configuration Status on AOS-CX
Aruba Central (on-premises) provides an audit dashboard for reviewing configuration changes for the AOS-CX switches provisioned in UI groups. The Configuration Status page displays the configuration status of the switches, pending changes, and local overrides present in the AOS-CX switches. It also provides options to push uncommitted changes to the switches.
To view and commit the configuration changes, complete the following steps:
- In the
- To select a group in the filter:
- Set the filter to a group.
The dashboard context for the group is displayed.
- Under , click > .
- Click the AOS-CX switch configuration dashboard. or icon to view the
- Set the filter to a group.
- To select a switch:
- Set the filter to or a group containing at least one switch.
- Under
A list of switches is displayed in the
view. , click > . - Click an AOS-CX switch under .
The dashboard context for the switch is displayed.
- Under
The AOS-CX UI configuration page is displayed.
, click .
app, select one of the following options: - To select a group in the filter:
- Click
The Configuration Status page is displayed with details about the configuration status of AOS-CX switches.
The page displays the following information at the group and device levels:
- At the group level:
- —Count of switches that have the auto-commit state on and off.
section—Click a number to view corresponding results filtered in the column in the table.- —Count of switches that have configuration changes that are pending commitment to the switch.
- —Count of switches for which errors in the pending configuration caused an attempted commit to fail.
In the Viewing and Committing Configuration Issues and Pending Changes at the Group Level.
column, click the link corresponding to the status to view the pending changes in a configuration or the link to view any issues in a pending configuration. For more information, see section—Click a number to view corresponding results filtered in the column in the table.- —Count of switches that have device level configuration changes.
- —Count of switches that do not have device level configuration changes.
section—Click a number to view corresponding results filtered in the column in the table.
- At the device level:
- Toggle switch in the on position—Displays a message that the configuration changes will be committed to the device immediately.
- Toggle switch in the off position—Displays a message that the configuration changes will not be committed to the device immediately.
section—Enable or disable the auto-commit mode by moving the toggle switch to the on or off position.- Table 1.
Click the Viewing and Committing Configuration Issues and Pending Changes at the Group Level.
link to view the pending changes in a configuration or the link to view any issues in a pending configuration. For more information, see section—Displays a message defining the status of configuration on the switch. For a list of all status messages, see the description of the column in - section—Displays a message to indicate whether there are any overrides in the switch configuration at the device level or not.
. - At the group level:
- Click the number in the sections to apply the corresponding filter in the
The
table displays the following information:The
table appears only at the group level.Column
Description
Value Name of the switch.
Status of the auto commit option for the switch.
,
Status of switch configuration between the device and Aruba Central (on-premises). The following statuses are available:
Indicates whether any overrides exist in the switches.
,
table.
Viewing and Committing Configuration Issues and Pending Changes at the Group Level
To view and commit configuration issues and pending changes in AOS-CX switches at the group level, complete the following steps:
- To view the pending changes in a configuration click the link corresponding to the following statuses in the
The Pending Configuration Changes window is displayed for that switch. This window displays the running and pending configurations of the switch and lets you review the changes made in configuration.
column for the switch: - Click one of the following buttons depending on the status:
- Click
Click this button to push the pending changes to the switch.
—Displayed only when the user has modify permissions for the group, and when auto-commit state is off and there are pending changes but no errors. - Click —Click this button to close the Pending Configuration Changes window without modifying the switch configuration.
- Click
- To view issues with a pending configuration, click the
The Configuration Conflicts window is displayed for that switch. This window displays a description for each error and the line number in the configuration file where the error has occurred.
The line number displayed in the Configuration Conflicts window might not be same as in the configuration editor. You must look for the correct line in the editor by searching the command where the error occurs.
link in the column for the switch. - Click .
Viewing and Committing Configuration Issues and Pending Changes at the Device Level
To view and commit configuration issues and pending changes in AOS-CX switches at the device level, complete the following steps:
- To view the pending changes in a configuration click the
The Pending Configuration Changes window is displayed for that switch. This window displays the running and pending configurations of the switch and lets you review the changes made in configuration.
If the pending changes do not have any errors, the
button is displayed, both in the section and in the Pending Configuration Changes window. link in the section. - Click to push the pending changes to the switch.
To view issues with a pending configuration, click the
link in the section.The Configuration Conflicts window is displayed for that switch. This window displays a description for each error and the line number in the configuration file where the error has occurred.
The line number displayed in the Configuration Conflicts window might not be same as in the configuration editor. You must look for the correct line in the editor by searching the command where the error occurs.
- Click .