Applications are not supported so no fixes and use at own risk.
This is something i picked up during my initial configuration of vCloud director and stumped me for a many days until i was finally able to figure out what was going on.
I created various isolated-backed networks, however during the course of the configuration changes were required and I delete ALL of the network pools to start over. When I then recreated the network pools with the same VLAN. When I deployed the vApps with local vApp network the VM’s did not want to communicate with each other at all.
Debugging the problem:
I tried recreating all of the network pools again, and deployed the vApps multiple times with different configuration. Tried to manually setup IP address and multiple network cards. However when i change the VM network to a portgroup that was not part of vcloud director I was able to communicate with the VM which lead me to believe the issue was not with the VM itself but with the vCloud network component. Tested the vShield Manager which seems to be working correctly.
VMware support case opened:
VMware was unable to figure out the problem at the time…
vCloud director 184.108.40.2068405
vShield manager 5.1.1-848085
Did some research to see if any other users were experiencing this problem and ran into the a community post which describe the problem to the teeth exactly like mine. Link below.
Solution we both came up with was to re-prepare the physical ESXi host within vCloud director, without needing to do anything else.
Another workaround to this was to always leave one network pool, and this problem only appears when you delete all the isolated-backed network pools.
I just ran into a very interesting problem today within vCloud Director when a vApp is deployed from catalog a VM will loose its network connection. Even when Guest OS customization is disabled.
We have a vApp with multiple VMs, all Windows 2008 R2 SP1.
The vApp was saved into catalog with “make identical copy”
After creating the vApp from catalog template all the VM’s come up correctly accept the one installed with Exchange.
Debugging the problem:
It seems the network was lost and then gets recreated but is set to DHCP so no network connections possible.
- Tried to fix by disabling the “guest OS customization” before powering on the vApp.
- Recreated the network card on the particular VM but with no luck.
Delete the Virtual network adapter.
Power on the VM
Use device manager to remove all network interfaces with name “VMXNET”.
( For more information, see the Microsoft Knowledge Base articles 241257 and 2550978.)
Shutdown the VM
Edit VM properties through Vcloud director interface and under the hardware tab add a new virtual network adapter.
Power on VM with force customization.
The solution to our problem was to install the hotfix from Microsoft: