You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Fedi Ben Ali <be...@gmail.com> on 2015/07/09 15:28:02 UTC
Public IP VLAN
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.
Re: Public IP VLAN
Posted by Andrija Panic <an...@gmail.com>.
"So to have one network that can caryies two different vlan's, the tag
should be set on ACS level."
Yes, I guess this is the only way (if one 1 logical Public
Network/bonds/whatever) - inside ACS you need 2 IP ranges on different
vlans.
and Yes you should be fine, with no network issues.
Your setup will be similar to:
bond0-->cloudbrX (or whatever Xen label you used - I reference here how it
works for KVM)
use cloudbrX as Network Label in Public network.
create 2 ranges (vlan80 and vlan81) inside 1 Public network
ACS will create folowing vlan and bridge interfaces on your Xen/KVM
- bond0.80 -->brbond0-80<--Pubic NICs joined to this bridge
- bond0.81 -->brbond0-81<--Pubic NICs joined to this bridge
NOTE: From my experience: make sure that the IP ranges used in these 2
public IP ranges - are NOT overlapping AT ALL - meaning, they must have
different range (of course) and also use different gateway etc - I have run
into problems when I was using 1/2 of a /24 network, and later wanted to
add the rest 1/2 IPs as 2nd IP range...
Best,
On 9 July 2015 at 16:26, Fedi Ben Ali <be...@gmail.com> wrote:
> hello ,
>
> thx for your response.
>
> The client has provided two public ip adreses ranges,he asks that those two
> ranges should be used on the same zone. In the network configuration each
> ip range is reacheable over a specific vlan (the first on vlan 80 and the
> scond on vlan 81).this configuration is made on the network hardware
> (switches ...).
>
> On my xenserver i have two networks for the public traffic each network
> with the specific Vlan (80 et 81).all my public traffic goes through the
> same xenserver nic bond but the first rage with vlan 80 and the second on
> vlan 81.
>
> On cloudstack,when we define the zones public network ,we set the name
> label of the network configured on the host (we should have one network not
> two).
>
> So to have one network that can caryies two different vlan's, the tag
> should be set on ACS level.
>
> can i do so without having networking issues ?
>
>
>
>
> 2015-07-09 14:54 GMT+01:00 Andrija Panic <an...@gmail.com>:
>
> > 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 <be...@gmail.com> 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ć
> >
>
--
Andrija Panić
Re: Public IP VLAN
Posted by Fedi Ben Ali <be...@gmail.com>.
hello ,
thx for your response.
The client has provided two public ip adreses ranges,he asks that those two
ranges should be used on the same zone. In the network configuration each
ip range is reacheable over a specific vlan (the first on vlan 80 and the
scond on vlan 81).this configuration is made on the network hardware
(switches ...).
On my xenserver i have two networks for the public traffic each network
with the specific Vlan (80 et 81).all my public traffic goes through the
same xenserver nic bond but the first rage with vlan 80 and the second on
vlan 81.
On cloudstack,when we define the zones public network ,we set the name
label of the network configured on the host (we should have one network not
two).
So to have one network that can caryies two different vlan's, the tag
should be set on ACS level.
can i do so without having networking issues ?
2015-07-09 14:54 GMT+01:00 Andrija Panic <an...@gmail.com>:
> 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 <be...@gmail.com> 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ć
>
Re: Public IP VLAN
Posted by Andrija Panic <an...@gmail.com>.
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 <be...@gmail.com> 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ć