Hi Pratiman, Yu, Rich,
In my past experiences with the rsp probe, I have found in general that the probe can handle approx. 200 profiles. I have heard other reports that it can support up to 300 or much more but I have not witnessed this in a few larger global environments where I've performed rsp troubleshooting and analysis for customers where one or more or a set of profiles were failing.
Normally, I set the following in the rsp.cfg:
- Max data collection threads to 300
- Running threads Exit timeout to 180
- WMI Retry Delay set to 1200
- WMI Connection timeout set to 600
- SSH Connection Timeout to 30
- Command timeout to 120
Then, if a single or small set of profiles/machines fails intermittently, try deleting those machines from the rsp instance where they are failing and deploy another rsp probe instance and add them to it, to distribute the rsp profile processing. Cold start (Deactivate-Activate) rsp and test again.
In general, after testing a few rsp probe instances and determining the best configuration that ensures seamless profile processing, you can distribute an rsp probe package to change the settings on all machines where rsp is installed and keep the number of profiles at ~200 or less.
Best Regards,
Steve