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 4ACF9F66A for ; Fri, 22 Mar 2013 19:10:54 +0000 (UTC) Received: (qmail 86079 invoked by uid 500); 22 Mar 2013 19:10:53 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 86035 invoked by uid 500); 22 Mar 2013 19:10:53 -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 86027 invoked by uid 99); 22 Mar 2013 19:10:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Mar 2013 19:10:53 +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 (nike.apache.org: domain of aemneina@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-we0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Mar 2013 19:10:46 +0000 Received: by mail-we0-f178.google.com with SMTP id o45so3534869wer.37 for ; Fri, 22 Mar 2013 12:10:26 -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=6u87hrJNBnnglGY0ERkL2VesK7DD+z3WtCh+jNRus7w=; b=s3NrAw8rVyFem0H+J/CJ7uzprQzmt7T7AZ0lbk40UriS0dHvy03vXcIURf13/Zchh1 VOv77+P1HMt1BQb9r7ACSbbSZsNRgoJLZpEvtR5/tP2b6FCXnu7UjgZBTno5S+GallHI E1D8B2xpuzR6rL7DByo7wwv0GSktGvH+VITwQqbA585lUoZmvE6HC8luVwLL3G7L7N8v YzGU3WXgjIjs4H76eGUm0w0+dAOpylEmaenqmDVfPCW8VtvuUWc3BlTYCl7R3t+70Dco iV9PPvXfYNXySO48v9SjCdpo6fNSlMCqbIqxmQmVQBr5W1hd6KBcHUhJqJMLS/Gr+zWm 8GKA== X-Received: by 10.180.82.33 with SMTP id f1mr13286104wiy.13.1363979426493; Fri, 22 Mar 2013 12:10:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.98.232 with HTTP; Fri, 22 Mar 2013 12:10:06 -0700 (PDT) Reply-To: aemneina@gmail.com In-Reply-To: References: From: Ahmad Emneina Date: Fri, 22 Mar 2013 12:10:06 -0700 Message-ID: Subject: Re: Cluster With two XenServer To: tawfiq zidi Cc: Cloudstack users mailing list Content-Type: multipart/alternative; boundary=f46d041826da32801e04d8883508 X-Virus-Checked: Checked by ClamAV on apache.org --f46d041826da32801e04d8883508 Content-Type: text/plain; charset=ISO-8859-1 Hey Tawfq, It could be a switch configuration issue. Make sure you trunk what you defined for your zone vlans, to each physical switch port the xen hosts are connected to. The guests get their private l2 network created by pulling from a pool you define in the zone vlan range... On Fri, Mar 22, 2013 at 12:06 PM, tawfiq zidi wrote: > Yes, this deployed with advanced configuration. Even , i checked the setup > configuration and i found that guest traffic is enabled. > > The problem that router DHCP discover available only within the hosts not > all the cluster , so the other XenServers in the pool can't see anything > from the router. > > So , is there any others configurations have to be done for XenServers > Pool ? > > > On Fri, Mar 22, 2013 at 7:05 PM, Ahmad Emneina wrote: > >> Is this using a basic or advanced zone. This is definitely NOT how it >> should work :) >> >> VM's across a zone, within the same account, should be able to reach each >> other... when deployed to the same network. >> >> >> On Fri, Mar 22, 2013 at 10:53 AM, tawfiq zidi >> wrote: >> >> > Hi, >> > >> > I've Created XenServer Cluster with two Host ( XS 6.0.2 ) , the system >> VMs >> > ( ssvm and cpvm ) and virtual router are created fine in the first host, >> > and I've succeded to launch VMs in the first host. >> > >> > But when I tried to launch VMs in the second Host, the VMs always >> remains >> > unreachable . >> > I've checked the traffic connection and I found that the VMs in the >> Second >> > host can't reach the Virtual router in the First Host , because the VM >> and >> > Virtual Router are in seperate Link local network. So that why the VMs >> in >> > the Second Host will not get an IP address after a DHCP discover from >> the >> > Virtual Router. >> > >> > My question is : is it a normal behavior that within a cluster , a VM >> in a >> > Host B can't reach a virtual router in a Host A., did I miss some >> > configuration in creating a pool of XenServer ? >> > >> > >> > Best Regards. >> > >> > > --f46d041826da32801e04d8883508--