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
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
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
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= name-label="
And that'
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 t
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
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 an
