NSX-T VDS to vCenter VDs migration failed when NVDs host switch is configured with LACP fast rate

Products

• VMware NSX

Issue/Introduction

Symptoms:

• You have configured NVDS host switch with LACP fast rate on the uplink profile as per the example image below.

• When running the API call POST https://<nsx-mgr>/api/v1/nvds-urt/topology?action=apply as per the NSX-T administration guide you may not receive any errors but may see a similar output to the one below:

{
  "topology" : [ {
    "nvds_id" : "932eee2c-xxxx-xxxx",
    "nvds_name" : "nsxHostSwitch",
    "compute_manager_topology" : [ {
      "compute_manager_id" : "dcfb228a-xxxx-xxxx",
      "dvswitch" : [ {
        "data_center_id" : "datacenter-3",
        "vds_name" : "CVDS-xxxx-xxxx",
        "transport_node_id" : [ "d0fa5112-xxxx-xxxx" ],
        "_protection" : "NOT_PROTECTED"
      } ]
    } ],
    "_protection" : "NOT_PROTECTED"
  } ]

• When you run the API GET https://<nsx-mgr>/api/v1/nvds-urt/status-summary/<precheck-id> you may observe that the precheck status is failed.

{
  "precheck_id" : "b17b96b9-xxxx-xxxx",
  "precheck_status" : "APPLY_TOPOLOGY_FAILED",
  "migration_state" : [ {
    "host" : "d0fa5112-xxxx-xxxx",
    "overall_state" : "UPGRADE_READY",
    "ip_address" : "10.x.x.x",
    "_protection" : "NOT_PROTECTED"
  } ]

• You may will receive the below error in vCenter while trying to migrate NVDS host switch to CVDS host switch

'Update Link Aggregation Control Protocol groups on vSphere Distributed Switch, The operation is not supported on the object. Feature feature is not supported on VDS version version'

 

Note: The preceding logs/output excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

 

Environment

VMware NSX-T Data Center

Cause

This issue is caused as LACP fast rate is not supported on VDS 7.0

Resolution

This is a known issue impacting NSX-T Data Center.

Workaround:

1. Change LACP uplinkprofile to 'LACP Time Out: Slow';
2. Run POST https://<nsx-mgr>/api/v1/nvds-urt?action=cleanup to clean the failed nvds-urt;
3. Follow NSX-T administration guide to migrate to VDS again;