Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1415DB95 for ; Tue, 14 May 2013 22:45:52 +0000 (UTC) Received: (qmail 1064 invoked by uid 500); 14 May 2013 22:45:52 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 1014 invoked by uid 500); 14 May 2013 22:45:52 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 1000 invoked by uid 99); 14 May 2013 22:45:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 22:45:51 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stanleyk@qwertyc.com designates 208.65.145.82 as permitted sender) Received: from [208.65.145.82] (HELO p02c12o149.mxlogic.net) (208.65.145.82) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 22:45:45 +0000 Received: from unknown [96.56.210.44] (EHLO mail.qwertyc.com) by p02c12o149.mxlogic.net(mxl_mta-7.1.0-2) over TLS secured channel with ESMTP id 28eb2915.0.5812.00-375.13403.p02c12o149.mxlogic.net (envelope-from ); Tue, 14 May 2013 16:45:24 -0600 (MDT) X-MXL-Hash: 5192be84640664a2-82e1f64aa313e4a4406cc1f262c7521119b429c0 Received: from QCMS.qwertyc.local (10.0.0.102) by QCMS.qwertyc.local (10.0.0.102) with Microsoft SMTP Server (TLS) id 15.0.516.32; Tue, 14 May 2013 18:45:01 -0400 Received: from QCMS.qwertyc.local ([fe80::d928:6f04:9f25:b35a]) by QCMS.qwertyc.local ([fe80::d928:6f04:9f25:b35a%13]) with mapi id 15.00.0516.029; Tue, 14 May 2013 18:45:00 -0400 From: Stanley Kaytovich To: "users@cloudstack.apache.org" , "aemneina@gmail.com" Subject: Re: Working with clouds on multiple ESX hosts Thread-Topic: Working with clouds on multiple ESX hosts Thread-Index: Ac5Q4MNotPemYRtLTO+FC2HGCBctTQAI1McAAAbQ3gD//9idAIAAQgng///KGYD//8Xigg== Date: Tue, 14 May 2013 22:45:00 +0000 Message-ID: References: <82864f5afcc549deaf5d174231de6959@QCMS.qwertyc.local> , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-AnalysisOut: [v=2.0 cv=caRlWA/M c=1 sm=1 a=8KRzRNRZIU/iNS3VKDv8hw==:17 a] X-AnalysisOut: [=E34oGv-KBsMA:10 a=nTqLj3QoI-4A:10 a=BLceEmwcHowA:10 a=8nJ] X-AnalysisOut: [EP1OIZ-IA:10 a=xqWC_Br6kY4A:10 a=c0_gJ9tDAAAA:8 a=n8i27M1m] X-AnalysisOut: [AAAA:8 a=bLBNgvusP30A:10 a=pGLkceISAAAA:8 a=L39yOscdAF7Niz] X-AnalysisOut: [8RmH8A:9 a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10 a=5KMYdd3WEfQ] X-AnalysisOut: [A:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SOURCE-IP: [96.56.210.44] X-Virus-Checked: Checked by ClamAV on apache.org 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 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 wr= ote: > 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 tru= nk > 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:aemneina@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 >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:aemneina@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 > > > >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 > > > > > >