I am answering to you, and I hope it will help the entire Community if anyone is looking for the same.
I am trying to give a comprehensive and honest answer here. The profiles are the "tip" of the iceberg here.
Each profile (template) comes with a self-explanatory description in the AV user interface (M4250, M4300, M4350, M4500) and in the Engage controller. Audio Dante, Video with Q-SYS, NDI 5/6 with Audio Dante, AES67, Q-SYS; etc.
It is very easy to apply a profile template to the VLAN 1 (default VLAN) of the NETGEAR AV Line switch and click apply. Then from the AV user interface directly, or from Engage (list of devices), startup the telnet console in the browser, and enter "show run" to see all the settings of the template.
These profiles are the results of very strict AV manufacturers certification processes, including the NETGEAR QA regression testing etc. We do not publish these settings as they would be prone to mistakes when the configuration would be done in the IT GUI (dozens and dozens of pages to navigate) and even worst in the console (CLI). And since all NETGEAR AV Line switches can be managed from the AV User Interface and the Engage controller, the profiles are there, ready to use anyway, with all the automation.
This is the tip of the iceberg, because the configuration isn't meant to just "work" on any other switch platform than the NETGEAR AV Line switches, anyway. AV is not only a matter of settings and standards - we know it, given the hundreds, if not thousands of other software issues, tolerances, adaptations we have to make with any new AV manufacturer during the certification process.
With the NETGEAR AV Line profile, it just works. But applying the same configuration commands on any other NETGEAR switch, or third-party switches at other manufacturers would be useless anyway - as the platforms wouldn't have all the other enhancements built-in to make it all work as expected. IGMP Plus is just one example, I could talk for days and days about fast leave, querier, QoS, battle between L2 CoS and L3 DSCPs, PTP, discovery protocols, and all the other underlying L2/L3 things that make AV over IP eventless. Using the NETGEAR AV Lines profiles are just solving it all.
I hope it helps - publishing the configuration behind the profiles would actually cause way more confusion and create a lot of problems. Again, you can see everything in the terminal - show run - but I cannot advise reproducing the NETGEAR AV Line profiles on any other switch platform as they wouldn't work as expected.
Thank you for your insightful response. The value and utility of the AV GUI is well appreciated, particularly when setting up a new switch or network.
I recently encountered Dante and other discovery problems in a network that I'd just started working with, where the IT manager is on leave. Looking for errant settings, without any information about how the switch's programming might have been altered from the AV profile that was used, requires investigating the IT GUI. Knowing what the unaltered profile settings should be would be quite valuable.
Sure - the best way remains to start fresh on a broken installation and factory-default everything
It is a 5-minute process using the Engage controller and the reconfiguration from scratch is another 5-minute process in most cases. This is why we have the ProAV Engineering Services, worldwide. Please email the team at ProAVDesign@netgear.com and ask for help@
