I have inherited a small internal vCloud environment, but have an urgent issue to address.
The vCloud network was configured with private IP addresses (192.168.100.x), while my main network is on a completely different VLan setup. There is no routing between the vCloud machines (vApps/VMs) and the rest of the network accordingly. Users are connecting via VMRC, but this is limiting functionality + the lack of network connectivity causes other problems. Apparently there is no need to have the 2 networks separated, but it was setup that way anyway.
I am in a shared office environment and have no options to expand my network. I have 4 VLans in a /22 setup. There are plenty of IP addresses available.
In vCloud the EdgeGateway has been configured with the /22 subnet and 1 IP address on this VLan accordingly.
The VDC network is configured with the 192.168.100.x VLan and the main EdgeGateway for the connection.
I was hoping that I can setup a secondary VDC Network using a pool of reserved IP addresses from my /22 VLAN, but vCloud then “complains” about that this subnet overlaps with a subnet of another network connected to the edge gateway.
So, I cannot get another VLan that is able to talk on the main network and I cannot use existing IP addresses on the /22 VLan that I have. I have 160 vApps/VMs deployed and this setup is severely limiting my users.
VDC Network = 192.168.100.x
Main Network = 10.x.x.x /22
Any ideas of how I could address this?