Foglight Agent Manager 7.3.0 - Foglight Agent Manager Guide

Advanced system configuration and troubleshooting

This contains platform-specific configuration information for configuring Foglight® Agent Manager on Windows® when using Windows Management Instrumentation (WMI) or Windows Remote Management (WinRM) for remote monitoring access.

NOTE: WMI and WinRM are two different mechanisms that monitoring agents can use to establish remote connections. In most scenarios, only one of these mechanisms needs to be configured. The preferred mechanism is WinRM because of WMI scalability limitations.

This also describes platform-specific instructions for configuring the Foglight Agent Manager on UNIX®.

Throughout this , “the agent” is used as a placeholder for any Foglight agent that encounters these issues.

Configuring Windows Management Instrumentation (WMI)

To remotely monitor a Windows® machine, some Foglight® agents require access to the WMI services, and specifically to the WMIConnectionService. This section outlines potential issues that may be encountered by agents attempting to access WMI, and provides solutions or workarounds.

NOTE: WMI is not allowed for remote connection in FIPS-compliant mode since the NTLM authentication it uses is non-FIPS compliant.

In order to access WMI, the user that the monitoring agent connects as must have sufficient credentials. Any user included in the Administrator group on the monitored machine already has the required access levels. For more information, see Minimum requirements for Windows Management Instrumentation.

There are several OS and environment-specific issues that may arise when using a Foglight agent to monitor a Windows machine remotely. This section provides solutions for the following issues:

WMI IPv6 connection support

Starting with the Foglight Agent Manager version 5.9.1, the WMI connection with unique local IPv6 Address and link-local IPv6 Address is supported on the Agent Manager running on Windows and Linux.

Windows Firewall interference

Since the agent connects remotely (that is, from an external source) the Windows® Firewall can interfere with operations. In such cases, it is recommended that you initially try disabling the firewall to determine if that allows the agent to connect. When the agent can connect with the firewall disabled, re-enable it and open the following ports: