Aruba pulled the "feature" and postponed it until a later 2.x Central version, IMHO as they recognized it renders AOS-S switches in UI-groups unusable, because of having only a few parameters that you can use in UI-groups.
Original Message:
Sent: Nov 20, 2023 11:50 AM
From: kadis500
Subject: Aruba Central overwriting CLI config on AOS-CX switches since 2.7 update
Hello,
I still can use Aruba-central support-mode , and when i pushed the configuration from CLI ( using Aruba CEntral console tools), Central does not override it !
So please tell me how this feature is working now ? :
Original Message:
Sent: Jul 18, 2023 02:11 AM
From: d4
Subject: Aruba Central overwriting CLI config on AOS-CX switches since 2.7 update
Thank you for this, do you have a link to this in the documentation?
Original Message:
Sent: Jul 11, 2023 11:53 PM
From: BrettV
Subject: Aruba Central overwriting CLI config on AOS-CX switches since 2.7 update
Found it!
Anyone care to tell me what a port-profile is? And how it can replace my bulk CLI push?
------------------------------
Regards,
Brett V
Original Message:
Sent: Jul 11, 2023 11:43 PM
From: BrettV
Subject: Aruba Central overwriting CLI config on AOS-CX switches since 2.7 update
Hi all,
Since Central version 2.7, no matter what I do - all config pushed to AOS-CX switches via CLI (SSH/Console) is overwritten via Central. These switches are in UI groups.
When a new switch is brought online (and I have several hundred more to install right now), we use automated tools that push the port config to each switch. We use CLI because Central does not support some of the commands we need, including the Central API. Multi-Edit doesn't allow for range of interfaces to be configured where our tool does.
I have tried:
aruba-central support mode
and
no configuration-lockout central managed
...but Central keeps overwriting the interface config with default values.
The only way for me to get the config to stick is to run the command:
aruba central
disable
wait for the switch to go offline in Central, delete it, apply the CLI config, enable central again on the switch:
aruba central
enable
then add the switch back to it's group with the "retain CX switch configuration" button.
but I still can't make any changes from that point forward.
Any ideas? Is this by design in 2.7 or am I doing something wrong?
------------------------------
Regards,
Brett V
------------------------------