topic OneAgent in Servers with DB2, but only running as cloud-infra (instead of full-stack) in Open Q&A

OneAgent in Servers with DB2, but only running as cloud-infra (instead of full-stack)

waikeat_chan — Mon, 16 Oct 2023 14:17:20 GMT

As mentioned in here (https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/troubleshooting/troubleshoot-oneagent-installation/#expand-873what-can-i-do-when-oneagent-blocks-a-port-i-need) and here (https://community.dynatrace.com/spaces/482/dynatrace-open-qa/questions/190238/oneagent-vs-db2.html),

it is good to edit the watchdog port-range for the servers that are running DB2 to avoid port-conflict.

While this definitely is a concern if the OneAgent inside it is running as full-stack, I am wondering how about OneAgent in full-stack? do I still need to do it? Is this still a concern if OneAgent is running only in cloud-infra mode?

Best Regards,
Wai Keat

Re: OneAgent in Servers with DB2, but only running as cloud-infra (instead of full-stack)

The_AM — Wed, 21 Oct 2020 03:44:34 GMT

Hi Wai,

In this scenario you described, you do need to modify the port range for the watchdog in both cloud-infrastructure and full-stack modes of OneAgent.

Andrew

Re: OneAgent in Servers with DB2, but only running as cloud-infra (instead of full-stack)

Julius_Loman — Wed, 21 Oct 2020 06:07:16 GMT

Just check if your DB2 listener is running on 50000 - that's just the default port, but I've seen in many environments listener configured on a different port. In that case you don't need to reconfigure the watchdog.