Some nodes are not backing up configs as scheduled in NCM

Some nodes are not backing up configs as scheduled and the 'Overall Devices Backed Up vs. Not Backed Up' resource under CONFIG SUMMARY shows a few nodes not being backed up.

• Nodes might not be added to the NCM Config backup job.
• Nodes might not be using the correct Connection Profile and Device Template.
• Config Settings has a high value for Simultaneous Uploads/Downloads
• Some devices might return the prompt before dumping the configuration to NCM

1. Choose a node and manually download a config:
   1. Go to the Node Details page of an affected node.
   2. Select the Left Config tab and click the Download button.
2. If the config was successfully downloaded from the node, check the download job:
   1. From the main menu, click My Dashboards > Network Configuration > Jobs.
   2. Edit the Nightly Config Backup job.
   3. On the Choose Nodes tab, verify that all nodes are added to this job. If not, add them by doing one of the following:
      • Select 'Select Nodes', select the nodes you want to add, and click Add.
      • Select 'All Nodes' to add all NCM nodes.
3. To avoid random failures, check the settings:
   1. Go to Settings > All Settings.
   2. Under Product Specific Settings, click NCM Settings.
   3. Check the following settings:
      • Config Settings > Simultaneous Downloads/Uploads from 3 to 10 sessions.
      • Config Settings > Config Min Length from 1 to 11 lines.
      • Protocol Settings > Telnet/SSH Connection Timeout from 45 to 280 seconds.
      • Protocol Settings > Telnet/SSH Prompt Timeout from 15 to 180 seconds.
4. For Devices returning the prompt before the Config is dumped, there is no workaround. (This issue is seen on Netscaler devices issuing the show ns.conf command, while one member of the pair is successful and the other is not.)