hi expert.
I have been asked by customer regarding what is the maximum concurrent connection supported by ncm to do batch upload to devices. and what is the best number for the setting.
kindly please help me..need to update asap to end user.
from my under standing
1 job = 10 device to push config. if I have 1000 device means I need to make 100 job. is it correct.
Good morning,
Are you referring to the maximum concurrent SSH connections within NCM? This number can be changed, what are you trying to accomplish? Have you considered using a job?
Bryan
yes. user are running multiple jobs to upload config update to their device. so they asking what is the maximum job can be run to update devices at one time.
Those settings can be configured under the NCM settings. Follow this link for instructions: Where to adjust Telnet and SSH connection and prompt timeout on NCM 7.7 - SolarWinds Worldwide, LLC. Help and Support
is there is any limit ?
Hi mistik84 I believe what you are referring to is the "Simultaneous Downloads/Uploads" which can be found in Settings > All Settings > NCM Settings > Config Settings.
It is set to 25 by default and can go up to a maximum of 100. If you are backing up more devices than that you should consider breaking up your backup schedules into smaller groups to avoid timeout issues.
Thanks
David
it mean break 1 job running how 10 per device.
Sorry I’m not sure I understand.
It rolls through them with 10 active sessions at a time, but as soon as it finishes one of those 10 it moves on to connecting to the next device and running the script there. I've had jobs running across several thousand devices but it tends to take a few hours to finish.
Is that 10 concurrent max per NCM? or Per job? I want to know if multiple jobs can be launched simultaneously?
Using the discussion above for example..
5 Jobs x 10 devices each = 50 simultaneous firmware upgrades?
Are there limitations?
If you wanted to run more jobs at once I would not even bother with trying to split the work into separate jobs, just increase the limit in the NCM settings. I am sure there is a limit, but that default limit has been there for years through many product changes so maybe you could squeeze in a lot more concurrent jobs, or maybe just a few more jobs. Just change the value, run a backup and see how it goes in the log files compared to past executions of that same backup.
