cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Trevor Francis <>
Subject Re: Xenserver Shared Public Network
Date Fri, 02 Nov 2012 03:59:43 GMT
Hmm, that isn't represented in the docs (3.02 or 4.0)… Not quite sure how to remove it.

Yes, I am running an advanced network because I have 3 physical bonds on my hosts and it is
my intent to direct assign a public ip address and a private ip address to my VMs.

Is there a better way to skin a cat? I can't do NAT because of the nature of the application
deployed over the cloud instances.


On Nov 1, 2012, at 10:55 PM, Kirk Kosinski <> wrote:

> Hi, Trevor.  Are you using a basic zone with Security Groups?  It sounds
> like you aren't since you mentioned creating multiple shared networks.
> You should not install the CSP on XS hosts in an advanced zone or a
> basic zone without SGs.  Doing so can result in network connectivity
> issues for VMs.
> Best regards,
> Kirk
> On 11/01/2012 08:42 PM, Trevor Francis wrote:
>> yeap.
>> On Nov 1, 2012, at 10:38 PM, "Kristoffer Sheather - Cloud Central" <>
>>> Have you installed the XenServer Cloud Support Pack (CSP)?
>>> ----------------------------------------
>>> From: "Trevor Francis" <>
>>> Sent: Friday, November 02, 2012 2:24 PM
>>> To: "" 
>>> <>
>>> Subject: Xenserver Shared Public Network
>>> So, I abandoned KVM due to Bonding floods that the community was unable to 
>>> resolve. I have no idea why it was happening.
>>> Anyway. I am now on XS 6.02 and trying to deploy my network. I have created 
>>> a shared public network and a shared private network. I have both VLANS in 
>>> my switches (10 = public, and 11 = private). There is a VR for the shared 
>>> public network, just being used to hand out dhcp. The guest VMs can get out 
>>> on the isolated private network, but are unable to get out on the shared 
>>> public network. Both networks are able to pull dhcp from their respective 
>>> virtual routers.
>>> The VMs cannot ping any system VMs (even though they reside on the same 
>>> physical host) and the host cannot ping the vms. 
>>> Any thoughts?
>>> TGF

View raw message