topic Re: Why my host not communicate with new AG? in Open Q&A

Why my host not communicate with new ActiveGate?

Aledang — Tue, 24 Sep 2024 12:35:46 GMT

Hello everyone. I have installed two new ActiveGates for my environment and assigned them to a new network zone. In the deployment status section, I set the new network zone to a host, and:

the host, after rebooting, is configured in the new network zone.
However, the host is still communicating with the old ActiveGate (in the default network zone) and not with the new ones

Any suggestions?

Re: Why my host not communicate with new AG?

p_devulapalli — Thu, 19 Sep 2024 03:41:24 GMT

Hi @Aledang , did you check if you are able to reach the new AG from the OneAgent on the AG port? Could be that the OneAgent is unable to communicate to the new AG and defaulting to old using one?

Re: Why my host not communicate with new AG?

PacoPorro — Thu, 19 Sep 2024 06:40:45 GMT

Please check with oneagentctl that the new AG is present as a communication endpoints
https://docs.dynatrace.com/docs/shortlink/oneagentctl#show-current-communication-endpoints

Check if you can access the AG via the configured port (usually 9999)

You can create a diagnostic file and check the logs from the agent.
https://docs.dynatrace.com/docs/shortlink/oneagent-diagnostics#contents

Re: Why my host not communicate with new AG?

Peter_Youssef — Fri, 20 Sep 2024 05:49:33 GMT

Hi @Aledang

PFA example to modify the connection endpoints through the UI as alternative to oneagent communications-oneagentctl

specify environment ID
token with the required scope

Both connection endpoints modification methods are applicable the trick here:

the server will keep sending the monitoring traffic to the old AG, until you stop Oneagent service > restart the monitored processes > Restart the oneagent service, it should work as expected.

Thanks.