NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
m4300 m5300 mlag support
Are there any plans to support MLAG on the M4300 line of switches? We recently moved from m5300-52g3 to m4300-24x24f and while we are using stacking, support for mlag would be very useful.
The only post I could find mentioning the m4300 line and mlag was this result which states that m4300 doesn't support mlag but I'm hoping implies that at some point mlag support on m4300 will be "ready"
Keep hope alive or give up and find another way to lag across multiple stacks?
Hi mstinaff
Thank you for your message. There is no ongoing MLAG development for our M4300 line, instead we are working hard on other enhancements for M4300 (MLAG isn't ranked high amongst customer requests).
To LAG across several stacks certainly represents a challenge beyond <<STP at Layer 2 and VRRP at Layer 3>> limitations. At this stage, we can envision another tier, just above M4300 stacks, that would provide distributed LAG to your hosts, and distributed LAG to our M4300 stacks. But I understand this may modify your network topology.
Regards,
5 Replies
Hi mstinaff
Thank you for your message. There is no ongoing MLAG development for our M4300 line, instead we are working hard on other enhancements for M4300 (MLAG isn't ranked high amongst customer requests).
To LAG across several stacks certainly represents a challenge beyond <<STP at Layer 2 and VRRP at Layer 3>> limitations. At this stage, we can envision another tier, just above M4300 stacks, that would provide distributed LAG to your hosts, and distributed LAG to our M4300 stacks. But I understand this may modify your network topology.
Regards,
Thanks for the reply, just wish it was better news.
We are trying to avoid any single point of failure so if I understand your suggestion we would have another tier of redundant 10g switches to provide mlag to the servers and existing m4300 stacks which will be able to connect as though it is a normal single switch lacp lag, yes?
I'm not eager to justify the expense for another set of redundant 10g switches, Any other suggestions for approximating mlag functionality with a pair of m4300 stacks,
-a pair of m4300 10G stacks
-a m5300 L3 stack that was replaced by the m4300s (to get 10g)
-one xs712t switch that is currently serving as an aggregation switch of sorts
-a stack of m4300 1g switches
- Hi mstinaff
Based on your topology, yes I think the best move would be a new tier above all your existing stacks.
I would consider this as an aggregation upper layer, and use a pair of M4300 10G switches, stacked together and dedicated to it.
With Seamless Failover, this pair of 10G switches would never stop if all downlinks to your existing stacks are distributed across the two switches. This is distributed link aggregation, not MLAG. For these LAGs you should use LACP default hashing, or if you setup the same on your other stacks, more advanced hashing algorithm based on IP and TCP/UDP ports.
Last, don't forget to also use Distributed LAG on the other side (on your existing stacks) with the master switch, and the backup master switch each time.
With this mesh, all based on LACP, you would achieve real, unstoppable 10G aggregation.
I hope this helps!
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
