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 0C570D559 for ; Wed, 15 May 2013 18:18:30 +0000 (UTC) Received: (qmail 56795 invoked by uid 500); 15 May 2013 18:18:29 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 56755 invoked by uid 500); 15 May 2013 18:18:29 -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 56747 invoked by uid 99); 15 May 2013 18:18:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 May 2013 18:18:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aemneina@gmail.com designates 74.125.82.48 as permitted sender) Received: from [74.125.82.48] (HELO mail-wg0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 May 2013 18:18:24 +0000 Received: by mail-wg0-f48.google.com with SMTP id f11so1838113wgh.3 for ; Wed, 15 May 2013 11:18:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:reply-to:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=0Ff364FvoBKspWIt+fiPWbxcta026wYm3Z0qYP317G4=; b=hXde8O9QrnQC7ZO9+wgi9kDfh731CFKO0RPnsa4HKDUbuOGhiYVmC9uTBwDVj55Pu4 lzyqaiF9JaJRqj0FgK0HcGw2JJYi0/+Zk33wB+dhT3Qc+p9ED7iigPVNgM8QKjGt4exH nzIUtVS+wnfKaYVtDh8UZ71LotGrfmY1GkzHXLOvcuS3hTNJwTAHcHwy78XByBe6hwWn HsW9dMqS1VvB+PiEgnpoH4suiVf70lDoj0/9YdeUlEkjJmMutuW13NWdVv6FFkdSx1lf LLMBqlcXA/ilvnACJoJXJflVMLEUSloWVXjcJqkZ9GXS+x/Ck24oB7ykJcOPxtt0E3jF bzTw== X-Received: by 10.180.185.179 with SMTP id fd19mr16781878wic.1.1368641883698; Wed, 15 May 2013 11:18:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.93.196 with HTTP; Wed, 15 May 2013 11:17:43 -0700 (PDT) Reply-To: aemneina@gmail.com In-Reply-To: References: <82864f5afcc549deaf5d174231de6959@QCMS.qwertyc.local> From: Ahmad Emneina Date: Wed, 15 May 2013 11:17:43 -0700 Message-ID: Subject: Re: Working with clouds on multiple ESX hosts To: Stanley Kaytovich Cc: "users@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=001a11c25e4c4d7fd404dcc5c5a7 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c25e4c4d7fd404dcc5c5a7 Content-Type: text/plain; charset=ISO-8859-1 I forgot to reply all so the group see's my answer: i see. so for trunk2, you want to trunk your zone vlans (that were defined in cloudstack for the advanced,guest networks) to it. you should see the portgroup being created on vswitch1, for the guest network. if that vlan is present on all hosts, and switchports, you should be good to go. On Tue, May 14, 2013 at 3:45 PM, Stanley Kaytovich wrote: > 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 >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: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 > > > > > > > > > > --001a11c25e4c4d7fd404dcc5c5a7--