Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Cannot use the vDS Import function to migrate to new vCenter Server (2045468)
Symptoms
- Cannot use the vDS import function to migrate to a new vCenter Server
- The Export function works properly
- In the vSphere Web Client, you see the error:
A specified parameter was not correct.spec.defaultPortConfig.lacpPolicyThe property spec.defaultPortConfig.lacpPolicy cannot be changed to unset in the VDS level settingsDVS 1a 75 17 50 0b 1b 51 ba-6b 00 07 f8 20 f6 8b 87 cannot be found
- In the vpxd.log file, you see entries similar to:
[04620 info 'commonvpxLro' opID=9a70e68] [VpxLRO] -- BEGIN task-32 -- -- vim.dvs.DistributedVirtualSwitchManager.importEntity -- 53eb6668-ca28-41d0-7bd0-3b904f9bd003(5216b5a6-537c-06c2-7db1-d5f37a0d79d7)[04620 error 'corevalidate' opID=9a70e68] [Validate::Check()FeatureCapability] LACP is not supported on DVS [dvSwitch01][04620 error 'dvsvpxdMoDvsManager' opID=9a70e68] [MoDvsManager::CreateNewEntity] Import Failed while creating DVS from Backup with key[1a 75 17 50 0b 1b 51 ba-6b 00 07 f8 20 f6 8b 87]. Fault:[vmodl.fault.InvalidArgument][04620 error 'dvsvpxdMoDvsManager' opID=9a70e68] [MoDvsManager::CreateNewEntity] Import Failed while creating DVPG from Backup with key[dvportgroup-79]. Fault:[vim.fault.NotFound][04620 info 'commonvpxLro' opID=9a70e68] [VpxLRO] -- FINISH task-32 -- -- vim.dvs.DistributedVirtualSwitchManager.importEntity --
Resolution
This is a known issue in vSphere 5.1 and is currently under investigation by VMware.
A resolution for this issue is being evaluated for inclusion in a future update.
Currently, there is no workaround for this issue.
Additional Information
See Also
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

