Control-m server and control-m agent connectivity issue

abhipali · Post by **abhipali** » 30 Dec 2009 2:00

Hi All,

I am finding connectivity problem with one of my window control-m 6.2 fp 2 agent in my 6.2 FP4 control-m server. i m finding that when a lot of jobs trying to start on same agent at same time...agent goes in unavailable status for few seconds then come back shortly ...after that some of jobs come back in their execution status while other don't return and remain in unknown status...if any one has any idea what could be do to improve this..It is happening quite frequently and as of now its an headache for me.

anilgupta1981 · Post by **anilgupta1981** » 30 Dec 2009 2:44

Ask BMC. They will solve this issue.

abhipali · Post by **abhipali** » 30 Dec 2009 4:33

Hi Anil,

Have u faced similar issue? if any please let me know what was workaround

philmalmaison · Post by **philmalmaison** » 31 Dec 2009 11:18

probably you can change timeout parameters for you agent to see the result

regards
philmalmaison

Zakeer · Post by **Zakeer** » 01 Jan 2010 9:05

Hi,

Check with BMC if they are provding any fixpacks. These kind of issues happens mostly on windows system when large number of jobs are submitted agent goes unavailable (network disconnection) and come back after few min. One of the possible solution would be set resources for these jobs and make sure minimum number of jobs are submitted at once.

Hope this helps.

~Zakeer

abhipali · Post by **abhipali** » 02 Jan 2010 7:46

Thanks Zaheer,
i have already logged the case with BMC but did not get any definitive answer except to upgrade version 6.3 which is more stable according to BMC.

Hi Phil,

Can you please elaborate which parameter you are talking about and what would be the benefit.

abhipali · Post by **abhipali** » 10 Feb 2010 2:41

Hi All,

Can nay one help on this? i am still facing the problem continously and have tested different no. of jobs to check when this problem start.
The worst part is that BMC is still not bale to provide any solution for this problem.

Whenever large chunk of jobs starts TR mark the agent unavailable and it changes to available after some time and again same continues. No idea what is causing this?

Venkateshwarulu · Post by **Venkateshwarulu** » 10 Feb 2010 10:53

Hello,

I had exactly similar issue with my Control-M agent which is on Windows box. We have 12 cylical jobs that are triggering for evry 15 minutes. Every time i was getting the simialr alert that you have receving.

I have modified the submit time for 6 jobs (delayed by 30 sec) and it resolved my issues. Hopefully this will resolve your issue as well

. If posibble please try to change the submit time for your jobs.

I guess this issue is because of high traffic between server and Agent, Since all the jobs are trying to update the staus back to Control-M server.

Thanks
Venkat

philmalmaison · Post by **philmalmaison** » 11 Feb 2010 4:45

sapteus2-controlm [1] su - ctmagent
Password:
sapteus2% ctmagcfg

Agent Configuration Utility

1) Agent-to-Server Port Number . . . : [7007]
2) Server-to-Agent Port Number . . . : [7996]
For items 3 and 4 do not use IP address
3) Primary CONTROL-M/Server Host . . : [sapteus2]
4) Authorized CONTROL-M/Server Hosts : [sapteus2]
5) Diagnostic Level. . . . . . . . . : [0]
6) Comm Trace. . . . . .(0-OFF|1-ON) : [0]
7) Advanced parameters

s) Save and Restart CONTROL-M/Agent Services
q) Quit

Please enter your choice:7

Agent Configuration Utility - advanced menu

1) Days To Retain Log Files. . . . . : [7]
2) Daily Log File Enabled. . . (Y|N): [Y]
3) Tracker Event Port. . . . . . . . : [7997]
4) Logical Agent Name. . . . . . . . : [sapteus2]
5) Persistent Connection . . . . . . : [N]
6) Allow Comm Init. . . . . . . . . : [Y]
7) Foreign Language Support. . . . . : []

Locale (LATIN-1 mode only) . . .. : []
9) Protocol Version. . . . . . . . . : [07]
10) AutoEdit Inline. . . . . . . (Y|N): [N]
11) Listen to Network Interface . . . : [*ANY]
12) CTMS Address Mode . . . . . (IP|) : []
13) Timeout for Agent utilities . . . : [120]
14) TCP/IP Timeout. . . . . . . . . . : [120]
15) Tracker Polling Interval. . . . . : [120]

r) Return to main menu

Please enter your choice:

13/14/15 parameters can be ajust, but the best way is to be in tha last fixpack server and agent do you ?

regards
philmalmaison

abhipali · Post by **abhipali** » 12 Feb 2010 8:49

Hi phil,

i have windows agent 6.2 with FP2 and value of these parameters are 600,60 and 60 respectively. i think utility time out is required for control-m agent utilities that run back to server. no issue with this. However 14 and 15 can be mix but in which manner thats no idea. If you can give some idea its welcome.

philmalmaison · Post by **philmalmaison** » 12 Feb 2010 2:04

change TCP/IP Timeout and Tracker Polling Interval to the default values : 120

regards
philmalmaison

nakul · Post by **nakul** » 12 May 2010 5:35

hi abhi,

please let me know if the suggestion given by phil has worked.