I would suggest that you reach out to your local Aruba SE and discuss this. The way it is designed, blocking local configuration when managed by Central, works for most cases. You obviously don't like it, but allowing local configuration that is overridden by a centralized management platform and reversed at the next sync, is probably worse. Or I don't understand what you want, because what you describe is exactly what happens. Template is the 'desired config', and is compared to the running config, then changes are pushed to the switch config.
Many engineers are used to build manual configs, but at scale that will not work and having both central and local control will make it unmanageable, at least at scale. It will require a different way of working from the network admin. And as mentioned before, if you need to test some local commands, enter central support mode and do whatever you want. Just be aware that when you disable that mode, all changed not committed in the central configuration are reverted.
As mentioned, please speak to your local Aruba team to get the options explained and find what is working for you and if features need to be added they can feed that into the product development process as well.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------
Original Message:
Sent: Apr 21, 2021 01:41 PM
From: john Stigall
Subject: Firmware upgrade and now restricted CLI commands
This is unacceptable in our network.
Here's how it should work:
Pull the config from the switch, compare to template.
Every time.
Report the result.
The product is just not usable to manage switches yet.
------------------------------
john Stigall
Original Message:
Sent: Feb 25, 2021 04:33 PM
From: Andrew Brown
Subject: Firmware upgrade and now restricted CLI commands
Hello,
Just new to Aruba Central. We have a small network with 2 x 3810m stacked and 3 stacks of 2930fs. I configured the network using CLI before the Central licence arrived and all was good. Everything working. This is a staged deployment so no actual users yet.
I added the switches to ACentral to the default group. After a firware update pushed out by Central I can no longer manage the switches via cli. It seems like a completely restricted command set.
I did notice that if i took the switches offline from central full access was available again. Is this normal ?
example:
CORE(config)# conf t
Invalid input: conf
CORE(config)# int
Invalid input: int
CORE(config)# int
Invalid input: int
CORE(config)# interface vlan 100
Invalid input: interface
CORE(config)# wr mem
Invalid input: mem
CORE(config)#
Any advice guys ?
------------------------------
Andrew Brown
------------------------------