Hello Andija, thank you very much for your effort and explanations :) Actually we're in advanced zone but I saw in SSVM cloud.log that it's trying to connect lo localhost:8250 so I understood that SSVM was trying to connect to Management Server that, obviously, is not localhost. It's still not clear for me how Management Server can push his hostname if the SSVM is unable to connect to Management Server, but I changed some settings in ACS (please, tell me which one is the right one), recreate SSVM and CPVM and all works fine! :)
Thank you On Sun, Oct 20, 2019 at 11:55 PM Andrija Panic <[email protected]> wrote: > HI Alessandro, > > in case of VMware, link local network is not (possible to be) used - so > the mgmt IP is actually used - i.e. mgmt server will talk mgmt IP inside > the SSVM (over ssh), so that is clear I guess. > Have you preseeded the systemVM template as the manual instructs? Once you > have systemVM template in place and at least one alive hypervisor host, ACS > will try to create a SSVM and CPVM from that template. > You can check their state in INfrastructure --> System VMs, their state > should be UP and Agent State should be Connected (both green) - if that is > in place, you are good to go to download any template/ISO. > > Are you using Basic zone or Advanced? I remember a bug in Basic zones, that > ssvm will try to mount Secondary NFS server by routing via it's Public > (default) interface, so in this case, even if SS is in same subnet/network > as the mgmt network, it's still advisable to explicitly define Storage > network, using same subnet, and also reserve a small chunk of the network > to be assinged to systemVMs etc. - so that another interface/NIC will be > created inside SSVM in that storage network (so your mgmt network again) > and then all will be OK. > > Let me know about systemVM template ^^^ > > Andrija > > On Sat, 19 Oct 2019 at 21:50, Alessandro Caviglione < > [email protected]> > wrote: > > > Hi, > > I've just deployed a new CS 4.13 management server and I've configured > the > > zone for VMware in this way: > > > > Management network vSwitch0 VLAN200 (SystemVM IPs 192.168.200.170-200) > > Public Network vSwitch1 VLAN201 (Some Public IPs) > > Guest Network vSwith1 VLAN 400-500 > > > > I do not have configured Storage Network because I know that if it's not > > configured, Management Network is used. > > In fact, Secondary Storage is in the same network as Management Network > and > > it has IP: 192.168.200.20 > > > > I've correctly configured Secondary Storage to use NFS share over > > 192.168.200.20 storage. > > Secondary Storage VM has been deployed and it's running, but I see that > it > > has 2 IPs, one on Management and one on Public Network. > > As far as I know, it should have one additional IP for Link Local... > > However, my issue is that when I try to add an ISO Template, nothing is > > downloaded and in management-server log I see: > > "There is no secondary storage VM for secondary storage host CS-SEC-VMW" > > > > what it means? > > > > Thank you!! > > > > > -- > > Andrija Panić >
