Hi, Your public network also has a Traffic Label, pointing towards a certain interface/bridge in XenServer. If you specify no vlan, CloudStack will assume it is untagged. You can then still point towards an interface/bridge that is tagged with a vlan. The alternative is to point towards a more generic interface/bridge (that has no vlan in XenServer) and specify a vlan tag in CloudStack. CloudStack will then create an the interface with the vlan on top of it. Be sure not to create a vlan tag ontop of interface/bridge that already has a vlan (as this will obviously not work).
Long story short: it depends on how your XenServers can plug vifs into the public network. Regards, Remi > On 2 jul. 2015, at 16:31, Fedi Ben Ali <ben.ali.fe...@gmail.com> wrote: > > Hello, > > On my deploiement cloudstack 4.4 and xenservers 6.2. i have configured > multiple networks each one for a specific traffic type > (Public,management,storage,guest). > > these networks are isolated and vlan tagged ,so on my xenservers i have > the 4 networks each with a specific name label and pointing to a Vlan. > > when i added the public ip range ,i did not mention the VLAN number of my > public network. > > Can this cause issues or not ? > > and what is the pupose of putting the vlan number on the ip ranges ? > > Thx.
