Viewing logical switches in the vSphere Web Client displays the error: "Internal server error has occurred"

Products

• VMware NSX

Issue/Introduction

Symptoms:
When viewing logical switches in the vSphere Web Client, you experience these symptoms:

• The vSphere Web Client displays the error:
  
  Internal Server error has occurred.
  
  
• Only some ​of the logical switches are impacted and you are not able to manage the Logical switches impacted from the vSphere Web client.
• In the vsm.log file of the NSX Manager, you see entries similar to:
  
  2018-04-02 07:52:33.642 GMT INFO http-nio-127.0.0.1-7441-exec-7 EdgeFacadeImpl:1451 - Returning from getEdgesOnVirtualWires in interval 19
  2018-04-02 07:52:34.758 GMT WARN http-nio-127.0.0.1-7441-exec-2 RemoteInvocationTraceInterceptor:87 - Processing of VsmHttpInvokerServiceExporter remote call resulted in fatal exception: com.vmware.vshield.vsm.vdn.facade.VdnInventoryFacade.getUiVirtualWire
  java.lang.NullPointerException
          at com.vmware.vshield.vsm.vdn.facade.VdnInventoryFacadeImpl.countActiveHostsByVirtualWire(VdnInventoryFacadeImpl.java:638
          
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX for vSphere 6.3.x
VMware NSX for vSphere 6.4.x

Cause

This issue occurs due to stale entries in the NSX Manager database.

One of the ways the NSX database will be inconsistent with the vCenter Server is when a VM becomes a template in vCenter Server and there is config changes on the VM template. Any changes to the VM templates are not synced with NSX unless they are converted back to VM.

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.5.

 

Workaround:
To work around this issue, file a Support Request with VMware Support and note this Knowledge Base article (54442) in the problem description and upload the NSX Manager diagnostic information.

• Do not take templates from VMs connected to one or more Logical Switches
• Otherwise convert the template back to a VM to sync latest updates to NSX inventory. This will remove stale entries in DB and get latest sync from VC, making NSX DB consistent with VC and there by resolving the issue. You can then convert back the VM to a template. You can then convert back the VM to a template.

For more information, see:

• Collecting diagnostic information for VMware NSX for vSphere 6.x (2074678)

Additional Information

Impact/Risks:
You are not able to manage the Logical switches impacted from the vSphere Web client.