This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (EXOS/Switch Engine)
- Link Aggregation negotiate in half-duplex
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Link Aggregation negotiate in half-duplex
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-26-2019 04:02 PM
I configured two port in aggregation between a X440G2-24t-G4 and a Moxa EDR 810 both in static mode.
Everything seems working fine but the two ports of the Extreme switch negotiate in half-duplex (with show port information). However Moxa shows his two ports in full-duplex.
The command I used is: enable sharing 21 grouping 21-22
Is there any reason why this can happen?
Thanks
Andrea
Everything seems working fine but the two ports of the Extreme switch negotiate in half-duplex (with show port information). However Moxa shows his two ports in full-duplex.
The command I used is: enable sharing 21 grouping 21-22
Is there any reason why this can happen?
Thanks
Andrea
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-27-2019 02:53 PM
when you set up the aggregation on the EXOS side you can choose what algorithm to use for the share. This must be defined when you create the share. Default is layer 2 so looks at mac addresses only ... Best is layer 3 and 4 so it looks deeper into packets for the sharing hash. But ports share will never be equal and if you only have one client on one side and one on other side transferring file or streaming ect all flows will only be on one port not matter what. This is why we are moving from ten gig lag groups in our metro core to 100 gig links... even with 2500 active vlans and about 89000 macs in core you can still get enough traffic from some of the larger single ip routers to load up a single ten gig port in a 40 or 60 gig lag group.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-27-2019 04:34 PM
Thank you very much for the explanation. Actually I tested only with one client connected.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-27-2019 02:53 PM
when you set up the aggregation on the EXOS side you can choose what algorithm to use for the share. This must be defined when you create the share. Default is layer 2 so looks at mac addresses only ... Best is layer 3 and 4 so it looks deeper into packets for the sharing hash. But ports share will never be equal and if you only have one client on one side and one on other side transferring file or streaming ect all flows will only be on one port not matter what. This is why we are moving from ten gig lag groups in our metro core to 100 gig links... even with 2500 active vlans and about 89000 macs in core you can still get enough traffic from some of the larger single ip routers to load up a single ten gig port in a 40 or 60 gig lag group.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-27-2019 02:21 PM
Yes it is in the section of link aggregation (or port trunking) but it is only possible in static mode (LACP is not present). So I have configured ports sharing in static mode also on the Extreme switch.
Anyway after manually force both interfaces in both MOXA and Extreme to 100 Full Duplex (the maximum speed in MOXA), all links are established in 100Mb/s Full duplex. Probably the auto negotiation between these two model/brand is not working fine with the aggregation.
However after solving that I have realized that the traffic load is always in one link so the bandwidth is still 100Mb/s (not 200 Mb/s as I was expecting). I tested even between two extreme switch with the same configuration of the ports (100 Full).
Is this normal in the Extreme link aggregation?
Appreciate your support
Anyway after manually force both interfaces in both MOXA and Extreme to 100 Full Duplex (the maximum speed in MOXA), all links are established in 100Mb/s Full duplex. Probably the auto negotiation between these two model/brand is not working fine with the aggregation.
However after solving that I have realized that the traffic load is always in one link so the bandwidth is still 100Mb/s (not 200 Mb/s as I was expecting). I tested even between two extreme switch with the same configuration of the ports (100 Full).
Is this normal in the Extreme link aggregation?
Appreciate your support
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-27-2019 02:00 PM
Does the MOXA support a lag group? I just looked at their manual and did not see a way to set up a port lag group. Both side have to be able to do lag for this to work.. This is more than likely the issue
