Erdősi,
Thank you for reply. But where do I tell CS what is my public
interface? When I configure advanced networking at CS I do set up:
1. Physical network name (I have 1 interface, so put just name "single").
Isolation method = VLAN (default)
2. Management XenServer traffic label: cloud-mgmt, Public XenServer traffic
label: cloud-public, Guest label: cloud-guest.
All three labels must be defined as network names at XenServer.
Even more – each network should be assigned with VLAN ID with „xe vlan-create…
“ otherwise I get „null pointer exception“. So, as I understand, XenServer
networking must be configured prior to set up CS advanced networking.
Regards,
Vadim.
-----Original Message-----
From: Erdősi Péter [mailto:f...@niif.hu]
Sent: Tuesday, September 30, 2014 2:14 AM
To: users@cloudstack.apache.org
Subject: Re: XenServer : VLAN logic at CS 4.4
2014.09.29. 16:54 keltezéssel, Vadim Kimlaychuk írta:
> I am trying to understand the logic of cloudstack for creating VLANs at
> XenServer 6.2. I have configured XenServer to use with advanced networking.
> Have followed these steps (basically for public VLAN):
I think, you fall into the same trap, as me before. "You tried to create a VLAN
on top of another VLAN - use the underlying physical PIF/bond instead"
So... You don't need to add any vlan interface on physical.
When you tell the CS, your public physical interface is XYZ, and when setup the
network, and type in the vlan id, the CS management server will be create vlan
tagget subinterface on XYZ physical... (the name will be like this:
VLAN-12f51238-cc75-42c6-b5a0-c0a3cb32bf01-108) which is for vlan 108.
Regards,
Peter
