Services and performance impact with Guest Introspection installed in NSX 6.4.1

Products

• VMware vDefend Firewall

Issue/Introduction

Symptoms:

• May take long time to vMotion VMs between hosts with Guest Introspection enabled.
• During vMotion or storage vMotion, the performance impact on other guest VMs.
• Frequent “Mux is disconnected” event logs observed in VM vmware.log file
• In the /vmfs/volumes/datastore/virtual machine/vmware.log file of the ESXi host, you see entries similar to:

mux is disconnected.

• In the /var/log/syslog.log file on the ESXi host, you see entries similar to:

2018-06-28T06:37:03Z EPSecMux[69545]: [ERROR] (EPSEC) [69545] PANIC: NamespaceDb.cpp:AccessNamespaceDb():83 Function call to read_key failed
2018-06-28T12:11:27Z EPSecMux[74329]: [ERROR] (EPSEC) [74329] PANIC: NamespaceDb.cpp:AccessNamespaceDb():83 Function call to update_key failed

• In the VM vmware.log file, you see entries similar to:
• 2018-07-02T10:58:46.833Z| vcpu-0| I125: Guest: vsep: AUDIT: VFileSocketMgrCloseSocket : Mux is disconnected
  2018-07-02T17:31:09.253Z| vcpu-0| I125: Guest: vsep: AUDIT: VFileSocketMgrCloseSocket : Mux is disconnected
  2018-07-02T18:12:46.326Z| vcpu-0| I125: Guest: vsep: AUDIT: VFileSocketMgrCloseSocket : Mux is disconnected
  2018-07-02T18:43:09.888Z| vcpu-0| I125: Guest: vsep: AUDIT: VFileSocketMgrCloseSocket : Mux is disconnected
   
• Problem observed in NSX 6.4.1 only.
  In the vsm.log file of the NSX Manager, you see entries similar to:
  
  2018-07-05 11:32:35.605 CEST ERROR messagingTaskExecutor-8 EndpointConfigurationManagerImpl:539 - - [nsxv@6876 comp="nsx-manager" errorCode="MP7018" subcomp="manager"] Configuration of host host-21700 failed: failed to send configuration to mux: Status code: 65539, Message: "Error - Mux VMCI socket"
  
  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.4.x

Resolution

This is a known issue affecting VMware NSX for vSphere 6.4.1.

This issue is resolved in 6.4.4

Workaround:
To work around this issue, contact Broadcom Support and note this Knowledge Base article ID (318254) in the problem description.