N-VDS to VDS migration fails at VDS migrate stage with the error "% An internal error occurred"
search cancel

N-VDS to VDS migration fails at VDS migrate stage with the error "% An internal error occurred"

book

Article ID: 389750

calendar_today

Updated On:

Products

VMware NSX-T Data Center

Issue/Introduction

  • Precheck ID is generated using the following API call:
    • POST https://<nsx-mgr>/api/v1/nvds-urt/precheck
  • No recommended topology is provided by NSX manager when running the following API call:

    • GET https://<nsx-mgr>/api/v1/nvds-urt/topology/<precheck-id>

  • Running "vds-migrate show-topology" in admin mode of the NSX manager might throw the error "% An internal error occurred".

  • The following log entries are observed in /var/log/proton/nsxapi.log, using the precheck-id generated using the above step:
2025-02-25T10:55:27.511Z  INFO http-nio-127.0.0.1-7440-exec-20 FacadeInterceptorHelperImpl 60867 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Starting intent for /policy/api/v1/infra/nvds-urt/status-summary/<precheck-id> with reqID <req-id>

2025-02-25T10:55:27.513Z  INFO http-nio-127.0.0.1-7440-exec-20 NvdsUpgradeReadinessCheckServiceImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" reqId="<req-id>" subcomp="manager" username="admin"] NVDS-UPGRADE getNvdsUpgradeSummary precheckId <precheck-id> upgradeState IN_PROGRESS

2025-02-25T10:55:27.513Z  WARN http-nio-127.0.0.1-7440-exec-20 FacadeInterceptorHelperImpl 60867 - [nsx@6876 comp="nsx-manager" level="WARNING" reqId="<req-id>" subcomp="manager" username="admin"] API result did not pass validationField level validation errors: {required property migration_state is missing}, {required property precheck_issue is missing}

  • After this, NSX manager will query for Network info from the ESXi hosts using the vCenter Server. Here, no network info is obtained for one or multiple host(s).
2025-02-25T10:56:18.261Z  INFO NvdsUpgradeTaskExecutor1 Utils 60867 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] getSystemIpAddress invoked with networkIFName = null

2025-02-25T10:56:18.265Z  INFO NvdsUpgradeTaskExecutor1 VcConnectionImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Successfully logged into <vCenter-Server-IP> with versionClass v7_0_2_0

2025-02-25T10:56:18.270Z  INFO NvdsUpgradeTaskExecutor1 VcResourceServiceImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Getting hardware and network info for host host-xyz in VC  and query is DEFAULT

2025-02-25T10:56:18.307Z  WARN NvdsUpgradeTaskExecutor1 VcResourceServiceImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] No config or Network found on host host-xyz in VC {}

2025-02-25T10:56:18.307Z  INFO NvdsUpgradeTaskExecutor1 VcConnectionImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Logout for Vc <vCenter-Server-IP>
  • After this, a NullPointerException is thrown and precheck fails:
2025-02-25T10:56:18.310Z  INFO NvdsUpgradeTaskExecutor1 NvdsUpgradeReadinessCheckServiceImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] NVDS-UPGRADE exception in precheckConfig <precheck-id>: java.lang.NullPointerException
        at com.vmware.nsx.management.nvdsupgrade.service.NvdsUpgradeReadinessCheckServiceImpl.validateNvdsUpgradeConfig(NvdsUpgradeReadinessCheckServiceImpl.java:1080)

2025-02-25T10:56:19.913Z  INFO http-nio-127.0.0.1-7440-exec-12 NvdsUpgradeReadinessCheckServiceImpl 60867 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" reqId="<req-id>" subcomp="manager" username="admin"] NVDS-UPGRADE getNvdsUpgradeSummary precheckId <precheck-id> upgradeState FAILED
  • To identify the ESXi host using MOID, open a new webpage and enter the following URL:

                 https://<vCenter-Server-FQDN-or-IP>/mob/?moid=host-xyz

                             host-xyz is the MOID of ESXi host which is thrown in above error.

                  Check for name field in the page and verify the status of ESXi host in vCenter UI.(Not responding or disconnected)

Environment

VMware NSX-T Data Center.

Cause

The precheck fails because NSX manager is unable to retrieve the host network info while validating the ESXi host for precheck.

Resolution

Verify that the ESXi host is successfully connected to vCenter Server. If the host in question shows as Disconnected or Not Responding, refer the following Knowledge base article:

Troubleshooting an ESXi host in a "not responding" state

Additional Information