Project

General

Profile

Bug #9447

Configuring LAGG at XG-7100 Switch Ports Broken

Added by DRago_Angel [InV@DER] about 2 months ago. Updated about 2 months ago.

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

0%

Estimated time:
Affected Version:
2.4.x
Affected Architecture:

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.

History

#1 Updated by DRago_Angel [InV@DER] about 2 months ago

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

#2 Updated by Daniele Palumbo about 2 months 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

#3 Updated by DRago_Angel [InV@DER] about 2 months 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.

Also available in: Atom PDF