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.
