Project

General

Profile

Actions

Bug #9447

closed

Configuring LAGG at XG-7100 Switch Ports Broken

Added by DRago_Angel [InV@DER] over 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Start date:
04/01/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.x
Affected Architecture:
All

Description

XG-7100 Switch Ports Lagg Table https://pfsense/switch_ports.php is broken.
When user assign lagg1 on port 3,4 this ports will be added to lagg1, but they will also be added to UPLINK lagg0 (which must have only 9,10 ports - each is 2,5G controller).
This will endup in network loop and pfSense will lose network connectivity even if in ETH3-ETH4 no cables actually was even plugged in.
Additionaly if user try create lagg2 with ports 5,6 then they will be added to lagg2, but they will also be added to:
  1. lagg1 (where alredy ports 3,4 wass exists)
  2. UPLINK lagg0.

More new ports at laggs3,4 will appier at laggs with lower number to.

Temporary workaround:
Use console (over USB-COM port, or SSH but with caution) and use Shell command to configure XG-7100 Switch Ports.
Example for create lagg1 with port 3,4 and lagg2 with ports 5,6 run 2 commands:
etherswitchcfg laggroup1 members 3,4
etherswitchcfg laggroup2 members 5,6

Additional request:
  1. Add information about LAGG column - what accepted number of LAGGs for one port can be configured at once (I think it only 1).
  2. Add some caution that chaning LAGG can lead to loops. Specially if user or system will modify ports9,10/lagg0.
  3. Add some exception wich will not allow save switch configuration if any of ports from 1 to 8 will be configured to lagg0.

Files

9447-fix_2.4.4-p3.diff (932 Bytes) 9447-fix_2.4.4-p3.diff Jim Pingle, 08/26/2019 01:29 PM
Actions #1

Updated by DRago_Angel [InV@DER] over 2 years ago

https://forum.netgate.com/user/stephenw10 said that this wass been fixed already in 2.5.

Actions #2

Updated by Daniele Palumbo over 2 years ago

+1 as i was about to report the same bug.
I think the following is the fix, applicable to 2.4.4p2
https://forum.netgate.com/post/834455

Actions #3

Updated by DRago_Angel [InV@DER] over 2 years ago

Daniele Palumbo wrote:

+1 as i was about to report the same bug.
I think the following is the fix, applicable to 2.4.4p2
https://forum.netgate.com/post/834455

I know because I am in that topic too.

Actions #4

Updated by Blaine Palmer over 2 years ago

I recently updated our XG-7100 and before attempting to apply the patch in the associated forum post I checked the existing switch.inc. It appears this patch was applied in 2.4.4p3 already, however when using the UI if I put any number in the LAGG column and click save it still comes back with all 0 and I lose LAN connectivity.

I'd really like to get LAGG working with an external switch to allow for more throughput between segments.

Actions #5

Updated by Jim Thompson over 2 years ago

  • Target version set to 2.5.0
  • Affected Architecture All added
  • Affected Architecture deleted ()
Actions #6

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Feedback
  • Assignee set to Jim Pingle
  • % Done changed from 0 to 100

I pushed a fix for this, will be in snaps soon

Actions #7

Updated by Blaine Palmer over 2 years ago

Jim Pingle wrote:

I pushed a fix for this, will be in snaps soon

Thank you very much. Any chance a patch can be made available for 2.4.4 p3?

Actions #8

Updated by Jim Pingle over 2 years ago

Patched attached for those who would like to test this against 2.4.4-p3.

Actions #9

Updated by Jim Pingle about 2 years ago

  • Target version changed from 2.5.0 to 2.4.5
Actions #10

Updated by Chris Linstruth almost 2 years ago

Setting 7 and 8 to lagg group 1 results in:
laggroup0:
members 9,10
laggroup1:
members 7,8

Setting 5 and 6 to lagg group 2 results in:
laggroup0:
members 9,10
laggroup1:
members 7,8
laggroup2:
members 5,6

Clearing the laggs results in:
laggroup0:
members 9,10

Looks good.

Actions #11

Updated by Jim Pingle almost 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF