Ahmad, Each host has a total of 8 physical nics.
2 Nics for management (vswitch0) (trunk1) 4 nics for public (vswitch1) (trunk2) 2 10gbe nics for storage (separate switch) 0 nics for guests - also tried 1 separate nic and got same results -Stan Ahmad Emneina <aemne...@gmail.com> wrote: I was talking about physical switchports and trunks. How many nics do your esx hosts have? Do the vSwitches correspond to different pysical nics, or do they all map to 1 nic? On Tue, May 14, 2013 at 2:42 PM, Stanley Kaytovich <stanl...@qwertyc.com>wrote: > Ahmad, > > Actually, I misspoke, there are 6 ports on each host, but our switch only > allows 8 ports in a trunk. If I understand you correctly, I created a trunk > on our switch for vSwitch1 (8 ports). > > Below is our vSwitch configuration in CloudStack/vCenter: > > vSwitch0 - management (excluded from trunk) > vSwitch1 - public > vSwitch2 - storage (excluded from trunk) > vSwitch3 - guests (excluded from trunk) > > Regards, > Stan > > -----Original Message----- > From: Ahmad Emneina [mailto:aemne...@gmail.com] > Sent: Tuesday, May 14, 2013 5:30 PM > To: Cloudstack users mailing list > Subject: Re: Working with clouds on multiple ESX hosts > > what vlans are you trunking to the hosts? what vlans are you using in > cloudstack as your zone vlans? > > > On Tue, May 14, 2013 at 2:22 PM, Stanley Kaytovich <stanl...@qwertyc.com > >wrote: > > > 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 > > > > > >
