You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Luke Camilleri <lu...@gmail.com> on 2015/06/12 18:47:06 UTC

Basic networking using a separate physical nic for guest traffic

Hi there, can anyone help me in configuring a second physical nic for 
the guest traffic please?

I am using the basic networking model and would like to use a dedicated 
nic to handle the guest traffic. i have set a network label (CS-GUEST) 
in xenserver 6.5 and mapped the same name in cloudstack's guest network 
option but I cannot ping the default gateway from the secondary storage 
VM and therefore I cannot download the initial CentOS 5.6 template and 
start creating the VM's

Thanks in advance

Luke

Re: Basic networking using a separate physical nic for guest traffic

Posted by Luke Camilleri <lu...@gmail.com>.
Just to answer myself and as a reference to others who end up in the 
same situation, the issue is pretty simple now that I think of it.

When creating the initial configuration when the guest network is setup 
either no traffic label name for xenserver is requested or I missed that 
and thus the only network assigned to the system vm's is the default 
management network. When the setup is done and the systemvm's are 
created along the way all the interfaces are assigned to this network 
and thus the guest traffic will not function properly.

In Cloudstack edit the network labels from : Home --> Infrastructure--> 
Zones--> <zone name> -->PhysicalNetworkInBasicZone--> Guest and type in 
the XenServer traffic label (This also needs to be done in case of 
Storage traffic I assume but I am not at that point yet!). When that is 
done you have 2 options to fix this problem in a deployment with XenServers:

1- either go into XenCenter and change the network of the SSVM and CPVM 
to the new guest network label that you just entered into CS from the 
Networking tab of the respective systemvm
2- Or destroy the VM's and let them re-create but this time CS will put 
them on the correct network as long as you entered the correct details 
in CS to match the traffic label of XenServer

Thanks for your help Erik and for pointing me in the rightdirection

On 6/14/2015 12:42 PM, Luke Camilleri wrote:
> Hi Erik,
>
> as with your suggestion using the xe-network-list and then using the 
> xe-network-param-set I think that is basically the same thing as 
> changing the name from the properties of the networking tab in the 
> hosts networking section.
>
> The SSVM needs to download the templates and that would be guest 
> traffic in fact when I fixed it the template downloaded immediately.
>
> The storage traffic will be added later but at this stage I am in the 
> testing phase
>
> On 6/14/2015 12:16 AM, Erik Weber wrote:
>> Can't really say I'm familiar with that setting, so it's hard to say 
>> what
>> kind of implications you get from it.
>>
>> What I usually do is find the uuid of the network I want to use within
>> cloudstack with "xe network-list", and give it a name-label with
>> "xe-network-param-set uuid=<FROM PREVIOUS> name-label=<WHATEVER I WANNA
>> CALL IT IN ACS>"
>> And that's it.
>> If necessary I create the bond first, but in the case of single nic
>> networks I use the network that's related to the nic.
>>
>> One thing though, your SSVM isn't doing any guest traffic, thus it
>> shouldn't be on any guest networks.
>>
>> You most likely want to add a storage network.
>>
>


Re: Basic networking using a separate physical nic for guest traffic

Posted by Luke Camilleri <lu...@gmail.com>.
Hi Erik,

as with your suggestion using the xe-network-list and then using the 
xe-network-param-set I think that is basically the same thing as 
changing the name from the properties of the networking tab in the hosts 
networking section.

The SSVM needs to download the templates and that would be guest traffic 
in fact when I fixed it the template downloaded immediately.

The storage traffic will be added later but at this stage I am in the 
testing phase

On 6/14/2015 12:16 AM, Erik Weber wrote:
> Can't really say I'm familiar with that setting, so it's hard to say what
> kind of implications you get from it.
>
> What I usually do is find the uuid of the network I want to use within
> cloudstack with "xe network-list", and give it a name-label with
> "xe-network-param-set uuid=<FROM PREVIOUS> name-label=<WHATEVER I WANNA
> CALL IT IN ACS>"
> And that's it.
> If necessary I create the bond first, but in the case of single nic
> networks I use the network that's related to the nic.
>
> One thing though, your SSVM isn't doing any guest traffic, thus it
> shouldn't be on any guest networks.
>
> You most likely want to add a storage network.
>


Re: Basic networking using a separate physical nic for guest traffic

Posted by Luke Camilleri <lu...@gmail.com>.
Hi Erik,

as with your suggestion using the xe-network-list and then using the 
xe-network-param-set I think that is basically the same thing as 
changing the name from the properties of the networking tab in the hosts 
networking section.

The SSVM needs to download the templates and that would be guest traffic 
in fact when I fixed it the template downloaded immediately.

The storage traffic will be added later but thanks for pointing it out

On 6/14/2015 12:16 AM, Erik Weber wrote:
> Can't really say I'm familiar with that setting, so it's hard to say what
> kind of implications you get from it.
>
> What I usually do is find the uuid of the network I want to use within
> cloudstack with "xe network-list", and give it a name-label with
> "xe-network-param-set uuid=<FROM PREVIOUS> name-label=<WHATEVER I WANNA
> CALL IT IN ACS>"
> And that's it.
> If necessary I create the bond first, but in the case of single nic
> networks I use the network that's related to the nic.
>
> One thing though, your SSVM isn't doing any guest traffic, thus it
> shouldn't be on any guest networks.
>
> You most likely want to add a storage network.
>


Re: Basic networking using a separate physical nic for guest traffic

Posted by Erik Weber <te...@gmail.com>.
Can't really say I'm familiar with that setting, so it's hard to say what
kind of implications you get from it.

What I usually do is find the uuid of the network I want to use within
cloudstack with "xe network-list", and give it a name-label with
"xe-network-param-set uuid=<FROM PREVIOUS> name-label=<WHATEVER I WANNA
CALL IT IN ACS>"
And that's it.
If necessary I create the bond first, but in the case of single nic
networks I use the network that's related to the nic.

One thing though, your SSVM isn't doing any guest traffic, thus it
shouldn't be on any guest networks.

You most likely want to add a storage network.

-- 
Erik

On Sat, Jun 13, 2015 at 11:51 PM, Luke Camilleri <
luke.camilleri.it@gmail.com> wrote:

> Thanks Erik you are spot on. When checking the 4 interfaces of the SSVM in
> XenCenter I noticed that eth1, eth2 and the3 are all assigned to the
> management interface network of the xenserver host although I changed the
> network label in the guest traffic UI.
>
> Can this be due to the case that on the xenserver in the network settings
> I have the "Automatically add this network to new virtual machines" checked?
>
> Thanks in advance
>
>
> On 6/12/2015 8:24 PM, Erik Weber wrote:
>
>> Verify in xencenter or by cli that the ssvm is actually connected to the
>> right interface.
>>
>> Erik
>>
>> Den fredag 12. juni 2015 skrev Luke Camilleri <
>> luke.camilleri.it@gmail.com>
>> følgende:
>>
>>  Hi there, can anyone help me in configuring a second physical nic for the
>>> guest traffic please?
>>>
>>> I am using the basic networking model and would like to use a dedicated
>>> nic to handle the guest traffic. i have set a network label (CS-GUEST) in
>>> xenserver 6.5 and mapped the same name in cloudstack's guest network
>>> option
>>> but I cannot ping the default gateway from the secondary storage VM and
>>> therefore I cannot download the initial CentOS 5.6 template and start
>>> creating the VM's
>>>
>>> Thanks in advance
>>>
>>> Luke
>>>
>>>
>

Re: Basic networking using a separate physical nic for guest traffic

Posted by Luke Camilleri <lu...@gmail.com>.
Thanks Erik you are spot on. When checking the 4 interfaces of the SSVM 
in XenCenter I noticed that eth1, eth2 and the3 are all assigned to the 
management interface network of the xenserver host although I changed 
the network label in the guest traffic UI.

Can this be due to the case that on the xenserver in the network 
settings I have the "Automatically add this network to new virtual 
machines" checked?

Thanks in advance

On 6/12/2015 8:24 PM, Erik Weber wrote:
> Verify in xencenter or by cli that the ssvm is actually connected to the
> right interface.
>
> Erik
>
> Den fredag 12. juni 2015 skrev Luke Camilleri <lu...@gmail.com>
> følgende:
>
>> Hi there, can anyone help me in configuring a second physical nic for the
>> guest traffic please?
>>
>> I am using the basic networking model and would like to use a dedicated
>> nic to handle the guest traffic. i have set a network label (CS-GUEST) in
>> xenserver 6.5 and mapped the same name in cloudstack's guest network option
>> but I cannot ping the default gateway from the secondary storage VM and
>> therefore I cannot download the initial CentOS 5.6 template and start
>> creating the VM's
>>
>> Thanks in advance
>>
>> Luke
>>


Re: Basic networking using a separate physical nic for guest traffic

Posted by Erik Weber <te...@gmail.com>.
Verify in xencenter or by cli that the ssvm is actually connected to the
right interface.

Erik

Den fredag 12. juni 2015 skrev Luke Camilleri <lu...@gmail.com>
følgende:

> Hi there, can anyone help me in configuring a second physical nic for the
> guest traffic please?
>
> I am using the basic networking model and would like to use a dedicated
> nic to handle the guest traffic. i have set a network label (CS-GUEST) in
> xenserver 6.5 and mapped the same name in cloudstack's guest network option
> but I cannot ping the default gateway from the secondary storage VM and
> therefore I cannot download the initial CentOS 5.6 template and start
> creating the VM's
>
> Thanks in advance
>
> Luke
>