NSX-T Migrate vSphere Network fails with error "General error has occured"
search cancel

NSX-T Migrate vSphere Network fails with error "General error has occured"

book

Article ID: 322628

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
  • Migrate vSphere Network fails with error "General error has occured"
  • NSX Manager logs (migration-coordinator.log) display message(s) similar to:
2019-11-13T13:53:30.995Z ERROR http-nio-127.0.0.1-7450-exec-1 NsxBaseRestController - - [nsx@6876 comp="nsx-manager" errorCode="MP100" subcomp="migration-coordinator"] 0
java.lang.ArrayIndexOutOfBoundsException: 0


Environment

VMware NSX-T
VMware NSX-T Data Center
VMware NSX-T Data Center 2.x

Cause

This issue is caused by ESXi host disconnected from vCenter triggering the error.

Resolution

This issue is resolved in NSX-T 2.5.0.

Workaround:
As a workaround identify the disconnected ESXi host and either reconnect them or remove them from vCenter.

To identify the ESXi host disconnected the following command can be used on the NSX Managers:
#grep "connectionState.*disconnected" var/log/syslog

Example of output:
<182>1 2019-11-08T12:03:08.844Z NSX-MANAGER NSX 5061 SYSTEM [nsx@6876 comp="nsx-manager" subcomp="upgrade-coordinator"] response: Response:: status code:200 status:null body:123#012  "results" : [ {#012    "external_id" : "c105251a-XXXX-XXXX-XXXX-77d5cfadbd16:host-45",#012    "ip_addresses" : [ ],#012
(output omitted)
"value" : ""#012    }, {#012      "key" : "connectionState",#012      "value" : "disconnected"#012    }, {#012      "key" : "vendor",#012      "value" : "HPE"#012    }, {#012      "key" : "licenseProductName",#012      "value" : ""#012    }, {#012      "key" (output omitted)


To find out the ESXi host name from the ESXi host id, you use the vCenter mob and access the following URL:
https://{VCENTER_IP}/mob/?moid=host-id