In the previous AOS version (6.x), the whole configuration of the controller in standalone mode was in an unique file (default.cfg). To provision the controllers, we were able to upload a new configuration file, replace the default.cfg file, and reboot the controller, it was working fine.
With the new version 8, it seems to be more complex. We can easily export the current configuration from a standalone controller with a "copy running-config ..." command, but I have noticed that the default.cfg file is now only containing the configuration after the initial setup, and not the current running configuration.
So, I didn't yet try to replace this default.cfg file with a complete configuration file as I don't want to bricked the controller.
Is there a procedure with the AOS verion 8 to upload a configuration file? We would like to do it as we have a tool that automatically generate configuration text file for each network equipement to ease deployments.
Just see that your thread doesn't get a reply. I think it would be good to post this in another dicussion group like Wireless Access. This thread is currently in the switching and routing group.
Thank you for moving the thread to a more appropriate group, but unhopefully, there is not yet an answer...
It's very hard (if not impossible to brick a controller) by tampering its file structure because in the worst case, you can always format the flash (format 0:2) at the cpboot prompt.
This being said, I'll try to have a look tomorrow on the file structure
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.