kentschuAre people using the SNMP function regularly? Is it working well?
Did they ever fix the "SNMPGET.EXE" problem that existed in the past where a ton of that EXE process would run on servers constantly and drag down performance?
droddenUnfortunately I don't have access to it at this point and couldn't give you any info, but it didn't stop the flood of SNMPGET commands, just lessened the load they placed on the processor. There is a SQL query you can use to limit the number of concurrent threads that are opened. Unfortunately, I don't have that either at this time but I may be able to dig it up for you. I believe it exists on the forums somewhere, but may also be available via standard support. I believe it can also be adjusted in the KaseyaD.ini file for an agent. The line 'SNMPConcurrentThreads' has a default value of thirty, and Kaseya recommends changing this to 5. The SQL query allows you to change this from the backbone, but you could easily write a script in Kaseya to query the contents of that file and change any values of 30 to 5. Unfortunately, with the original SNMPGet process, 5 threads still caused the CPU to peg.