Fedi, I need more details to answer that completely, but it works as folowing:
- if you use UNTAGGED vlan inside ACS when defining Public network/range (and still use vlan) - this means you have to manually provision vlan/bridge interface on your physical hosts (ACS will just plug VNIC to the brige/traffic label you provided during creating Public netowrk). Other possibility is: you dont do manuall tagging of vlan interface - you let ACS do it (prefered from my perspective, because of some bugs that I experienced with previous/untagged solution) This means i.e. you have eth0/cloudbr2 - your Public network uses i.e. vlan 160, and you configure vlan 160 inside ACS while adding public IP range - here ACS will extract child interface (eth0) from the provided parent interface/traffic label (cloudbr2), and then ACS will create eth0.160 interface, and create a new bridge (and joing eth0.160 and all public vNICs to this bridge...) If you can share more details, if would be good. Cheers On 9 July 2015 at 15:28, Fedi Ben Ali <[email protected]> wrote: > Hi, > > I want to configure one cloudstack zone with two public ip ranges each one > is configured on a vlan (this configuration is already made on my network > equipement). > > as we know when i define my public network i will point it to a network > already configured on my xenserver hosts. > > my question is this , > > when i configure the network on th hosts and i set the vlan as untagged > ,and when i add the ip ranges to my cloudstack zone i specify the vlan id > to each range,does this work ? > > Thx. > -- Andrija Panić
