vMotion fails with error: A general system error occurred: vim.fault.NotFound
search cancel

vMotion fails with error: A general system error occurred: vim.fault.NotFound

book

Article ID: 334897

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

You have configured vSphere Distributed Switch in you environment. When you attempt vMotion, you experience the below symptoms:

  • vMotion fails with below error:

    A general system error occurred: vim.fault.NotFound
     
  • You are able to ping over vMotion network without any issue.
     
  • VM settings shows the VM is connected to a network.
     
  • Port settings on vDS does not show the VM / Port ID.
     
  • In the %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\vmware-vpx\vpxd.log file, you see entries similar to:

    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=coreanchor opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] [MoDVSwitch::UpdatePortProxyHostInt] updating port [34] proxy host to [host-117]
    2017-07-20T16:59:44.882Z error vpxd[7F616A408700] [Originator@6876 sub=MoDVSwitch opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] [MoDVSwitch::CheckInPortKeySetInt] port [34] not found in dvs [DS_OMA01_ZZ_POD13_DC01].
    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=coreanchor opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] [MoDVSwitch::UpdatePortProxyHostInt] updating port [34] proxy host to [host-101]

    2017-07-20T16:59:44.882Z error vpxd[7F616A408700] [Originator@6876 sub=MoDVSwitch opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] [MoDVSwitch::CheckInPortKeySetInt] port [34] not found in dvs [DS_OMA01_ZZ_POD13_DC01].
    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=VmProv opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] Invoking callback type 2 on AutoStartManager
    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=VmProv opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] Invoking callback type 2 on CbkServiceMgrMigrateCallback
    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=VmProv opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] Invoking callback type 2 on ContextValidator
    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=VmProv opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] Invoking callback type 2 on CryptoManager
    2017-07-20T16:59:44.882Z info vpxd[7F616A408700] [Originator@6876 sub=VmProv opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] Invoking callback type 2 on DAS
    2017-07-20T16:59:44.882Z error vpxd[7F616A408700] [Originator@6876 sub=VmProv opID=MigrationWizard-applyOnMultiEntity-10193-ngc-aa-01] Get exception while executing action vpx.vmprov.InvokeCallbacks: N7Vmacore9ExceptionE(vim.fault.NotFound)


Environment

VMware vSphere ESXi 6.5

Resolution

To resolve this issue:

Note: Ensure to have a maintenance window before toggling the network.

  1. Right click on the VM and go to Edit Settings.
     
  2. Toggle the port group to another network and then back to the original.
     
  3. Navigate to the ports setting on the vDS: Networking > vDS > Ports.
     
  4. Verify that Port ID is listed for the VM.
     
  5. Perform the vMotion again.