During preparation for NVDS to CVDS migration, "vds-migrate apply-topology" step it is failing with error "APPLY_TOPOLOGY_FAILED"
search cancel

During preparation for NVDS to CVDS migration, "vds-migrate apply-topology" step it is failing with error "APPLY_TOPOLOGY_FAILED"

book

Article ID: 404906

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Receiving the following error when performing "Make the following API call to create a VDS with the recommended topology" step during the Migrate Host Switch to vSphere Distributed Switch workflow:
    • {    
      "precheck_id": "########-####-####-####-############",  
      "precheck_status": "APPLY_TOPOLOGY_FAILED",    
      "migration_state": [        
           {            
         "host": "/infra/sites/default/enforcement-points/default/host-transport-nodes/########-####-####-####-############",
           "overall_state": "UPGRADE_READY",
         "ip_address": "<IP-Address>",
           "_protection": "NOT_PROTECTED"}, 
           {
         "host": "/infra/sites/default/enforcement-points/default/host-transport-nodes/########-####-####-####-############",
           "overall_state": "UPGRADE_READY",
         "ip_address": "<IP-Address>",
           "_protection": "NOT_PROTECTED"}, 
           {
         "host": "/infra/sites/default/enforcement-points/default/host-transport-nodes/########-####-####-####-############",
           "overall_state": "UPGRADE_READY",
         "ip_address": "<IP-Address>",
           "_protection": "NOT_PROTECTED"}
           ]
      }
  • The following error can be found in /var/log/proton/nsxapi.log in NSX Manager logs mentioning a specific Transport node, in this example its AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA:
    • <TimeStamp> ERROR NvdsUpgradeTaskExecutor1 TransportNodeServiceImpl 71782 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8233" level="ERROR" subcomp="manager"] Mixing Logical Switch id ########-####-####-####-############ with port-group in ESX vmk migr
      ation parameter esx_mgmt_if_migration_dest is not allowed.
      <TimeStamp>  WARN NvdsUpgradeTaskExecutor1 PolicyResourceChangeNotificationManager 71782 POLICY [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Failure received invoking listener TransportNodeListener for change UPDATING on resource /infra
      /sites/default/enforcement-points/default/host-transport-nodes/AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA
      com.vmware.nsx.management.switching.common.exceptions.SwitchingException: null
            at com.vmware.nsx.management.switching.infrastructure.service.TransportNodeServiceImpl.validateVmkMigrateOutOfLogicalSwitchSpec(TransportNodeServiceImpl.java:2969) ~[?:?]
      ...
      ...
      <TimeStamp> ERROR NvdsUpgradeTaskExecutor1 NvdsUpgradeReadinessCheckServiceImpl 71782 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP250020" level="ERROR" subcomp="manager"] Failed to apply ExtraConfigHswProfile on TransportNode AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA, exception Error in Updated TransportNode. Exception: null  : com.vmware.nsx.management.switching.common.exceptions.SwitchingException: Error in Updated TransportNode. Exception: null
              at com.vmware.nsx.management.switching.infrastructure.ufodao.TransportNodeDaoHelper.createOrUpdateHostTransportNode(TransportNodeDaoHelper.java:362)
              at com.vmware.nsx.management.nvdsupgrade.service.NvdsUpgradeReadinessCheckServiceImpl.updateExtraConfigProfileOnTransportNodes(NvdsUpgradeReadinessCheckServiceImpl.java:2017)
              at com.vmware.nsx.management.nvdsupgrade.service.NvdsUpgradeReadinessCheckServiceImpl$NvdsUpgradeTask.run(NvdsUpgradeReadinessCheckServiceImpl.java:1409)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
              at java.lang.Thread.run(Thread.java:750)

Cause

If there is a discrepancy in NSX configuration for one of the hosts in the cluster, it would cause a failure in step 7 of Migrate Host Switch to vSphere Distributed Switch because every host configuration has to be identical in order for the script workflow to create new vDS.

Resolution

Get the TransportNode ID from the error as mentioned in the Issue/Introduction field above, find it in NSX UI search and investigate for any discrepancies against other hosts in the cluster.  Please make sure that this TransportNode has identical configuration to the rest of the hosts. 

Once the configuration discrepancy has been resolved, re-try step 7 in Migrate Host Switch to vSphere Distributed Switch.