NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LAGG / LACP with MS510TXM
I've been struggling for a few days now with this.
I have a Netgear R8000 running a custom firmware (FreshTomato, in case anyone is wondering) and a MS510TXM running the latest firmware (1.0.5.10).
I am trying to create a dynamic link aggregation between two ports on the R8000 (1 Gbps each) and two ports on the MS510TXM, but failed miserably.
How I have it set up - on the MS510TXM:
- Switching - LAG - LAG configuration - edit a predefined one (ch1): set LAG type to LACP, all other options default (Admin Mode enabled, Hash Mode 1, STP Mode Disable, Link Trap Enable)
- then in the same window - LAG Membership: check the boxes for the two ports in question (1 and 2), click Apply.
In the Switching - Ports, the two ports (mg1, mg2) show as "Trunk Member" and "Link Up".
I didn't touch anything in the VLAN configuration on the MS510TXM.
How I have it set up - on the R8000:
- selected two ports for link aggregation (LAN port 2 and port 3) and set them into two separate VLANs (vlan3 and vlan4) as indicated at https://openlinksys.info/forum/viewthread.php?thread_id=21132 (I assume this is because there's no way to identify those ports "directly" from the web interface)
- rebooted the R8000, then configured manually (the "linkagg" script is seemingly broken), as follows:
modprobe bonding
ip link set bond0 down
echo 4 > /sys/class/net/bond0/bonding/mode
echo 1 > /sys/class/net/bond0/bonding/lacp_rate
echo 50 > /sys/class/net/bond0/bonding/miimon
echo 1 > /sys/class/net/bond0/bonding/xmit_hash_policy
ip link set bond0 up
echo +vlan3 > /sys/class/net/bond0/bonding/slaves
echo +vlan4 > /sys/class/net/bond0/bonding/slaves
brctl addif br0 bond0
- everything looks OK on the R8000 up to this point.
In the Switching - LAG - LAG Configuration, the two ports appear under "Active ports" for the respective LAG (ch1)
-- if I put the LAG Type to "LACP" on the MS510TXM, the LAG State is "Link Down", no matter what.
-- if I put the LAG Type to "Static" on the MS510TXM, the LAG State goes to "Link Up"; however, I can only ping from one to the other when one of the cables is plugged on both ends (if I plug in both, no ping)
I tested with different cables, different ports on the two devices, swapping things around - no luck.
Any ideas?
2 Replies
hetf,
Welcome to the community! 🙂
- if I put the LAG Type to "LACP" on the MS510TXM, the LAG State is "Link Down", no matter what.
-- if I put the LAG Type to "Static" on the MS510TXM, the LAG State goes to "Link Up"
It seems that the R8000 which is running a custom firmware FreshTomato does NOT support LACP. Hence, it ONLY supports Static LAG.
For you to be able to test if LACP works on the MS510TXM, I suggest you try to configure another switch that supports LACP (like another MS510TXM) and connect the corresponding LACP ports that you have configured on both switches. Otherwise, if you are ok with static LAG between the R8000 and the MS510TXM, then that's alright.
Regards,
DaneA
NETGEAR Community Team
Hi DaneA and thanks for the reply!
I would be OK with static LAG, if only it worked. Unfortunately, I don't have another device to test with (as Microsoft removed LACP support from Win 11).
I think I mentioned it in the post - when I set it to Static 802.3ad, the link does go up, but it seems to be limited to a single connection.
If I unplug the "working" cable, the connection doesn't fail over to the other one - which kind of defeats the whole purpose of LAG, I think.
Later edit: this post by Shibby (the author of the original Tomato alternate firmware, hence someone I would consider knowledgeable) hints that LACP works on Tomato (FreshTomato is a more recent fork).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
