Project

General

Profile

Bug #6014

Changing active LAGG configuration orphans VLANs on it

Added by Hiroki Yamamoto about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
03/19/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

Test case:

1x Netgate SG-2440 (pfSense 2.2.6)
1x Cisco SG-30028 managed L2 switch
2x Client laptops, plugged into the switch

On each client laptop, a ping to their respective gateway (the pfSense node, both client nodes are on different VLANS. Each VLAN is configured on LAGG0) keeps running for the duration of the test case.

Configuration:
pfSense:
- igb1+igb2+igb3 in 1 LAGG named 'LAGG0'
- LAGG configured in LACP mode

Cisco switch:
- GE22+GE23+GE24 in 1 LAGG named 'LAG0'
- LAGG configured in LACP mode

Reproduction steps (see attached screenshots for visual confirmation):
- Login to pfSense web interface
- Click on 'interfaces'
- Click on LAGG
- Edit an active LAGG configuration
- Remove or add a parent interface from or to the LAGG
-- In my scenario, I removed igb3 from the LAGG0 configuration
- Click on save

Result - after clicking on save:
- The running pings from the client laptops to their gateways (the pfSense node) stop immedeately
- pfSense seems to not be participating anymore in any of the VLANs configured on the LAGG
- the LAGG seems to have stopped functioning alltogether

Steps to fix it:
- Restart the pfSense node

Untitled.png (44.7 KB) Untitled.png Hiroki Yamamoto, 03/19/2016 12:17 PM
Untitled 2.png (147 KB) Untitled 2.png Hiroki Yamamoto, 03/19/2016 12:17 PM

Associated revisions

Revision ac387383 (diff)
Added by Chris Buechler about 3 years ago

Reconfigure any VLANs with a lagg parent after recreating the lagg. Ticket #6014

History

#1 Updated by Chris Buechler about 3 years ago

  • Subject changed from Changing active LAGG configuration breaks network configuration to Changing active LAGG configuration orphans VLANs on it
  • Status changed from New to Confirmed
  • Affected Version changed from 2.2.x to All
  • Affected Architecture deleted (amd64)

Subject is root issue (at least as it stands today in 2.3, haven't looked back further but probably same previously)

#2 Updated by Chris Buechler about 3 years ago

  • Status changed from Confirmed to Feedback
  • Assignee set to Chris Buechler
  • Target version set to 2.3

fixed

#3 Updated by Chris Buechler about 3 years ago

  • Status changed from Feedback to Resolved

works

Also available in: Atom PDF