- Fail to add a newly installed Control-M/Agent on Control-M/Server using Control-M Configuration Manager (CCM)
OR
After applying new firewall settings, multiple existing Control-M/Agents become unavailable randomly and self-recovered after a few seconds.
- When comparing the output from the ctm_diag_comm and ag_diag_comm utilities, all configurations such as communication protocol, protocol version, and ports match up.
- The ag_diag_comm output shows a successful connection but the ctm_diag_comm shows the following error in the output:
Agent: <agent host>, Msg: Agent not available: Socket closed due to unknown reason
- The following error can be seen in the logs:
Internal communication error after 59 seconds [<agent host>/<agent IP>:<server to agent port>]
- The Control-M/Server logs (<Control-M/Server home>\ctm_server\proclog\) may have messages like "connection unexpectedly closed while service waiting for a message".
- However a telnet to the agent on the server-to-agent port is successful

Check with the network and firewall team regarding the network disconnections

Some firewalls have application awareness setting turned on and it may interpret the Control-M traffic as it was on the standard Control-M TCP port. Disabling application awareness setting to disable packet inspection on the server-to-agent and/or agent-to-server ports can resolve the problem.