Ahmad, I configured trunking on the switch for 8 ports. Each host has 4 physical NICs, so 8 ports are in a trunk on the switch. Still no network connectivity.
:-/ -----Original Message----- From: Ahmad Emneina [mailto:aemne...@gmail.com] Sent: Tuesday, May 14, 2013 4:35 PM To: Cloudstack users mailing list Subject: Re: Working with clouds on multiple ESX hosts Sounds like youre not trunking the zone vlans to all the switchports your hosts connect to. Can you verify the vlans are trunked, then see if your networking starts working? On Tue, May 14, 2013 at 1:28 PM, Stanley Kaytovich <stanl...@qwertyc.com>wrote: > Hello, > > This is more of a general question pertaining to best practices of how > everyone works with multiple ESX hosts in a cloudstack zone. It seems > that if a VM instance resides on a different host from other > instances, there is no networking ability on the alienated > instance(s). Since the hosts are chosen automatically, occasionally > instances are created on an alternate host and the instance boots up > without networking. Adding a tag in the computer offering is a way of > forcing instances to be created on a particular hosts, though that requires > additional offerings for every host. > > Using a dvSwitch would be great, though on 4.0.2 I do not believe it > is supported or I am unable to find any documentation to prove me otherwise. > > What is the best practice or workaround for this? > > - Stan >
