WA Agent in DMZ (cluster) may stop communicating with the DE manager

Products

• CA Workload Automation DE - Business Agents (dSeries)
• CA Workload Automation DE
• DSERIES- SERVER
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

The WA Agent appears as Agent down on dSeries (DE) side.  The traclelogs show the following error:

20200101 00:00:00.132 [dm:communications:exception] [ERROR] DM.OutputMessageQueue.AGENT1234: [2020-01-01_00:00:00.132] Exception caught sending to AGENT1234: Destination AGENT1234 sent "x'Y[gop<w1234W=" from AGENT1234, not the expected ACK. - [Originator: WA_MANAGER_7500]

 

Environment

Release : 12.0

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Cause

The manager(s) send its own address to agent(s) if there is any change.  This can cause issues if agents are in cluster or in DMZ.  Agents may not have direct access to the managers and all traffic may go through particular route or firewall.  The agentparm.txt may have address of DMZ/firewall as manager address.

 

Resolution

Set the following setting to false in Topology (Desktop Client -> Admin -> Topology -> Agents -> <Agent name>

Remember Manager address changes between restarts.

Additional Information

See the following link for details on the property.