Unable to connect agent with Scheduler
search cancel

Unable to connect agent with Scheduler


Article ID: 102689


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) Workload Automation Agent CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE - System Agent (dSeries)


After a newly installed agent has been introduced to the environment, it is unable to communicate with the scheduling engine.

How can we determine if a firewall port is allowing traffic between the agent and scheduler?


Workload Automation AE or Workload Automation DE running on Linux OS


Most organizations do not allow for telnet communications to be enabled by default. One can perform the following tests to ensure that communications over ports:

nc -v <hostname> <port>

For Example, to validate communications on the default agent port of 7520 from your scheduler (AE, DE), you would issue the command string as follows:

From the scheduler server:
nc -v linux-agent 7520

Provided the agent service is up and running on the agent noted above, you should receive a response indicating that we connected. It should look something like this:

[root@linux-ae-server]# nc -v linux-agent 7520
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to

If you do not receive response similar to the above, then it is likely that either the agent process is down or the communication port is blocked by a firewall. Consult your network administrator as well as your System Administrator (in case a locally installed firewall is running) for assistance in resolving the communication.