This is a known issue affecting upgraded vDS switches in vCenter Server 5.5. Currently there is no resolution.
To work around this issue, a modification of the vCenter Server database is required to make the switch export correctly.
To modify the database and allow correct vDS export:
- Log in to the source vCenter Server database using SQL management studio
- Run this SQL script prior to exporting the vDS switch:
update VPX_DVPORT_SETTING
set VPX_DVPORT_SETTING.LACP_ENABLE = NULL, VPX_DVPORT_SETTING.LACP_MODE = NULL
from VPX_DVPORT_SETTING B
inner join VPX_DVS A
on A.ID = B.DVS_ID AND A.PRODUCT_VERSION = '5.5.0' AND A.LACP_API_VERSION = 'multipleLag';