Collecting environment details is useful when checking the compatibility of components.
- Determine if Guest Introspection is used in the customer environment. If it is not, remove the Guest Introspection service for the virtual machine, and confirm the issue is resolved.
- Collect environment details:
ESXi build version - Run the commanduname –a on the ESXi host or click on a host in the vSphere Web Client and look for the build number at top of the right-hand pane.
- Linux product version and build number
- /usr/sbin/vsep -v will give the production version
Build number ------------------ Ubuntu dpkg -l | grep vmware-nsx-gi-file SLES12 and RHEL7 rpm -qa | grep vmware-nsx-gi-file
- Collect NSX Data Center for vSphere version, and the following:
- Partner solution name and version number
EPSec Library version number used by the partner solution: Log into the GI SVM and run this command:
strings <path to EPSec library>/libEPSec.so | grep BUILD
- Guest operating system in the virtual machine
- Any other third-party applications or file system drivers
- ESX GI Module (MUX) version - run the command esxcli software vib list | grep epsec-mux.
- Collect workload details, such as the type of server.
- Collect ESXi host logs. For more information, see Collecting diagnostic information for VMware ESX/ESXi (653).
- Collect service virtual machine (GI SVM) logs from the partner solution. Reach out to your partner for more details on GI SVM log collection.
- Collect a suspend state file while the problem is occurring, see Suspending a virtual machine on ESX/ESX (2005831) to collect diagnostic information.
- After collecting date, compare the compatibility of the vSphere components. For more information, see the VMware Product Interoperability Matrices.