NSX Guest Introspection Platform Host Agent (MUX) Logs
NSX Guest Introspection Platform
Host Agent (MUX) LogsIf virtual machines on an ESXi host are not being protected by policy configured Endpoint Security solution or if there are alarms related to Endpoint Security Service VM and host agent communication then the
NSX Guest Introspection Platform
Host Agent(MUX) may have issues that need to be analysed. This section describes log format, log location for the Host Agent (MUX) and how to ensure the Host Agent (MUX) service is running on the ESXi host.Log Path and Sample Message
MUX Log path |
|---|
/var/log/syslog |
NSX Guest Introspection Platform
host agent (MUX) messages follow the format of <timestamp>ContextMUX<[ThreadID]>: <message> For example:
2022-08-25T11:42:02Z ContextMux[54425342]: [INFO] (EPSEC) [54425342] NSX Context Multiplexor 17883598. [3.1.2.0.0] 2022-08-25T11:42:02Z ContextMux[54425342]: [INFO] (EPSEC) [54425342] VMkernel localhost 6.7.0 #1 SMP Release build-13006603 Mar 26 2019 13:38:24 x86_64 2022-08-25T11:42:02Z ContextMux[54425342]: [WARNING] (EPSEC) [54425345] Not sending events. MuxHandler has not been registered.
In the above example
- [ERROR] is the type of message. Other types can be [DEBUG], [INFO]
- (EPSEC) represents that the messages are specific to Endpoint Security
Enabling and Viewing Log Files
To change log levels, perform these steps on the ESXi host command shell:
- Set theNSX Guest Introspection Platformhost agent (MUX) logging level.~ # nsxcli -c set service nsx-context-mux logging-level debugoff- This is intended to turn off loggingfatal- Designates very severe events that may cause application to aborterror- Designates error events that may allow application to continue runningwarn- Designates potentially harmful situationsinfo- Designates coarse-grained informational messagesdebug- Designates fine-grained informational messages for debugging purposestrace- Designates verbose log messages
- View theNSX Guest Introspection Platformhost agent (MUX) log messages in the/var/log/syslog.logfile on the ESXi host. Check that the entries corresponding to the global solutions, solution ID, and port number are specified correctly.
- The default logging option forNSX Guest Introspection Platformis info and can be raised to debug to gather more information.
- To get a better idea of what theNSX Guest Introspection Platformis doing or check the communication status, you can check the logs on the ESXi host.NSX Guest Introspection Platformlogs are written to the host/var/log/syslogfile. This is also included in the ESXi host support logs.
- If you run into issues with the VIB installation, check the/var/log/esxupdate.logfile on the ESXi host. This log provides accurate information to know the reason the package was not successfully installed. This is a common issue forNSX Guest Introspection Platforminstallation issues.