NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4300, LAG and LACP issues
Greetings!
My issue is a little bit difficult to explain, hope it is understandable:
We are using 2 x M4300-24XF in a stacked configuration. I am trying to connect these two switches to two FS 40 GBit switches. the ports on the FS switches are split into 4x10GBit using MTP cables.
The FS switches are using MLAG, Both 40Gbit ports make up one channel-group.
Left Netgear is connected using 4x10GBit to left FS (interfaces 2/0/14-2/0/16).
Right Netgear is connected using 4x10GBit to right FS (interfaces 1/0/14-1/0/16)..
A LAG is configured on Netgear side with all 8 ports (4 left, 4 right).
When connecting left Netgear with left FS only, the LAG is coming up.
When connecting right Netgear with right FS only, the LAG is coming up.
When connecting left and right Netgear to its counterpart on FS side, only one "side" of the LAG is coming up - depending on which Netgear has been plugged in earlier to the FS. For the Netgear connected second, the following messages appear in the log:
| <12> Jun 27 10:36:43 rack04-sw02-2 DOT3AD[dot3ad_core_lac]: dot3ad_lacp.c(2294) 2536182 %% Interface 2/0/14 partner priority 32768 is not same as existing members of LAG interface lag 8 (32768). Not adding interface 2/0/14 as active member of LAG interface lag 8. |
| <12> Jun 27 10:36:43 rack04-sw02-2 DOT3AD[dot3ad_core_lac]: dot3ad_lacp.c(2294) 2536181 %% Interface 2/0/16 partner priority 32768 is not same as existing members of LAG interface lag 8 (32768). Not adding interface 2/0/16 as active member of LAG interface lag 8. |
| <12> Jun 27 10:36:43 rack04-sw02-2 DOT3AD[dot3ad_core_lac]: dot3ad_lacp.c(2294) 2536180 %% Interface 2/0/13 partner priority 32768 is not same as existing members of LAG interface lag 8 (32768). Not adding interface 2/0/13 as active member of LAG interface lag 8. |
<12> Jun 27 10:36:43 rack04-sw02-2 DOT3AD[dot3ad_core_lac]: dot3ad_lacp.c(2294) 2536179 %% Interface 2/0/15 partner priority 32768 is not same as existing members of LAG interface lag 8 (32768). Not adding interface 2/0/15 as active member of LAG interface lag 8.
|
When reverting the order in which the Netgears are connected to the FS switches, the same messages appear, just the interface numbers change.
As a result, only one Netgear only works in that LAG.
Any hints?
1 Reply
inhouse-support wrote:
40 GBit switches. the ports on the FS switches are split into 4x10GBit using MTP cables.
The FS switches are using MLAG, Both 40Gbit ports make up one channel-group.
The primary requirement for a LAG config is that all links are using the same speed and latency. This appears not to be given in your deployment. Is it correct you have no 40G port on the Netgear stack?
If configuring -one- (M)LAG spanning all four 10 G ports, the LAG can (in my opinion and understanding at least) not come up, magically combining four 10 G links into one LAG. Curious what Netgear engineers think about this....
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
