- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Thanks for your help
We have couple environment of esx's clusters
on one of our environment we get error message when deploying OVF using api
"The provided network mapping between OVF networks and the system network is not supported by any host."
we use Vcenter 6U3 with standard switch
do you have any idea where to start?
Thanks shai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Provide some more information about your OVF and the properties it contains. It's a manual deployment via the Flex client successful or not?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
if you share some more information about error so will help to resolve the problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have seen this problem when the portgroup Names are not consistent things like you have changed the Standard Switch port group's names.
Try this
Edit the interfaces and change the Connected To field to use the new name of the Standard Switch port group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
manual deployment work normal
only when we work with vim dll to vcenter
its works well on other environment that we have
We are using vmware.vim v4.0.30319:
private OvfCreateImportSpecResult createOvfImportSpec(
string vmName,
string ovfDescriptor,
string defaultOvfNetwork,
string datacenterName,
WindowsIdentity userIdentity,
List<string> ignoredDataStores,
string targetResourcePool,
HostSystem hostSystem,
ResourcePool resourcePool,
OvfManager ovfManager)
{
Datacenter datacenter = FindDataCenterByName(datacenterName);
if (datacenter == null)
throw new Exception(string.Format("CreateMachine failed: failed to find datacenter by name {0}", datacenterName));
Datastore dataStoreWithMostFreeSpace = FindDataStoreWithMostFreeSpace(datacenterName, userIdentity, ignoredDataStores);
if (dataStoreWithMostFreeSpace == null)
throw new Exception(string.Format("CreateMachine failed: failed to find accessible datastore for user {0}", userIdentity.Name));
OvfCreateImportSpecParams importSpecParams = new OvfCreateImportSpecParams();
importSpecParams.DiskProvisioning = OvfCreateImportSpecParamsDiskProvisioningType.thin.ToString();
importSpecParams.EntityName = vmName;
importSpecParams.HostSystem = hostSystem.MoRef;
importSpecParams.Locale = "US";
importSpecParams.DeploymentOption = string.Empty;
importSpecParams.NetworkMapping = createNetworkMapping(ovfDescriptor, defaultOvfNetwork, ovfManager);
//returning the import specification
return ovfManager.CreateImportSpec(ovfDescriptor, resourcePool.MoRef, dataStoreWithMostFreeSpace.MoRef, importSpecParams);
}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot
i didn't understand well..
on all our esxi's we have STD switch with the same portgroup name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I fixed it by creating a new portgroup and move all the vm's and ten change the name.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In my case, I was using dvs port groups and the hosts were not added to that dvs switch. I added all esxi hosts of the cluster and then it worked.