What is p_ctmag.exe?
If Control-M/Agent is running and listening on the SAPN listening port, you should check it out. To check the listening port, run the following command at Control-M Agent host: Unix: netstat -an | grep
The Local Address Foreign Address status iscp4 0 0 0 *.7006
If there is no line in netstat command output, then the Control-M/Agent services will not listen on this port.
If this is the case, please proceed directly to "Verifying Configuration"(Step 4) in this document.- From the netstat command output above, there is a process listening on this SAPN port. - Perform a telnet to the Control-M/Agent host name and SAPN port number, from within the same host using below command to verify the port can be connected:
You can use the telnet option.
To exit from the interface, enter 'CTRL> + ]' and follow by 'quit'.
If the Control-M/Agent process is running, execute the following. The following will be displayed if the Control-M/Agent is running.
1 0 01:20 is the user'spid.
- If there is no entry returned, it means Control-M/Agent is not running and there is another application using the port number. - Change the Server to Agent port number (SAPN) by following the steps in the "Changing Agent Port Configuration" (Step 5) section of this document.
There is a possibility of a configuration issue with the configuration if there is a refused message from the telnet command. Proceed to theVerifying Control-M/Agent Configuration section of the document.
Step 4 Verifying Control-M/Agent Configuration:- After login as Control-M/Agent user on the Control-M/Agent host, executes 'ctmagcfg' command to check the port settings as below.1) Agent-to-Server Port Number . . . : 2) Server-to-Agent Port Number . . . :
- Make sure that the port numbers are correct and the Control-M/Agent SAPN port is not used by any other application on the machine.- This can be verified again by stopping the Control-M/Agent services (for Unix, '$ Agent Home/ctm/scripts/shut-ag' or from Windows Services.msc) and check with "netstat -an" command to see if the Server to Agent port number (SAPN) is still active.On Windows:netstat -an | findstr "7006" On Unix:netstat -an | grep 7006
If the port is used by another application, then change the port by following the steps in the "Changing Control-M/Agent Port Configuration" document. The Control-M/Agent port configuration needs to be changed after login as a user or local administrator. To find a port that is free, use the "netstat -an" and look for a port that is higher up.
This example will look at the port. If you don't see any lines returned, this port is not used by any application. The port can be set as a new server to agent port number if you check with the system administrator. The Control-M/Agent services should be stopped.
ctmagcfgii is executed. You can change the value by selecting the server-to-agent Port Number option. The agent should not be changed to the port number.
Accept the defaults for the rest of the parameters, or change only the port number. You can save the change by selecting the's' option. Start Control-M/Agent services can be accessed from Windows Services.msc.
The new port 7016 can be connected to via Verify telnet.
You can use the telnet feature on the localhost.
If the connection still fails, check with the system administrator or contact the support team for assistance. There is an issue with the configuration of the machine. The Control-M/Server host can be used to update the server-to-agent configuration.
It executes 'ctm_menu'. Select the Parameter Customization option. Select the Parameters for Communicating with Specific Agent Platforms. The host ID of the agent platform is agent>v.
Step 6 Performing Control-M/Agent communication diagnostics:- Control-M/Agent communication diagnostics can be performed by running 'ag_diag_comm' command on the Control-M/Agent host machine. - This command have to be executed under the Control-M/Agent user account for Unix and Administrator for Windows. - Once the command completes, verify all of the entries are correct and that the UNIX/System ping to Control-M Server is successful. - If the UNIX/System ping did not succeed, please approach system administrator to verify that host name of the Control-M Server can be resolved on the Control-M/Agent host. - If the 'ping' command succeeds or the system administrator has verified the name resolution, then perform 'ag_ping' command at OS prompt.i.
If 'ag_ping' completes, then you should verify Control-M/Agent connection. If 'ag_ping' fails, then continue on troubleshooting the Control-M/Server.Step 7Performing Control-M Server communication diagnostic:- The following is to be executed on Control-M/Server host with Control-M/Server user account on Unix or Administrator on Windows.a.
The 'ctm_diag_comm' is a program that runs on the Control-M/Agent host. The Control-M/Agent is ready to be used if the 'CTMS ping to Agent or remote host' succeeds. If the ''CTMS ping to Agent or remote host'' fails or the status is 'unavailable'- Please check with a system administrator and make sure that the Control-M/Server host can resolve the host name of the Control-M/ Agent. - Typically, this is Name Resolution issue, and depending on environment, local /etc/hosts file or DNS server host table will need to be updated.- If there is firewall in the environment, please alert infrastructure team of the ports involved.- The firewall communication requirement is as follows:- Any port from the Control-M/Server needs to be able to initiate a connection to the agent on the SAPN. - Any port on the Control-M/Agent needs to be able to create a communication to the Control-M/Server on the ASPN. - If NAT is in used or have any other questions, please contact BMC support.NOTE: 'UNIX ping to Agent or Remote host' may appears as 'Failed' on some hosts because the OS Ping executable is disabled for the account due to security hardening. If this is the case, this will not affect the communication. Please investigate this with the system administrator.
Additional Information----------------------------For information about Persistent Connections, see the following resolution: Connecting an Agent and Server with persistent connections when using a firewall: 000026617.The following error messages in Control-M/Server's NS logs may be observed:0609 11:27:22.095 NS: Agent
