Configuring LAGG at XG-7100 Switch Ports 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:
- lagg1 (where alredy ports 3,4 wass exists)
- UPLINK lagg0.
More new ports at laggs3,4 will appier at laggs with lower number to.
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
- Add information about LAGG column - what accepted number of LAGGs for one port can be configured at once (I think it only 1).
- Add some caution that chaning LAGG can lead to loops. Specially if user or system will modify ports9,10/lagg0.
- Add some exception wich will not allow save switch configuration if any of ports from 1 to 8 will be configured to lagg0.
#4 Updated by Blaine Palmer over 1 year 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.
#10 Updated by Chris Linstruth 9 months ago
Setting 7 and 8 to lagg group 1 results in:
Setting 5 and 6 to lagg group 2 results in:
Clearing the laggs results in: