This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
M4350 - AVUI "download config" vs MainUI "Maintenance > Export"
When archiving the switch configuration for future maintenance referral, if I take a backup from the AVUI it creates a "startup-config.cfg" file that includes the text configuration AND the html for the AV Profiles (commented out).
However, from the MainUI all backup methods seem to only grab the text configuration without the AV Profile information.
Is there an equivalent backup from the MainUI or the CLI? I am asking as I am trying to script a recurring backup.
Thank you for your message. You are right, let me explain:
From the AV User Interface or the NETGEAR Engage Controller, when you back up (download) the configuration, this is a .cfg file that has the startup config (CLI) and the AVUI profiles information (XML data in there)
From the main IT GUI or CLI, when you back up (export) the configuration, this is a text file without extension that only has the startup config (CLI) with the AVUI XML information
So when you are trying to "reload" the config file from the AVUI or the Engage Controller using the Main IT GUI or CLI, you are "losing" the AVUI profiles configuration. For now, if you are using the AVUI or the Engage Controller, best practice is to "keep using the AVUI or the Engage controller" only for backup/restore.
If you want to script a recurring backup, you will need to use the AVUI API - so that you have all AVUI XML info into the .cfg config files. Please contact us via email at ProAVDesign@netgear.com and we will share the AVUI API with you.
Thank you for your message. You are right, let me explain:
From the AV User Interface or the NETGEAR Engage Controller, when you back up (download) the configuration, this is a .cfg file that has the startup config (CLI) and the AVUI profiles information (XML data in there)
From the main IT GUI or CLI, when you back up (export) the configuration, this is a text file without extension that only has the startup config (CLI) with the AVUI XML information
So when you are trying to "reload" the config file from the AVUI or the Engage Controller using the Main IT GUI or CLI, you are "losing" the AVUI profiles configuration. For now, if you are using the AVUI or the Engage Controller, best practice is to "keep using the AVUI or the Engage controller" only for backup/restore.
If you want to script a recurring backup, you will need to use the AVUI API - so that you have all AVUI XML info into the .cfg config files. Please contact us via email at ProAVDesign@netgear.com and we will share the AVUI API with you.
