vShield Edge is unmanagable after upgrading from vCNS 5.5 to NSX 6.2.x
search cancel

vShield Edge is unmanagable after upgrading from vCNS 5.5 to NSX 6.2.x

book

Article ID: 342291

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:

After upgrade from vCenter Network & Security 5.5.x to NSX 6.1.x or 6.2.x:

  • vShield Edges on versions 5.5.0 & 5.5.2 are unmanageable.
  • While trying to manage the Edge, you see entries similar to:

    'Failed to communicate with NSX Edge vm vse-Esyst_GW(1c72322f-4940-9a57-f637d7aebc72)-0. Error coe: VIX_E_FILE_NOT_FOUND was returned by VIX API.
    2016-07-26 15:47:27.463 GMT-00:00 ERROR vixCommandExecutor-1 VixCommandExecutor$ProcessResponseTask:702 - Vix Command 485352 failed, reason com.vmware.vshield.edge.exception.VixException: vShield Edge:10013:Failed to communicate with NSX Edge vm vm-4256. Error code VIX_E_FILE_NOT_FOUND was returned by VIX API.
    2016-07-26 15:47:24.122 GMT-00:00 ERROR edgeVseMonitoringThread InventoryUtils:418 - Failed to discover the vm : 'null' using vcUuId = '421ced9b-c0c4-2786-f4d2-4ec18692d056
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vCloud Networking and Security 5.5.x
VMware NSX for vSphere 6.2.x

Cause

This issue occurs due to a mismatch between vc_uuid stored in Edge module and in vCenter Server.

Resolution

This is a known issue affecting NSX for vSphere 6.2.x.

Currently, there is no resolution.

To work around this issue, contact VMware Support and note this Knowledge Base article ID (2149104) in the problem description. For more information, see How to Submit a Support Request.