Is there a limit of ControlM Agent per ControlM Server

sharonc · Post by **sharonc** » 20 Apr 2007 7:48

Hi,
I would like to find out, if there is a maximum limit, or recommended limit of how many ControlM Agents per ControlM Server?
Thanks.

Post by **fyot** » 20 Apr 2007 8:46

Hi,

I don't think so. In fact, there are some limits using the database.
Control-M Agent are not concerned by those limits.

May be it could be quite different with the version 6.3.01 seeing that you can manage Control-M Agent with the Configuration Manager using Control-M/EM database.

sharonc · Post by **sharonc** » 26 Apr 2007 1:14

So, if the version of controlm is 6.1.01, there's no limit to the number of controlm agents per controlm server?

Post by **fyot** » 26 Apr 2007 10:41

Hi,

I think there are no real limits.

GrahamH · Post by **GrahamH** » 29 Apr 2007 12:16

Hi SharonC

There are no physical restrictions on how many agents you connect to the CTM server. The CONTROL-M labs will usually say that they recomend about 128 agents per server. However, that said, it all depends on the strength of the CTM Server and the workload profile being pushed through the agents. I have a customer who runs around 50,000 production jobs per day across several hundred agents, but they have over 1000 agents connected to a single CTM Server as many of these jobs are daily housekeeping across all agent macines. So I would look at the level of potential activity you intend to schedule and the specification of the CTM Server machine as these things can influence the number of agents connected.

Graham

sharonc · Post by **sharonc** » 30 Apr 2007 5:25

Okay, thanks for the extra information. It helps me understand a bit more.

sharonc · Post by **sharonc** » 01 May 2007 7:56

A lot of the agents become 'unavailable' every now and then. I'm not sure why. Could having too many agents under one ControlM server be a factor?

Post by **fyot** » 01 May 2007 8:12

Hi,

Normally No.
Agents is "Unavailable" if the Control-M Server lost the communication with the agent.

Many reasons :
- Server reboot
- Control-M Agent Services or deamon down
- Network Issue
- etc ...