NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
LACP
2 TopicsIssues with LACP with VLANs
Hi all, Network newbie here. I am having some trouble with VLAN's combined with LACP. The setup I have at the moment are purely for educating my self. It consists of: One Netgear GS724Tv4 One PFsense router virtualized in Proxmox. The LAN interface of router is a separate NIC where all ports are in the same bond, which is configured for LACP. This bond have a dedicated bridge which is assigned as LAN interface for the router. This NIC is connected to port 1-4 on the switch, which is configured as "lag1" One Synology rack station with a SSD. The LAN interface is configured to use all four ports in LACP. It is connected to ports 5-8 on the switch which is configured as "lag2" I am using two computers to test the bandwidth of the system, just by simply copying a large file from each computer to the NAS. These are either connected to ports 19 and 20, or 21 and 22 depending on which VLAN I want to use. When connecting the computers to the same VLAN as the NAS everything seems to work just fine: Port 19 and 20 are receiving ~2050000 packets each. Lag2, the LACP of the NAS, is transmitting ~4100000 packets. These packages are distributed between port 6 and 8. This means that the LACP to the NAS is working, right? But when moving the computers to another VLAN the trouble begins: Port 21 and 22 are receiving ~2050000 packets each. These are transmitted to the router on lag1 and it seems like it decided to use port 2 and 3 for the task. The router is routing the packages from the VLAN with the computers to the VLAN with the NAS. The switch is receiving the packages on lag1 again, but this time on port 1 and 3. So far so good? It seems like the LACP between the switch and the router is working good to? The switch is transmitting the packages on lag2 to the NAS, but why does it only use port 8 now!? The consequence is obvious when looking at the speeds of the file transfer... What am I missing?10Views0likes1CommentM7300/M4300, and all netgear managed switches, apparently do not support LACP fallback mode
We have both M4300 and M7300 10GbE switches from Netgear in our environment. It does not appear that any netgear switches support LACP fallback mode. We already checked with support and tried the latest firmware. In other words, LACP is either enabled or disabled. There is no way to have it enabled, but to automatically fall back to disabled, when appropriate. This creates significant issues in our environment, and for many others, as any kind of re-imaging of a server using PXE will fail. There is no way to have PXE enable LACP, so as soon as the server reboots and goes into PXE, we lose connectivity. Even outside of PXE, if you take a typical ESXi server that has LACP turned on and then try to reinstall ESXi off a ISO image, you cannot configure LACP during the install, so the 10GbE ports will have no connectivity. Cisco, Arista and every other switch vendor we have seen has some kind of setting to turn on LACP fallback mode. On catalyst it is turned on by default. On nexus it is enabled with "lacp suspend-individual", etc., etc. It would be great to get some feedback from Netgear product management on this topic, as this greatly limits how we can adopt this switch in enterprise deployments. Thanks, FYI, I am waiting for a response before I post this on other forums and product reviews to make sure this is not a mistake or some kind of hidden feature that I could not find.Solved4KViews0likes11Comments