Hi guys, Thanks, this clears it more why we have VM and display options and how it's used on the nics. What hapens with me on a 3.2 installation when I want to attach a network without IP (VM option or not) to a Nic I get the noticed error like I told before: Error while executing action Setup Networks: Illegal or Incomplete IP Address Here is the error from the log: eth2 {id=713f2687-6d84-4010-9076-fbfc67cf6831, vdsId=033febb8-4f52-4253-bb6d-a8807816affd, name=eth2, macAddress=00:1c:c4:d8:cb:36, networkName=LAN_TEST, bondName=null, bootProtocol=NONE, address=, subnet=, gateway=null, mtu=0, bridged=false, speed=1000, type=0, networkImplementationDetails=null}], removedNetworks=[], removedBonds=[]), log id: 7a99dbd1 2013-02-12 23:31:08,783 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] (ajp--127.0.0.1-8702-10) [7289062c] FINISH, SetupNetworksVDSCommand, log id: 7a99dbd1 2013-02-12 23:31:09,796 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (ajp--127.0.0.1-8702-10) [7289062c] org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Specified netmask or gateway but not ip 2013-02-12 23:31:09,797 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (ajp--127.0.0.1-8702-10) [7289062c] Command SetupNetworksVDS execution failed. Exception: VDSNetworkException: VDSGenericException: VDSNetworkException: Specified netmask or gateway but not ip 2013-02-12 23:31:09,798 ERROR [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand] (ajp--127.0.0.1-8702-10) [7289062c] Command org.ovirt.engine.core.bll.network.host.SetupNetworksCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Specified netmask or gateway but not ip Why does this happen on None Bootproto or DHCP ? 2013/2/12 Moti Asayag <masayag@redhat.com>
On 02/11/2013 12:37 PM, Matt . wrote:
I'm struggeling setting up my network in oVirt at the moment as I would like to seperate specific VM's from other devices/clients in my network.
You should define the 'logical networks' which describe the networks of your setup. See the response to Nicolas on this thread of the steps to achieve it. If wish to create a network dedicated to storage which shouldn't allow VMs to use it, it should be defined as non-vm network. Once the network is assigned to a cluster, you can add new network interface to your VMs which defines to which bridges (vm networks) they are connected: hence, segregating the VMs is done by the vlan-id of the bridge the VMs are connected to.
I have decent setup switching network using Vlans, this is also the fact for ovirt and the storage nodes where teh ports are seperated between storage and management.
Because I want to manage which client can acces which VM I need Vlan tagging. The question is where are we going to do this, on the VM itself or on the network I attach the VM's Nic to.
Because of the lacking documentation at this point it's not clear, so I would like to figure out and maybe change the wiki there.
I also cannot understand why I can set an IP to a network and only the subnet where I also can set DHCP which puts also the gateway.
The default gateway can be provided for the management network only. You can define its IP address either as static by providing its known IP address or letting it determine the address from the DHCP server. You cannot select 'None' as boot-protocol for the management network since then the engine will not be able to communicate with the host.
However you can select 'none' boot-protocol to any other networks if wishes.
I'm not able to set None or DHCP and can only add a network with IP, but what IP and why ? Or just a 192.16.x.0 with a 255.255.255.0 subnet ?
I hope someone can clear this a little bit more out.
Thanks!
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users