NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Problems configuring multi-chassis LAG with STP to core router
I am trying to configure two M7100-24X in a configuration that looks exactly like this http://i.imgur.com/huVN2h9.png, ready to take to our datacenter and migrate our existing hosts onto it. The ...
Hi Eric,
Thanks for your reply.
I appears that I am on a newer firmware than that manual was written for.
I have consulted the manual for the latest firmware (the version I have installed), followed the configuration instructions as before and I am still facing the same issue.
Let's simplify the situation, as I get the feeling it requires the same solution.
I now have a setup which looks like the following:
dev1 ----- sw1 ===== sw2 ----- dev2
The sw1-sw2 peer link has been set as a LAG that was fully functioning before configuring the peer link.
I have also disabled STP on the LAG and member ports, despite the current manual suggesting that STP across the peer link is actually possible.
Now I am unable to ping across the link between dev1 and dev2 which are connected to plain (i.e. non-MLAG configured) ports.
Why isn't non-MLAG traffic able to cross the peer link? Presumably this is the same reason why in my previous post MLAG to gateway flows were not working depending on which switch they were sent to first.
Hi connorzc,
Thanks for your response immediately.
As you saied, you give us one simplistic situation, but it's a LAG situation, not same as MLAG situation. And the configuration is not same too.
In LAG situation, all member ports need to enable STP to prevent the loop.
Then you said unable to ping across the link between dev1 and dev2, I suggest you can check LAG status at first. To confirm whether the LAG status is up or not.
Thanks,
Eric
NETGEAR® Community Team
NETGEAR® Community Team
Hi Eric,
The set up is the same, just with different types of links attached to it.
From my first post, the main issue is where traffic that doesn't terminate at an MLAG won't cross the peer link.
Here is a reference diagram to go along with the various use cases I am trying to demonstrate below:
https://i.imgur.com/PRe9lv2.jpg
dev-3 > dev-4: works under all failure conditions where there is still a viable path
dev-4 > dev-3: works under all failure conditions where there is still a viable path
dev-1 > dev-2: doesn't work
dev-2 > dev-2: doesn't work
dev-1/2 > dev-3/4: works as long as dev-3/4.eth0 is up
dev-3/4 > dev-1/2: only works if bond0 hashes the flow down the link to the switch directly attached to the recipient e.g. dev-3/4.eth0 > dev-1 or dev-3/4.eth1 > dev-2
dev-3/4 > dev-5 only works if bond0 hashes the flow down the link to the switch which has it's link to dev-5 as the designated STP root port
dev-1/2 > dev-5 only works if the common switch's has it's link to dev-5 as the designated STP root port
I see no activity that suggests a loop has been formed at any point. The switches correctly designate STP root ports to create a non-looping path to dev-5.
I hope this helps describe exactly the issue I am having.
Connor
Hi connorzc,
Per your testbed topology, I have some question as below:
1. Have you create LAG with port eth0 and eth1 on dev-5? If so, you should config VPC3 on two MLAG switches;
2. If dev-5 does not support LAG, you should enable VRRP on two MLAG switches to Load Balance the traffic, and add all ports to same L3 VLAN interface, then set IP address for them;
3. You said dev-1 to dev-2 not work, do these two dev in same subnet or different subnet? Then we can confirm the traffic should accross via L3 or L2 network.
4. Would you please provide the configuration file for all switches? I think it will be helpful for us to debug.
Thanks,
Eric
NETGEAR® Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
