To increase the number of threads used in polling use the following step:
Locate the DMT version of the software being used.
- Navigate to <base dir>/smarts/bin.
- Run the command ./sm_server --version
- Look for version number next to the word Foundation or DMT
For Foundation/DMT pre-version 9.x use the following steps: These versions are beyond EOSL and not supported by EMC.
- Edit file with BASEDIR/IP/smarts/bin/sm_edit conf/icf/DEVSTAT.import.
- In this file, find the section, "SNMP_AccessorInterface::DEVSTAT-SNMP-Poller", which controls the number of threads used for SNMP polling.
- Update the key, "num_threads" to the value you require, not to exceed 50.
For Foundation/DMT versions 9.x and up use the following steps: See current EOSL timings on the Smarts Product Pages.
- Edit file with BASEDIR/IP/smarts/bin/sm_edit conf/icf/FULL_DEVSTAT.import.
- In this file, find the section, "ICIP_SNMPAccessorInterface::DEVSTAT-SNMP-Poller", which controls the number of threads used for SNMP polling.
- Update the key, "num_threads" to the value you require, not to exceed 50.
- If you are using the Smarts Solution Pack please do not increase this key, "num_threads" to the value you require, not to exceed 25. This will adversely impact client connections timing out and will lead to issues with hitting the File Descriptor limits on Linux and CentOS Servers and causing the IP domain to crash.
Restart the server to effect these changes
Please note that the increasing the snmp polling threads does not always increase performance, the law of diminishing returns applies here.
It is suggested to start at 10, then move to 20 and 25. *See the note above if you are using the Smarts Solution Pack (Watch4Net) with your Smarts environment. Evaluate the balance between CPU usage and average late polling and let the IP domain run with the updated number for at least 24 to 48 hours in testing.