NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Jeroenvans's avatar
Jeroenvans
Follower
Oct 03, 2025

Engage switchconfig bug

I've just started commissioning a rather large M4350-based network, and this is my first encounter with Netgear and Engage for this. (I do have experience with Arista/CVP and Cisco.)

I like the Engage software, and I'm aware it's still being developed, but there is one bug that's very annoying, which I've found in 2 parts of the config software now.

It has to do with duplicates in remants of config that remain after deleting something. For now I found this for an IP-address and a LAG name.

 

When I create a LAG with a certain name and then delete the LAG for whatever reason, I'm now no longer able to reuse the name I've deleted. Re-creating a LAG with the same ID but a different name enabled me to reuse the first LAG name.

The same goes for an IP-address. I wanted to swap the IP address from the OOB interface to a VLAN interface. I changed the OOB to DHCP and reconnected to the new IP address on the OOB port. I was then unable to reuse the old static address on a VLAN interface because it was already "in -use".

I had to first change the static address on the OOB and then set it back to DHCP to "release" the IP address for use somewhere else.

So it seems the deleted config bits are not fully deleted. 

 

Also, please either remove the stacking function from Engage or add a warning that it's very limited and refer to the switchGUI for more options until the feature is more complete. It took me longer than I'm willing to admit to find this out.

 

I'm on the latest software and firmware.

1 Reply

Replies have been turned off for this discussion
  • LaurentMa's avatar
    LaurentMa
    NETGEAR Expert

    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:ProAVDesign@netgear.com 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:ProAVDesign@netgear.com as the forum here is not a support avenue.  Thanks! Laurent

NETGEAR Academy

Master AV-over-IP networking, multicast protocols, and troubleshooting to confidently deploy and manage AV networks. 
Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More