"Host with NamedTeaming config in uplink profile" error when migrating from N-VDS to VDS
search cancel

"Host with NamedTeaming config in uplink profile" error when migrating from N-VDS to VDS

book

Article ID: 336824

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Performing an N-VDS to VDS migration.
  • Host(s) have an Uplink profile which contain a Named Teaming Policy.
  • When you run the pre-check command vds-migrate precheck, you are presented with an error:

GetVDSUpgradeSummary: {"precheck_id": "ec2e051e-####-####-####-########52b", "precheck_status": "FAILED", "precheck_issue": [{"component": "Transport Node", "objid": "01a44b75-####-####-####-########09b", "error": "Host with NamedTeaming config in uplink profile", "recommendation":

Environment

VMware NSX-T Data Center

Cause

Migration from N-VDS to VDS for host(s) with Named Teaming Policy configuration, in the uplink profile, is not supported in versions prior to NSX 3.1.2.

Resolution

This issue is resolved in VMware NSX 3.1.2, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

NSX-T 3.1.2 and above, now permits the use of Named Teaming Policy.

If you are unable to upgrade, you will need to remove the Named Teaming Policy to allow the migration.

Additional Information