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...@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...@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 >>> >>> >
