RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1364275 - Unable to set up mtu on bonded interface in RHEL 7.2
Summary: Unable to set up mtu on bonded interface in RHEL 7.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Rashid Khan
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-04 22:29 UTC by Saul Serna
Modified: 2019-11-14 08:53 UTC (History)
6 users (show)

Fixed In Version: NetworkManager-1.4.0-0.2.git20160621.072358da.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 19:27:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2581 0 normal SHIPPED_LIVE Low: NetworkManager security, bug fix, and enhancement update 2016-11-03 12:08:07 UTC

Description Saul Serna 2016-08-04 22:29:55 UTC 
ISSUE:
======
- Unable to set MTU on bond device.
- Already running newer NetworkManager release below based on:

  https://access.redhat.com/solutions/1309583

RUNNING:       NetworkManager-1.0.6-30.el7_2.x86_64
RECOMMENDED:   NetworkManager-1.0.6-27.el7 or later

- Adjusting the MTU manually appears to work:

[root@newanaly ~]# ip link set dev bond0 mtu 9000
[root@newanaly ~]# ip link set dev vlan53 mtu 9000



REPRODUCTION/TESTING:
=====================
Seems this is a bug.

I only could set the MTU if I add a "BOOTPROTO=dhcp" on ifcfg-bond0.

# grep "MTU\|BOOTPROTO" /etc/sysconfig/network-scripts/ifcfg-bond*
/etc/sysconfig/network-scripts/ifcfg-bond0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth1:MTU="9000"

# for dev in eth0 eth1 bond0; do ip l show dev $dev; done
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff
7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff

# echo "BOOTPROTO=dhcp" >> /etc/sysconfig/network-scripts/ifcfg-bond0

# reboot

# for dev in eth0 eth1 bond0; do ip l show dev $dev; done
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff
7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT 
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff

# grep "MTU\|BOOTPROTO" /etc/sysconfig/network-scripts/ifcfg-bond*
/etc/sysconfig/network-scripts/ifcfg-bond0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond0:BOOTPROTO=dhcp
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth1:MTU="9000"

And the "BOOTPROTO" must be "dhcp" or "static".

--- As 'dhcp':

# sed -i "s/^BOOTPROTO=.*$/BOOTPROTO=none/g" /etc/sysconfig/network-scripts/ifcfg-bond0

# grep "MTU\|BOOTPROTO" /etc/sysconfig/network-scripts/ifcfg-bond*
/etc/sysconfig/network-scripts/ifcfg-bond0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond0:BOOTPROTO=none
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth1:MTU="9000"

# reboot

# for dev in eth0 eth1 bond0; do ip l show dev $dev; done
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:1a:bb:9f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:1a:bb:9f brd ff:ff:ff:ff:ff:ff
7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 00:16:3e:1a:bb:9f brd ff:ff:ff:ff:ff:ff

--- As 'static' is not necessary set a IP address. The MTU of the bond0 is configured as 9000, but the devices eth0 and eth1 are not configured.

# sed -i "s/^BOOTPROTO=.*$/BOOTPROTO=static/g" /etc/sysconfig/network-scripts/ifcfg-bond0

# reboot

# grep "MTU\|BOOTPROTO" /etc/sysconfig/network-scripts/ifcfg-bond*
/etc/sysconfig/network-scripts/ifcfg-bond0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond0:BOOTPROTO=static
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth0:MTU="9000"
/etc/sysconfig/network-scripts/ifcfg-bond-slave-eth1:MTU="9000"

# for dev in eth0 eth1 bond0; do ip l show dev $dev; done
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:1a:bb:9f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 00:16:3e:31:c5:0f brd ff:ff:ff:ff:ff:ff
7: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 9000 qdisc noqueue state DOWN mode DEFAULT 
    link/ether 9e:c8:27:9d:f2:3e brd ff:ff:ff:ff:ff:ff
Comment 2 Beniamino Galvani 2016-08-05 07:37:44 UTC 
Tried on RHEL 7.3, NetworkManager-1.4.0-0.4.git20160727.9446481f.el7,
the bond and vlan interfaces get the correct MTU:

6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether 52:54:00:a4:80:fb brd ff:ff:ff:ff:ff:ff
7: vlan53@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether 52:54:00:a4:80:fb brd ff:ff:ff:ff:ff:ff

The issue was fixed by commit [1] for bug 1303968, which is quite
similar to this. But probably it's wise not to close this as duplicate
so the different scenario (bond + vlan) gets tested by QE as well.

[1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=53dfaddda2adad15f4fbf35780bc03503cc45a63
Comment 4 Vladimir Benes 2016-08-26 20:16:04 UTC 
mtu can be set correctly to bridged bond
Comment 6 errata-xmlrpc 2016-11-03 19:27:58 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2581.html
Note You need to log in before you can comment on or make changes to this bug.