1 of 1 people found this helpful
Perhaps another application is using ports 7005/7006 on that agent. You could try defining the agent to use a different set of ports and see if that resolves the issue.
4 of 4 people found this helpful
You follow the following troubleshooting steps to identify the issue.
1. Check the telnet on agent to server over the port 7005 and server to agent port 7006.
2. check if the port 7006 is used by any other application using netstat -an|grep 7006, if it is a Windows server use netstat -an|findstr "7006"
3. Run the ag_diag_comm on agent machine and ctm_diag_comm agent_ip on server machine and check if you find any difference.
4. You may also run ag_ping on agent machine to check if the agent is connecting to the ctms server.
Hope this helps.
The agent is port is already configure as below
Server to Agent Port is 7026
Agent to Server Port is 7025
I see the > CTMS ping to agent is "Failed"
Can you please check if the proclog folder has file starting with "ag_ping*" or log files generated at the time of fluctuation. please check those log files for any specific error statement & post it here.
2 of 2 people found this helpful
Those are not the default values, I suspect the person who originally installed the Agent had their reasons for using them instead of the defaults (i.e. 7005/7006).
The ports are not officially reserved for Control-M but are usually recognised as "standard" to be used for the Control-M Agent. However I have found other products that sometimes use the same (e.g. Peoplesoft) and obviously you cannot guarantee a lost & confused admin (who doesn't know that Control-M was there first) might mistakenly use them.
BMC has a step-by-step guide for you in this situation -