NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
LAG ports create DUP packets and STP chaos
Hi all. We have exchanged or previous Aruba switches with Netgear XSM4348S switches, which are acting as a stack (4 switches). Behind these switches are GSM4328S & GS728TPPv2, which are connected...
Today I gave it another try - long story short:
not the stack switch was the problem but the M4300s behind it. AFAIK all M4300 don't use the static mode by default which means that LACP is used. I had to reset the M4300 to factory defaults (but not the stack) and start over. After I reconfigured the M4300s which are connected behind the stack by re-importing the config the LAG came up as usual and works.
Side notice: when using a standard LAG in the M4300 series in combination with the mentioned Smart Managed switches (GS728TPPv2) you have to set the LACP mode on the GS728TPPv2 manually. Unlike the M4300s the Smart Managed switches seem to use the static mode by default. Same applies to other vendors like HP (ProCurve series).
Reads like we have some basic definition problem: A one-port LAG - what is the point of this? Are you probably mix up the functionality of a LAG (port aggregation) with a port or a LAG configured as a trunk for handling multiple VLAN?
Different hash modes are only defining on how the traffic is distributed on a LAG with multiple physical !inks.
If STP issues arise on LAGs, it's an indication that the LAG are not set-up correct, the duplicate packets confirm this.
Another possibility is that you mix stack ports (which automatically handle all VLAN between stack members) with LAG - an impossible config.
I would strongly suggest to configure all M4300s in a stack, with all links in stack port mode. The links to the Smart Managed switches must be configured as trunk, all VLANs tagged, probably except of one VLAN which can be operated untagged and that same PVID, on general Ethernet (not stack mode).
Different hash modes are only defining on how the traffic is distributed on a LAG with multiple physical !inks.
If STP issues arise on LAGs, it's an indication that the LAG are not set-up correct, the duplicate packets confirm this.
Another possibility is that you mix stack ports (which automatically handle all VLAN between stack members) with LAG - an impossible config.
I would strongly suggest to configure all M4300s in a stack, with all links in stack port mode. The links to the Smart Managed switches must be configured as trunk, all VLANs tagged, probably except of one VLAN which can be operated untagged and that same PVID, on general Ethernet (not stack mode).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
