Created attachment 786946 [details] log_collector Description of problem: If host is to be added over bridgeless VLAN, host installation fails with following error: Failed to configure management network on host dell-06 due to setup networks failure. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.15.master.el6ev OS Version: RHEL - 6Server - 6.4.0.4.el6 Kernel Version: 2.6.32 - 358.el6.x86_64 VDSM Version: vdsm-4.12.0-61.git8178ec2.el6ev How reproducible: 100% Steps to Reproduce: 1. Create DC with bridgeless VLAN tagged network management network (rhevm) 2. Configure VLAN at host manually 3. Install host into RHEVM over the VLAN configured above Actual results: Host dell-06 installation failed. Failed to configure management network on the host. Expected results: Host installation successfull, rhevm interface configured Additional info: configuration file used to create VLAN interface on host DEVICE=em1.172 VLAN=yes BOOTPROTO=dhcp engine.log 2013-08-15 15:55:56,850 ERROR [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-5-thread-50) Host installation failed for host 4e6285d9-b595-4f84-9289-d443dd5ec6c7, dell-06.: org.ovirt.engine.core.bll.InstallVdsCommand$VdsInstallException: Failed to configure management network on the host at org.ovirt.engine.core.bll.InstallVdsCommand.configureManagementNetwork(InstallVdsCommand.java:306) [bll.jar:] at org.ovirt.engine.core.bll.InstallVdsCommand.installHost(InstallVdsCommand.java:205) [bll.jar:] at org.ovirt.engine.core.bll.InstallVdsCommand.executeCommand(InstallVdsCommand.java:105) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1130) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1215) [bll.jar:] vdsm.log Thread-15::ERROR::2013-08-15 15:55:55,245::API::1262::vds::(setupNetworks) Determining IP information for em1.172... failed. Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1260, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/share/vdsm/supervdsm.py", line 50, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (29, 'Determining IP information for em1.172... failed.')
Martin, Could you try the same scenario with a vm network and see if the host is able to obtain an ip address for this VLAN ?
(In reply to Moti Asayag from comment #1) > Martin, > > Could you try the same scenario with a vm network and see if the host is > able to obtain an ip address for this VLAN ? Yes, this works.
Gathering relevant information from the logs: Engine.log setupNetworks command parameters for configuring the management network: networks=[rhevm {id=98c85123-b4a2-4237-8f62-8288e8b51e1c, description=Management Network, comment=null, subnet=null, gateway=null, type=null, vlanId=172, stp=false, dataCenterId=97338a92-4571-43eb-b291-5cb9453badfa, mtu=0, vmNetwork=false, cluster=NetworkCluster {id={clusterId=null, networkId=null}, status=OPERATIONAL, display=false, required=true, migration=false}, providedBy=null, label=null}], em1.172 {id=84da9a52-4bed-46af-a7c4-b0051e287fcd, vdsId=256d07d2-25c8-469b-9d67-7293dd75dda6, macAddress=null, networkName=rhevm, vlanId=172, bonded=null, bondName=null, bondOptions=null, bootProtocol=DHCP, address=10.34.67.66, subnet=255.255.255.224, gateway=null, mtu=1500, bridged=false, speed=null, type=0, networkImplementationDetails=null}], There are additional 3 interfaces which are configured with BOOTPROTO=DHCP: p1p2 {id=dbd56731-c67e-4b36-b17a-12c252f6e456, vdsId=256d07d2-25c8-469b-9d67-7293dd75dda6, macAddress=90:e2:ba:04:28:c1, networkName=null, vlanId=null, bonded=null, bondName=null, bondOptions=null, bootProtocol=DHCP, address=, subnet=, gateway=null, mtu=1500, bridged=false, speed=1000, type=0, networkImplementationDetails=null}, em1 {id=2ba7134a-9443-44f8-916f-75ca0262652d, vdsId=256d07d2-25c8-469b-9d67-7293dd75dda6, macAddress=d0:67:e5:f0:83:5e, networkName=null, vlanId=null, bonded=null, bondName=null, bondOptions=null, bootProtocol=DHCP, address=10.34.66.61, subnet=255.255.255.0, gateway=null, mtu=1500, bridged=false, speed=1000, type=0, networkImplementationDetails=null}, em2 {id=8214b529-c224-4a8a-9643-352402f11f85, vdsId=256d07d2-25c8-469b-9d67-7293dd75dda6, macAddress=d0:67:e5:f0:83:5f, networkName=null, vlanId=null, bonded=null, bondName=null, bondOptions=null, bootProtocol=DHCP, address=, subnet=, gateway=null, mtu=1500, bridged=false, speed=1000, type=0, networkImplementationDetails=null}, The engine.log indicates the setupNetworks command fails when trying to obtain an IP address from the DHCP server for em1: 2013-08-15 15:47:10,531 ERROR [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand] (pool-5-thread-45) Command org.ovirt.engine.core.bll.network.host.SetupNetworksCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to SetupNetworksVDS, error = Determining IP information for em1... failed. (Failed with error unexpected and code 16) In another attempt the action fails with the same parameters due to: 2013-08-15 15:55:56,808 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] (pool-5-thread-50) Command SetupNetworksVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to SetupNetworksVDS, error = Determining IP information for em1.172... failed. From VDSM.log: Host capabilities which indicates the management network should be created on top of em.172 device: Thread-14::DEBUG::2013-08-15 15:44:54,855::BindingXMLRPC::981::vds::(wrapper) return getCapabilities with {'status': {'message': 'Done', 'code': 0}, 'info': {'HBAInventory': {'iSCSI': [{'InitiatorName': 'iqn.1994-05.com.redhat:a77ef67146b2'}], 'FC': []}, 'packages2': {'kernel': {'release': '358.el6.x86_64', 'buildtime': 1359456461.0, 'version': '2.6.32'}, 'spice-server': {'release': '12.el6_4.2', 'buildtime': 1371724647L, 'version': '0.12.0'}, 'vdsm': {'release': '61.git8178ec2.el6ev', 'buildtime': 1376390441L, 'version': '4.12.0'}, 'qemu-kvm': {'release': '2.355.el6_4.5', 'buildtime': 1369322701L, 'version': '0.12.1.2'}, 'libvirt': {'release': '18.el6_4.9', 'buildtime': 1371761993L, 'version': '0.10.2'}, 'qemu-img': {'release': '2.355.el6_4.5', 'buildtime': 1369322701L, 'version': '0.12.1.2'}, 'mom': {'release': '3.el6ev', 'buildtime': 1375261095L, 'version': '0.3.2'}}, 'cpuModel': 'Intel(R) Xeon(R) CPU E31240 @ 3.30GHz', 'hooks': {}, 'cpuSockets': '1', 'vmTypes': ['kvm'], 'supportedProtocols': ['2.2', '2.3' ], 'networks': {}, 'bridges': {}, 'uuid': '4C4C4544-0037-5410-8033-C4C04F39354A', 'lastClientIface': 'em1.172', 'nics': {'em1': {'netmask': '255.255.255.0', 'addr': '10.34.66.61', 'hwaddr': 'd0:67:e5:f0:83:5e', 'cfg': {'IPV6INIT': 'yes', 'NM_CONTROLLED': 'yes', 'MTU': '1500', 'HWADDR': 'D0:67:E5:F0:83:5E', 'BOOTPROTO': 'dhcp', 'DEVICE': 'em1', 'TYPE': 'Ethernet', 'ONBOOT': 'yes', 'UUID': 'b58311e4-aa7b-49ac-b91c-09303c259324'}, 'ipv6addrs': [], 'speed': 1000, 'mtu': '1500'}, 'em2': {'netmask': '', 'addr': '', 'hwaddr': 'd0:67:e5:f0:83:5f', 'cfg': {'UUID': 'bfc4f231-78e4-4fb7-91f8-298a15ec610e', 'NM_CONTROLLED': 'yes', 'HWADDR': 'D0:67:E5:F0:83:5F', 'BOOTPROTO': 'dhcp', 'DEVICE': 'em2', 'TYPE': 'Ethernet', 'ONBOOT': 'no'}, 'ipv6addrs': [], 'speed': 1000, 'mtu': '1500'}, 'p1p1': {'netmask': '', 'addr': '', 'hwaddr': '90:e2:ba:04:28:c0', 'cfg': {'UUID': '9fe5c2e9-b1a2-40fc-81e4-2e78be110efa', 'NM_CONTROLLED': 'yes', 'HWADDR': '90:E2:BA:04:28:C0', 'BOOTPROTO': 'dhcp', 'DEVICE': 'p1p1', 'TYPE': 'Ethernet', ' ONBOOT': 'no'}, 'ipv6addrs': [], 'speed': 1000, 'mtu': '1500'}, 'p1p2': {'netmask': '', 'addr': '', 'hwaddr': '90:e2:ba:04:28:c1', 'cfg': {'UUID': '40dfaa85-07dd-4153-9aad-10b98c1a0294', 'NM_CONTROLLED': 'yes', 'HWADDR': '90:E2:BA:04:28:C1', 'BOOTPROTO': 'dhcp', 'DEVICE': 'p1p2', 'TYPE': 'Ethernet', 'ONBOOT': 'no'}, 'ipv6addrs': [], 'speed': 1000, 'mtu': '1500'}}, 'software_revision': '61', 'management_ip': '0.0.0.0', 'clusterLevels': ['3.0', '3.1', '3.2', '3.3'], 'cpuFlags': u'fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,xtopology,nonstop_tsc,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,sse4_1,sse4_2,x2apic,popcnt,tsc_deadline_timer,aes,xsave,avx,lahf_lm,ida,arat,epb,xsaveopt,pln,pts,dts,tpr_shadow,vnmi,flexpriority,ept,vpid,model_Nehalem,model_Conroe,model_coreduo,model_core2duo,model_Penryn,model_Westmere,model_n270,model_ SandyBridge', 'ISCSIInitiatorName': 'iqn.1994-05.com.redhat:a77ef67146b2', 'netConfigDirty': 'False', 'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3'], 'reservedMem': '321', 'bondings': {'bond4': {'netmask': '', 'addr': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'ipv6addrs': [], 'mtu': '1500'}, 'bond0': {'netmask': '', 'addr': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'ipv6addrs': [], 'mtu': '1500'}, 'bond1': {'netmask': '', 'addr': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'ipv6addrs': [], 'mtu': '1500'}, 'bond2': {'netmask': '', 'addr': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'ipv6addrs': [], 'mtu': '1500'}, 'bond3': {'netmask': '', 'addr': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'ipv6addrs': [], 'mtu': '1500'}}, 'software_version': '4.12', 'memSize': '7862', 'cpuSpeed': '3301.000', 'version_name': 'Snow Man', 'vlans': {'em1.172': {'netmask': '255.255.255.224', 'iface': 'em1', 'addr': '10.34.67.66', 'cfg': {'DEVICE' : 'em1.172', 'VLAN': 'yes', 'BOOTPROTO': 'dhcp'}, 'ipv6addrs': [], 'mtu': '1500'}}, 'cpuCores': '4', 'kvmEnabled': 'true', 'guestOverhead': '65', 'supportedRHEVMs': ['3.0'], 'cpuThreads': '8', 'emulatedMachines': [u'rhel6.4.0', u'pc', u'rhel6.3.0', u'rhel6.2.0', u'rhel6.1.0', u'rhel6.0.0', u'rhel5.5.0', u'rhel5.4.4', u'rhel5.4.0'], 'operatingSystem': {'release': '6.4.0.4.el6', 'version': '6Server', 'name': 'RHEL'}, 'lastClient': '10.34.63.69'}} setupNetworks parameters: Thread-15::DEBUG::2013-08-15 15:44:54,989::BindingXMLRPC::974::vds::(wrapper) client [10.34.63.69]::call setupNetworks with ({'rhevm': {'nic': 'em1', 'bootproto': 'dhcp', 'vlan': '172', 'bridged': 'false'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}) {} Thread-15::ERROR::2013-08-15 15:45:36,236::API::1262::vds::(setupNetworks) Determining IP information for em1... failed. Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1260, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/share/vdsm/supervdsm.py", line 50, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (29, 'Determining IP information for em1... failed.') Thread-15::DEBUG::2013-08-15 15:45:36,255::BindingXMLRPC::981::vds::(wrapper) return setupNetworks with {'status': {'message': 'Determining IP information for em1... failed.', 'code': 29}} same error goes for the second attempt for the em.172 device: Thread-15::ERROR::2013-08-15 15:55:55,245::API::1262::vds::(setupNetworks) Determining IP information for em1.172... failed. Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1260, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/share/vdsm/supervdsm.py", line 50, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (29, 'Determining IP information for em1.172... failed.') Thread-15::DEBUG::2013-08-15 15:55:55,250::BindingXMLRPC::981::vds::(wrapper)
The relevant piece from /var/log/messages for the DHCP request failures: Aug 15 15:55:08 dell-r210ii-06 ntpd[5438]: Deleting interface #10 em1.172, 10.34.67.66#123, interface stats: received=0, sent=2, dropped=0, active_time=131 secs Aug 15 15:55:09 dell-r210ii-06 dhclient[396]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x570ae497) Aug 15 15:55:09 dell-r210ii-06 kernel: device-mapper: table: 253:3: multipath: error getting device Aug 15 15:55:09 dell-r210ii-06 kernel: device-mapper: ioctl: error adding target to table Aug 15 15:55:09 dell-r210ii-06 kernel: device-mapper: table: 253:3: multipath: error getting device Aug 15 15:55:09 dell-r210ii-06 kernel: device-mapper: ioctl: error adding target to table Aug 15 15:55:10 dell-r210ii-06 kernel: bnx2 0000:02:00.0: em1: NIC Copper Link is Up, 1000 Mbps full duplex Aug 15 15:55:10 dell-r210ii-06 kernel: ADDRCONF(NETDEV_CHANGE): em1: link becomes ready Aug 15 15:55:10 dell-r210ii-06 kernel: ADDRCONF(NETDEV_CHANGE): em1.172: link becomes ready Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: dhclient(949) is already running - exiting. Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: This version of ISC DHCP is based on the release available Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: on ftp.isc.org. Features have been added and other changes Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: have been made to the base software release in order to make Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: it work better with this distribution. Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: Please report for this software via the Red Hat Bugzilla site: Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: http://bugzilla.redhat.com Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: Aug 15 15:55:10 dell-r210ii-06 dhclient[966]: exiting. Aug 15 15:55:11 dell-r210ii-06 dhclient[949]: DHCPREQUEST on em1.172 to 255.255.255.255 port 67 (xid=0x46c5e373) Aug 15 15:55:12 dell-r210ii-06 dhclient[396]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x570ae497) Aug 15 15:55:15 dell-r210ii-06 dhclient[396]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x570ae497) Aug 15 15:55:18 dell-r210ii-06 dhclient[949]: DHCPREQUEST on em1.172 to 255.255.255.255 port 67 (xid=0x46c5e373) Aug 15 15:55:21 dell-r210ii-06 dhclient[396]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 6 (xid=0x99bc7dc) Aug 15 15:55:27 dell-r210ii-06 dhclient[396]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 7 (xid=0x99bc7dc) Aug 15 15:55:31 dell-r210ii-06 dhclient[949]: DHCPDISCOVER on em1.172 to 255.255.255.255 port 67 interval 8 (xid=0x321530d2) Aug 15 15:55:34 dell-r210ii-06 dhclient[396]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 10 (xid=0x99bc7dc) Aug 15 15:55:39 dell-r210ii-06 dhclient[949]: DHCPDISCOVER on em1.172 to 255.255.255.255 port 67 interval 14 (xid=0x321530d2) Aug 15 15:55:44 dell-r210ii-06 dhclient[396]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 12 (xid=0x99bc7dc) Aug 15 15:55:44 dell-r210ii-06 dhclient[396]: DHCPOFFER from 10.34.67.29 Aug 15 15:55:44 dell-r210ii-06 dhclient[396]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x99bc7dc) Aug 15 15:55:44 dell-r210ii-06 dhclient[396]: DHCPACK from 10.34.67.29 (xid=0x99bc7dc) Aug 15 15:55:46 dell-r210ii-06 NET[1013]: /sbin/dhclient-script : updated /etc/resolv.conf Aug 15 15:55:46 dell-r210ii-06 dhclient[396]: bound to 10.34.67.2 -- renewal in 334961 seconds. Aug 15 15:55:47 dell-r210ii-06 ntpd[5438]: Listening on interface #11 em2, 10.34.67.2#123 Enabled Aug 15 15:55:53 dell-r210ii-06 dhclient[949]: DHCPDISCOVER on em1.172 to 255.255.255.255 port 67 interval 17 (xid=0x321530d2) Aug 15 15:55:53 dell-r210ii-06 dhclient[949]: DHCPOFFER from 10.34.67.93 Aug 15 15:55:53 dell-r210ii-06 dhclient[949]: DHCPREQUEST on em1.172 to 255.255.255.255 port 67 (xid=0x321530d2) Aug 15 15:55:53 dell-r210ii-06 dhclient[949]: DHCPACK from 10.34.67.93 (xid=0x321530d2) Aug 15 15:55:55 dell-r210ii-06 NET[1085]: /sbin/dhclient-script : updated /etc/resolv.conf Aug 15 15:55:55 dell-r210ii-06 dhclient[949]: bound to 10.34.67.66 -- renewal in 295341 seconds. Aug 15 15:55:55 dell-r210ii-06 vdsm vds ERROR Determining IP information for em1.172... failed.#012Traceback (most recent call last):#012 File "/usr/share/vdsm/API.py", line 1260, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/share/vdsm/supervdsm.py", line 50, in __call__#012 return callMethod()#012 File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (29, 'Determining IP information for em1.172... failed.') Aug 15 15:55:56 dell-r210ii-06 ntpd[5438]: Listening on interface #12 em1.172, 10.34.67.66#123 Enabled
Martin, could you repeat the command vdsClient -s 0 "{rhevm:{nic:em1,bootproto:dhcp,vlan:172,bridged:false}" from the command line and report the content of your /etc/sysconfig/network-scripts/ifcfg-em1* after that? (not that vdsm is expected to keep its modification of the file, instead of reverting them as it does when Engine sends the command). If the dhcp failure reproduces, please try to re-request it manually, with ifup em1.172
if ifcfg-em1.172 misses the BOOTPROTO line, this is a dup of bug 980174.
(In reply to Dan Kenigsberg from comment #5) > Martin, could you repeat the command > > vdsClient -s 0 "{rhevm:{nic:em1,bootproto:dhcp,vlan:172,bridged:false}" > > from the command line and report the content of your > /etc/sysconfig/network-scripts/ifcfg-em1* after that? (not that vdsm is > expected to keep its modification of the file, instead of reverting them as > it does when Engine sends the command). > > If the dhcp failure reproduces, please try to re-request it manually, with > > ifup em1.172 unfortunately this command is incomplete vdsClient -s 0 "{rhevm:{nic:em1,bootproto:dhcp,vlan:172,bridged:false}"
(In reply to Dan Kenigsberg from comment #6) > if ifcfg-em1.172 misses the BOOTPROTO line, this is a dup of bug 980174. after host install failure BOOTPROTO is present in ifcfg file
For the receord, I've meant the complete command vdsClient -s 0 setupNetworks networks="{rhevm:{nic:em1,bootproto:dhcp,vlan:172,bridged:false}}"
After maximal isolation of other possible causes by configuring all other interfaces to be down and have BOOTPROTO=none, it was confirmed that is a dup of bug 980174 ifcfg files before host installation: [root@dell-r210ii-06 ~]# cat /etc/sysconfig/network-scripts/ifcfg-* DEVICE="em1" BOOTPROTO="none" IPV6INIT="no" ONBOOT="yes" DEFROUTE="no" DEVICE="em1.172" VLAN="yes" ONBOOT="yes" DEFROUTE="yes" BOOTPROT="yes" DEVICE="em2" BOOTPROTO="none" IPV6INIT="no" ONBOOT="no" DEFROUTE="no" DEVICE="p1p1" BOOTPROTO="none" IPV6INIT="no" ONBOOT="no" DEFROUTE="no" DEVICE="p1p2" BOOTPROTO="none" IPV6INIT="no" ONBOOT="no" DEFROUTE="no" ifcfg file after installation: [root@dell-r210ii-06 ~]# cat /etc/sysconfig/network-scripts/ifcfg-em1.172 # Generated by VDSM version 4.12.0-138.gitab256be.el6ev DEVICE=em1.172 ONBOOT=yes VLAN=yes DEFROUTE=yes NM_CONTROLLED=no BOOTPROTO is missing *** This bug has been marked as a duplicate of bug 980174 ***