Does this really exists?
The VCD entity network "cfx_direct_1" does not exist.
1 of 1 people found this helpful
Since you have mentioned that VM gets created and OS customization goes through, try to look at the jobs in VCloud to see what the error is? Since CLM is getting that "cfx_direct_1" does not exist, there can be some configuration issue in your vCloud.
Thanks Devendra for your inputs to look in VCloud configurations.
We have investigated further inside VCloud for the issue.
If the network assigned to the template is having one default network. But every new VDC has a new associated network. Then we request provisioning, it gives error saying that the VCD entity network does not exist from VCloud itself during VM reconfiguration.
Thus, this is root cause identified and VM template and newly created ORG VDC network must be same. When we have created new template with new org vdc network, VM provisioning completed successfully.
But this will require template to be created for every new VDC. Accordingly, we need to make every new template available in CLM along with taggings.
Also, new template is not coming into CLM by just LDC synchronization, it requires a restart of csm service to show up in CLM. Could you please confirm if this is the correct behavior of CLM?
The issue that you mentioned, about the VCD entity network "cfx_direct_1" does not exist, is because we cannot change the network with the help of tagging in CLM. The Network is referencing to tag need to be present in the your vCloud vApp Template.Tagging facilitates mapping between your NIC in the vAppTemplate.
Thus, for each set of network in your case (cfx_direct_1) that you want to provision to, you must need a separate vApp template with those networks attached.Or else availability of vOrg network on your vApp template used.
Thanks & Regards,