RHEL6: Sporadically VLAN interfaces are not configured after system reboot.

Solution Verified - Updated -

Issue

  • Sporadically VLAN interfaces are not configured after system reboot.
  • Sporadically VLAN interfaces are not configured for be2net driven NIC-ports after a system reboot. On a system two VLANs were configured on eth2 (eth2.353 and eth2.354) . They got their IP-addresses over DHCP and were working well. After 2-3 reboots none of the eth2 interfaces came up. The file /etc/udev/rules.d/70-persistent-net.rules contained an entry for eth2.354 and in /var/log/messages you can find entries like "udev:renamed network interface eth0 to eth2.354" etc. The command ifup eth2 aborted with

    Device eth2 does not seem to be present, delaying initialization
    

but lspci displayed all network interfaces. When removing the eth2.354 entrie from the persistent network rules and reboot of the system, the interfaces were up and running again.

Environment

  • Red Hat Enterprise Linux (RHEL) 6
  • be2net network driver
  • package initscripts version between 9.03.23-1.el6 (part of RHEL6.1GA) and 9.03.38-1.el6 (part of RHEL6.4GA)

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