GitHub user TheKunalSen added a comment to the discussion: Multi-subnet setup with VPN – System VMs unreachable and agent not connecting
@prashanthr2 We added the .2 network host in a totally seperate zone with the internal dns1 of .2.1 and also the physical network ip address range also we put of .2 network and also the pod tha got created in that zone also has .2 ip ranges and it worked, vms getting created and all evrything worked but if I create a zone on .1 ip address and only put .1.1 as a internal dns1 in the zone and then create a separate pod in that .1 zone which will have ip ranges of .2 network then also in that pod -> cluster the .2 host were getting added and also the vm was getting created on that .2 host too but there was a problem, the vms which are getting created on .2 host was getting stuck at boot screen and even if after a long time the login screen was showing but the password it was providing, it always says incorrect note that if I create vm with that same Ubuntu template on .1 host then it's not issue all smooth, Different zone for .2 network host totally works but then I can not migrate the vms through out the zones , ig I have to build my own layer upon cloudstack itself to do that but if I add different network hosts in different pods but same zone then I can migrate, Let me know if I add the .2.1 on internal dns2 of the zone and .1.1 on the internal dns1 of the zone then will it work? Even if it works then what will I do if I have to add hosts from 4 different networks under one zone and different pods GitHub link: https://github.com/apache/cloudstack/discussions/12909#discussioncomment-16464851 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
