Software Delivery performance turning that requires multiple reboots on the agent machines

Products

• CA Client Automation - IT Client Manager

Issue/Introduction

When CA Client automation Software Delivery(SD) upgrades packages on the agent machines that require multiple reboots of the agent machines, the administrator could observe that some agents may not be able to connect to Scalability machine on time which results in package upgrade failure or the package would need multiple tries to be upgraded. This article discusses some parameters the administrator could use to improve the SD performance.

Environment

• CA Client Automation 14.5 and 14.6

Resolution

Consider adjust these parameters and changes

1. If the number of agents is large like 500 agents, change these defaults to allow more simutaneous connections and executions
   
   Concurrency: Maximum number of simultaneously connected agents on Scalability Server (MaxSimConnect) = 100
Concurrency: Maximum number of simultaneously executing agents on Scalability Server (MaxSimActCheck) = 50
   
   For example
   
   Concurrency: Maximum number of simultaneously connected agents on Scalability Server (MaxSimConnect) = 200
Concurrency: Maximum number of simultaneously executing agents on Scalability Server (MaxSimActCheck) = 100
   
   
2. Modify these two from defaults to allow more retries and more time for retry
   
   DSM/Software Delivery/Agent/Communication: Maximum number of retries (Windows) = 30
DSM/Software Delivery/Agent/Communication: Maximum number of seconds to retry = 1800
   
   For example
   
   DSM/Software Delivery/Agent/Communication: Maximum number of retries (Windows) = 10
DSM/Software Delivery/Agent/Communication: Maximum number of seconds to retry = 3600
   
   
3. Delay startup of agent machines to allow more time for the system to fully start and initialize the network
   
   sc config hmagent start= delayed-auto
sc config caf start= delayed-auto

Additional Information

Software Delivery Agent Policy Group