Why nmcli fails to autostart VLAN interface created on top bonded device in RHEL7?

Solution In Progress - Updated -

Issue

  • We have used the following steps to create a bond and a vlan interface on top of it:
mkdir /etc/sysconfig/network-scripts/backup
mv /etc/sysconfig/network-scripts/ifcfg-enp5s0f0 /etc/sysconfig/network-scripts/backup
mv /etc/sysconfig/network-scripts/ifcfg-enp5s0f1 /etc/sysconfig/network-scripts/backup

bonding
nmcli con add type bond con-name bond0 ifname bond0 mode 802.3ad
nmcli con mod bond0 ipv4.method disabled
nmcli con mod bond0 ipv6.method ignore
nmcli con add type bond-slave ifname enp5s0f0 master bond0
nmcli con add type bond-slave ifname enp5s0f1 master bond0

nmcli con up bond0

vlan
nmcli con add type vlan con-name bond0.84 ifname bond0.84 dev bond0 id 84
nmcli con up bond0.84
  • But the bonded VLAN will not auto start after reboot.
  • How to make the vlan interface persistently active?

Environment

  • Red Hat Enterprise Linux(RHEL)7.0
  • nmcli utility.
  • Bonding.
  • Vlan tagging.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content