Engage switchconfig bug

Hello Jeroenvans​ 

Thank you for your constructive feedback here, and let me respond in the second paragraph about what I know and why (you call things bug - it might not be true ;-) On your side, thank you for considering the NETGEAR M4350 AV series for your AV project - you are not alone for this initial commissioning - please come to us sending a message (email) at mailto:[email protected] and one proficient System Engineer will help you and transfer good practices. You can also take a look at our step by step application notes here: https://www.netgear.com/hub/business/av/av-tech-guides/

I don't believe the two issues you are describing have a "bug" as a root cause:

1. I just tested in my lab here Engage 2.2.1.4 and M4350 switches running 14.0.6.9, and I can create a LAG with a name and LAG ID, adding ports to it, apply - then delete this LAG, and recreate a new LAG using the same name and the same ID directly
2. I know it may sound counter-intuitive, but the system doesn't allow the same subnet between OOB interface and in-band interfaces. I just tested, and I cannot reproduce either. If the OOB port gets a DHCP client address from a DHCP server, then its previous fixed IP address is gone and the system is allowing that subnet again on the other side (VLAN interfaces). You can always verify the running-configuration by doing a show service-port or a show run in the enable mode of the console/terminal from Engage or AVUI

Since I cannot reproduce, it means other factors in your configuration on the switches or your site in Engage may have conflicted - for this the ProAV Design team would have asked the Tech-Support file out of your site in Engage (Support tab) or individually from the switches (AVUI Diagnostics\Support Diagnostics) to understand when the issue is present.

I need to warn you for stacking, please refer to the M4350 datasheet on page 30:

• Stacking is supported in AV environments only in a 2-switch stack at the core for HA
• But AVB and PTP are mutually exclusive features with stacking, so you cannot use stacking if AVB or PTP
• At the core, stacking links must handle the total multicast on the network so you need to calibrate it
• If there is a need of PTP for instance at the core and HA, then MLAG on M4500 series is required at the core

Please come to us at mailto:[email protected] as the forum here is not a support avenue.  Thanks! Laurent