Should we configure underlying interface of VLAN to be up on boot or not?
Issue
- Should we configure underlying interface of VLAN to be up on boot or not?
- If a physical device (eg:
eth0) hasONBOOT=nobut the VLAN interface (eg:eth0.100) hasONBOOT=yes, the underlying device comes up when VLAN interface comes up. - Do we need to set the underlying physical device to
ONBOOT=yeswhen that physical device has VLANs attached to it?
Environment
- Red Hat Enterprise Linux 6
- 802.1q VLAN Tagging
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.