| So, I have effectively brought up my network with Xenserver. The VMs spin up fine, no issues other than CPVM not allowing me to do a graphical install of Centos 6.3. For grins, I took 2 hosts and converted them to KVM. Setup the bonds exactly like Xenserver. The network storms reappear.
This is an incredibly strange problem to have.
Trevor Francis Partner 46 Labs | The PeerEdge Cloud 405-362-0046 - Voice | 405-410-4980 - Cell trevorgfrancis - Skype Solutions Provider for the Telecom Industry
You might also want to hop on irc (irc.freenode.net) in the #cloudstack
channel, for some closer to 'real time' help.
On 11/2/12 10:20 AM, "Ahmad Emneina" <[email protected]> wrote:
Your public network comes in through the router, correct? If that’s the
case, make the switchport the router connects to an access port on vlan
10. Then you can trunk 10 to the other ports, and use that vlan within
cloudstack to define and access the public network. I believe you will
also need to define your private network on the switch and have it route
traffic out through the router. I use poweredge 6200's they're different
to configure than the 5200 series.
On 11/2/12 5:38 AM, "Trevor Francis" <[email protected]> wrote:
So, I have added vlan 10 to all the ports on the switch, including port 1
which is connected to the router. Does the router need to be VLAN aware?
If so, that might be a problem as it belongs to my ISP.
Does anyone have experience with Dell power edge switches as it pertains
to a cloud stack setup?
Regards,
Trevor Francis (mobile)
On Nov 2, 2012, at 12:05 AM, Ahmad Emneina <[email protected]>
wrote:
The docs don¹t explicitly say don¹t install CSP for advanced installs.
It
does speak to it being a step in the basic zone installation section.
Trevor, I think youre on the right track to getting your cat pelt. I do
this exact same thing in a couple clouds I have provisioned. Make sure
VLAN 10 has an interface on your switch that routes, giving the vlan
interface an ip address to be used as the gateway for your shared
network.
On 11/1/12 8:59 PM, "Trevor Francis"
<[email protected]>
wrote:
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.
TGF
On Nov 1, 2012, at 10:55 PM, Kirk Kosinski <[email protected]>
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"
<[email protected]> wrote:
Have you installed the XenServer Cloud Support Pack (CSP)?
----------------------------------------
From: "Trevor Francis" <[email protected]>
Sent: Friday, November 02, 2012 2:24 PM
To: "[email protected]"
<[email protected]>
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
--
Æ
--
Æ
--
Æ
|
