지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight Agent Manager 7.1.0 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers
Understanding how the Agent Manager communicates with the Management Server Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager Starting or stopping the Agent Manager process Frequently asked questions
Configuring the Agent Manager Advanced system configuration and troubleshooting
Configuring Windows Management Instrumentation (WMI) Configuring Windows Remote Management (WinRM) UNIX- and Linux-specific configuration
Monitoring the Agent Manager performance Deploying the Agent Manager to large-scale environments

Troubleshooting

If you have verified all of the WinRM configuration information and are still experiencing connection issues, the following techniques may be helpful for diagnosing the problem.

Enabling specific TLS protocols

If an agent could not establish secure connection to a target server, verify if the target server supports TLS protocol version negotiation. To enable specific TLS protocols on the agent manager, run the Agent Manager with the following switch:

-Djdk.tls.client.protocols=TLSv1, TLSv1.1, TLSv1.2

Verifying setup

To check whether a listener is configured for WinRM, you can issue the following command and observe its output:

The Port and Transport elements contain important information. The above command output identifies an HTTP listener on port 5985.

To see a full list of WinRM configuration values for the WinRM service that the Agent Manager is to use on the remote machine, you can issue the following command and observe its output:

The important properties are AllowUnencrypted (it indicates whether HTTP is allowed or not), and the Auth values that are set to true (enabled), namely Basic and Negotiate. In this example, both authentication types are enabled.

For more information on setting up for HTTPS, see About WinRM authentication and the Agent Manager .

Identifying common causes of WinRM failures

The following conditions can result in a WinRM failure:

The AllowUnencrypted WinRM service configuration setting is false, and HTTP is used on the remote machine.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택