Cloud Managed Networks

So, over the weekend, one of the two switches has synced it config, but not the other one.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.

Building on where Herman pointed you, those "configuration settings were filtered" blocks are the interesting part. Filtered means Central decided not to push those lines to that switch, and the most common reason on a freshly onboarded box is a local override: anything that was set on the switch itself before onboarding, the hostname included, is treated as switch-owned and quietly wins over what you set in Central. That would explain why the name never updates while its twin, which presumably came in cleaner, synced fine over the weekend.

On that switch's Configuration Status page check the Local Overrides view specifically, not just the sync banner. If the hostname or those filtered sections show up there, clear the override or push from Central with the overwrite intent, and that should also be the clean commit that finally clears the stale error.

------------------------------
Dustin Burns

@Worldcom Exchange, Inc.


If my post was useful accept solution and/or give kudos
------------------------------


Original Message:
Sent: Aug 31, 2026 08:03 AM
From: DS-FkB358
Subject: New Central not properly updating Configuration

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Original Message:
Sent: Aug 31, 2026 06:40 AM
From: HR-abaef5
Subject: New Central not properly updating Configuration

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------




Original Message:
Sent: Aug 31, 2026 04:45 AM
From: DS-FkB358
Subject: New Central not properly updating Configuration

So, over the weekend, one of the two switches has synced it config, but not the other one.

Where do i find that configuration status page in new Central?
the only place in the switch overview that mentions config status is this one, and its not expandable.
The Config settings of the switch dont mention Syncing at all, it also does not show the System information section (which controls the Switches hostname) as override.

Building on where Herman pointed you, those "configuration settings were filtered" blocks are the interesting part. Filtered means Central decided not to push those lines to that switch, and the most common reason on a freshly onboarded box is a local override: anything that was set on the switch itself before onboarding, the hostname included, is treated as switch-owned and quietly wins over what you set in Central. That would explain why the name never updates while its twin, which presumably came in cleaner, synced fine over the weekend.

On that switch's Configuration Status page check the Local Overrides view specifically, not just the sync banner. If the hostname or those filtered sections show up there, clear the override or push from Central with the overwrite intent, and that should also be the clean commit that finally clears the stale error.

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.

I think Dustin refers to the Device -> Configuration -> Configuration Audit page in Classic Central.

I've myself only seen this for gateways, but there sometimes are overrides from Classic still active. When moving a gateway from Classic to (New) Central for configuration, you may need to reset the configuration in Classic to avoid configuration conflicts.

Where do i find that configuration status page in new Central?
the only place in the switch overview that mentions config status is this one, and its not expandable.
The Config settings of the switch dont mention Syncing at all, it also does not show the System information section (which controls the Switches hostname) as override.

Building on where Herman pointed you, those "configuration settings were filtered" blocks are the interesting part. Filtered means Central decided not to push those lines to that switch, and the most common reason on a freshly onboarded box is a local override: anything that was set on the switch itself before onboarding, the hostname included, is treated as switch-owned and quietly wins over what you set in Central. That would explain why the name never updates while its twin, which presumably came in cleaner, synced fine over the weekend.

On that switch's Configuration Status page check the Local Overrides view specifically, not just the sync banner. If the hostname or those filtered sections show up there, clear the override or push from Central with the overwrite intent, and that should also be the clean commit that finally clears the stale error.

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.

in classic central, there is no option for me to configure a singular switch anymore, this tab is simply gone, which makes the config page for this one inaccessible.

the group configuration page in classic central is empty for the group the switch is in.

I think Dustin refers to the Device -> Configuration -> Configuration Audit page in Classic Central.

I've myself only seen this for gateways, but there sometimes are overrides from Classic still active. When moving a gateway from Classic to (New) Central for configuration, you may need to reset the configuration in Classic to avoid configuration conflicts.

Where do i find that configuration status page in new Central?
the only place in the switch overview that mentions config status is this one, and its not expandable.
The Config settings of the switch dont mention Syncing at all, it also does not show the System information section (which controls the Switches hostname) as override.

Building on where Herman pointed you, those "configuration settings were filtered" blocks are the interesting part. Filtered means Central decided not to push those lines to that switch, and the most common reason on a freshly onboarded box is a local override: anything that was set on the switch itself before onboarding, the hostname included, is treated as switch-owned and quietly wins over what you set in Central. That would explain why the name never updates while its twin, which presumably came in cleaner, synced fine over the weekend.

On that switch's Configuration Status page check the Local Overrides view specifically, not just the sync banner. If the hostname or those filtered sections show up there, clear the override or push from Central with the overwrite intent, and that should also be the clean commit that finally clears the stale error.

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.

My mistake on the page, and Herman's right: that Configuration Status view is a Classic Central thing and doesn't exist the same way in New Central. Sorry for the runaround. Your Classic tab being gone is actually expected, once the switch is New Central managed, Classic hands off and shows nothing for it.

The wrong uptime is the detail I'd chase now. A switch reporting stale uptime is a switch whose management session to Central isn't healthy, and a box in that state will accept a name change in the UI and never actually receive it. From the switch CLI run show aruba-central and look at Central connection status. If it says anything but connected, that's your whole problem. If it's connected and still refusing the push, that output plus the audit trail entry for the failed attempt is a TAC case, because at that point it's a platform problem, not your config.

in classic central, there is no option for me to configure a singular switch anymore, this tab is simply gone, which makes the config page for this one inaccessible.

the group configuration page in classic central is empty for the group the switch is in.

I think Dustin refers to the Device -> Configuration -> Configuration Audit page in Classic Central.

I've myself only seen this for gateways, but there sometimes are overrides from Classic still active. When moving a gateway from Classic to (New) Central for configuration, you may need to reset the configuration in Classic to avoid configuration conflicts.

Where do i find that configuration status page in new Central?
the only place in the switch overview that mentions config status is this one, and its not expandable.
The Config settings of the switch dont mention Syncing at all, it also does not show the System information section (which controls the Switches hostname) as override.

Building on where Herman pointed you, those "configuration settings were filtered" blocks are the interesting part. Filtered means Central decided not to push those lines to that switch, and the most common reason on a freshly onboarded box is a local override: anything that was set on the switch itself before onboarding, the hostname included, is treated as switch-owned and quietly wins over what you set in Central. That would explain why the name never updates while its twin, which presumably came in cleaner, synced fine over the weekend.

On that switch's Configuration Status page check the Local Overrides view specifically, not just the sync banner. If the hostname or those filtered sections show up there, clear the override or push from Central with the overwrite intent, and that should also be the clean commit that finally clears the stale error.

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.

The switch says its happy with its central connection, so i will be opening a TAC case for this now.

I'll update the post once its resolved.

My mistake on the page, and Herman's right: that Configuration Status view is a Classic Central thing and doesn't exist the same way in New Central. Sorry for the runaround. Your Classic tab being gone is actually expected, once the switch is New Central managed, Classic hands off and shows nothing for it.

The wrong uptime is the detail I'd chase now. A switch reporting stale uptime is a switch whose management session to Central isn't healthy, and a box in that state will accept a name change in the UI and never actually receive it. From the switch CLI run show aruba-central and look at Central connection status. If it says anything but connected, that's your whole problem. If it's connected and still refusing the push, that output plus the audit trail entry for the failed attempt is a TAC case, because at that point it's a platform problem, not your config.

in classic central, there is no option for me to configure a singular switch anymore, this tab is simply gone, which makes the config page for this one inaccessible.

the group configuration page in classic central is empty for the group the switch is in.

I think Dustin refers to the Device -> Configuration -> Configuration Audit page in Classic Central.

I've myself only seen this for gateways, but there sometimes are overrides from Classic still active. When moving a gateway from Classic to (New) Central for configuration, you may need to reset the configuration in Classic to avoid configuration conflicts.

Where do i find that configuration status page in new Central?
the only place in the switch overview that mentions config status is this one, and its not expandable.
The Config settings of the switch dont mention Syncing at all, it also does not show the System information section (which controls the Switches hostname) as override.

Building on where Herman pointed you, those "configuration settings were filtered" blocks are the interesting part. Filtered means Central decided not to push those lines to that switch, and the most common reason on a freshly onboarded box is a local override: anything that was set on the switch itself before onboarding, the hostname included, is treated as switch-owned and quietly wins over what you set in Central. That would explain why the name never updates while its twin, which presumably came in cleaner, synced fine over the weekend.

On that switch's Configuration Status page check the Local Overrides view specifically, not just the sync banner. If the hostname or those filtered sections show up there, clear the override or push from Central with the overwrite intent, and that should also be the clean commit that finally clears the stale error.

Hi Herman, both of the previous screenshots were from the Config Status Page.
thanks to your tip I have synced both of them again just to see how it looks in the Audit Trial:

i did read through the "Configurtion settings were filtered" blocks, half of that is Configuration that I never even touched, so it should be the default. the other thing i noticed, the one successfuly syncing is getting that confirmation message for asuccessful sync at the very top, but the switch with the default name doesnt have that. both of those switches have the same configuration from the same site and same device group, the only difference between them should be IP Address, Name (if it would update) and which of the port profiles apply to which ports.

Do you have on the Central start page the 'Configuration Status' card?

From there, if you expand it (to arrows on the top-right); there should be more information. Also, the audit trail may indicate a reason for the configuration not being propagated or synchronized.

So, over the weekend, one of the two switches has synced it config, but not the other one.