Project

General

Profile

Feature #25092

Allow changing MTU of lagg interface

Added by Mike Ely over 2 years ago. Updated 7 months ago.

Status:
Done
Priority:
Nice to have
Assignee:
Ryan Moeller
Category:
OS
Target version:
Estimated time:
Severity:
Low
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

Host has two VLAN interfaces running on an LACP LAGG. Upon rebooting from the update, networking was not online. This could be corrected by running through IPV4 params on one of the VLAN interfaces without making changes, causing networking to reload. I've repeated this by rebooting.

Will happily gather needed logs - say what you require.


Related issues

Related to FreeNAS - Bug #19544: lagg0 network configuration must be manually reset on reboot to restore connectivityResolved2016-12-12
Related to FreeNAS - Bug #25134: LAGG broken after upgradeClosed: Behaves correctly2017-07-13
Related to FreeNAS - Feature #29094: Add field for MTU config on network interfaces to legacy UIPassed Testing

History

#1 Updated by Dru Lavigne over 2 years ago

  • Category changed from 1 to 129
  • Assignee changed from Release Council to Alexander Motin

Sasha, looks like there is still an issue here.

Mike: please attach a debug (System -> Advanced -> Save Debug). The ticket will be marked private until the developer has a chance to review your debug.

#2 Updated by Dru Lavigne over 2 years ago

  • Related to Bug #19544: lagg0 network configuration must be manually reset on reboot to restore connectivity added

#3 Updated by Mike Ely over 2 years ago

  • File debug-a.attic-20170712084629.tgz added

Debug attached. Thanks for looking into this.

#4 Updated by Dru Lavigne over 2 years ago

  • Private changed from No to Yes

#5 Updated by Mike Ely over 2 years ago

I have it working right. Saw Bug #24849 where the fix was to change the MTU configuration so that it exists on the interfaces rather than the LAGG. In this case, the MTU was actually configured on the VLAN ints under options. Followed the instructions on the attached bug and the host boots with networking online.

It looks like this was a case of "I configured it wrong." Since this seems to be cropping up here and there, perhaps the right way to normalize this from a UI standpoint might be to have an explicit MTU option in the interface configuration, thereby avoiding/preventing further user error.

#6 Updated by Dru Lavigne over 2 years ago

  • Related to Bug #25134: LAGG broken after upgrade added

#7 Updated by Alexander Motin over 2 years ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Nice to have
  • Target version set to 11.1

After William added added protection against setting MTU on LAGG interfaces this could be just closed, but I'll probably take a look whether we could allow MTU setting on LAGG.

#8 Updated by Alexander Motin about 2 years ago

  • Target version changed from 11.1 to 11.2-BETA1

#9 Updated by Alexander Motin almost 2 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from After updating from a2dc21583 to aa82cc58d, network requires manual start to Allow MTU control on LAGG interface
  • Seen in deleted (11.0)
  • ChangeLog Required deleted (No)

Reclassify this as feature request.

#10 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 2 years ago

  • Target version changed from 11.2-BETA1 to 11.3

#11 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 2 years ago

  • Status changed from Screened to Not Started

#12 Updated by Alexander Motin over 1 year ago

  • Related to Feature #29094: Add field for MTU config on network interfaces to legacy UI added

#13 Updated by Alexander Motin over 1 year ago

  • Severity set to Low

#14 Avatar?id=13649&size=24x24 Updated by Ben Gadd over 1 year ago

  • Target version changed from 11.3 to Backlog

#15 Updated by Alexander Motin about 1 year ago

  • Status changed from Not Started to Unscreened
  • Assignee changed from Alexander Motin to Ryan Moeller

Ryan, would be nice to have this fixed to avoid specific hack in middleware. IIRC lagg locking was modified in 12, so not sure work done can be merged to 11, but 12 may be good too.

#16 Updated by Ryan Moeller about 1 year ago

  • Status changed from Unscreened to In Progress

#18 Updated by Ryan Moeller about 1 year ago

  • File deleted (debug-a.attic-20170712084629.tgz)

#19 Updated by Ryan Moeller about 1 year ago

  • Private changed from Yes to No

This feature has landed upstream in head, and I plan to backport it to 11-stable as well.

#20 Updated by Ryan Moeller 11 months ago

The feature was MFC'd to 12 and 11, so we shall have it in our tree when our next merge from upstream occurs.

#21 Updated by Alexander Motin 11 months ago

I've just merged fresh FreeBSD stable/11 including the lagg patch to freenas/11-stable.
https://github.com/freenas/os/commit/14ae9290a5d68c0ffce7a838ceb620bbef2caed0

#22 Updated by Ryan Moeller 11 months ago

  • Status changed from In Progress to Ready for Testing
  • Needs Merging changed from Yes to No

#24 Updated by Dru Lavigne 11 months ago

  • Subject changed from Allow MTU control on LAGG interface to Allow changing MTU of lagg interface

#26 Updated by Dru Lavigne 10 months ago

  • Target version changed from Backlog to 11.3

#29 Updated by Dru Lavigne 10 months ago

  • Target version changed from 11.3 to 11.3-BETA1

#30 Updated by Dru Lavigne 9 months ago

  • Needs QA changed from Yes to No

#32 Updated by Dru Lavigne 9 months ago

  • Status changed from Ready for Testing to Done
  • Needs Doc changed from Yes to No

#34 Updated by Dru Lavigne 7 months ago

  • Target version changed from 11.3-BETA1 to 11.3-ALPHA1

Also available in: Atom PDF