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 C8563119BA for ; Fri, 5 Sep 2014 10:04:36 +0000 (UTC) Received: (qmail 80737 invoked by uid 500); 5 Sep 2014 10:04:25 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 80674 invoked by uid 500); 5 Sep 2014 10:04:25 -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 80662 invoked by uid 99); 5 Sep 2014 10:04:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Sep 2014 10:04:24 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=AC_DIV_BONANZA,FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kurushi4000@gmail.com designates 209.85.216.41 as permitted sender) Received: from [209.85.216.41] (HELO mail-qa0-f41.google.com) (209.85.216.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Sep 2014 10:04:19 +0000 Received: by mail-qa0-f41.google.com with SMTP id m5so10903537qaj.28 for ; Fri, 05 Sep 2014 03:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=OLVz7bLOHURE/kFCdCPA+GyEpDOzNFhmOtjIhsYy2rA=; b=qmSeQWFRssSj2pI5JJJ0MpV6GMphGjQloLfOeEu8sJwfQOMxJZhMWE7dvRS9wLgywH 5e7voKvSFeOlpTqCeqGSGpdI4Sg91hZJJlmdbOi3f4RyyOsuAKibSuwJjIN1IMR9VgAs 7zeTHmZAUpnTL1Fd1G4CT7LB70aQwcmqB0c8bmhcvLo7j3im+1IA/vZ5D6bAKgjnPirt TUdJyDYZhbpNUsQ4Iw6MRFihEgxZrrdeQgktlCw2gHw6cMJ+GYMr9+jrZ+feUoxLRaOU 9aWLBTkbtiG3739ciEWSxTF0ne5hqkpcgtEFUdjPVSEd74ExJu+BlYTBoEjlp6FLCGRa JT9w== MIME-Version: 1.0 X-Received: by 10.224.161.11 with SMTP id p11mr16765097qax.40.1409911438638; Fri, 05 Sep 2014 03:03:58 -0700 (PDT) Received: by 10.96.159.7 with HTTP; Fri, 5 Sep 2014 03:03:58 -0700 (PDT) Date: Fri, 5 Sep 2014 12:03:58 +0200 Message-ID: Subject: Netscaler & VPC and multiple inter tiers LB From: benoit lair To: users@cloudstack.apache.org Content-Type: multipart/alternative; boundary=089e0149d2e877077a05024e96b2 X-Virus-Checked: Checked by ClamAV on apache.org --089e0149d2e877077a05024e96b2 Content-Type: text/plain; charset=UTF-8 Hello Folks, I'm testing Netscaler VPX with acs 4.3. I have several VPCs deployed into my cloud. I would like to get my netscaler working with my vpcs. So from what i have tested, it seems that : - i can't share a VPX with more than one VPC ? - in order to get my netscaler working with my vpc, i need to declare it "dedicated". So it can't be used both with vpc tiers and isolated networks ? - i can use netscaler with a vpc only with "public" tier (means external tier) Can you confirm these limitations, or is it due to a misconfiguration of my own networks offerings ? So another question is : How can i achieve ns-lb with several tiers in a vpc ? I have a vpc with web-tier, app-tier and sql-tier : how can i have in the same time, nslb between outside and web-tier, nslb between web-tier and app-tier and nslb between app-tier and sql-tier, having only one VPX ? Thanks four your lights. Regards, Benoit. --089e0149d2e877077a05024e96b2--