You should see the Linux box in the list of devices. Go to Monitor > SNMP Monitoring > Assign SNMP and click on the name of the server for which you ran the scan. Hopefully the scan from step 1 has completed by now.I won’t set an alarm on the other counters (i.e. On a system with 512MB, that means below about 26,000KB. For an alarm, it looks like Linux generally keeps 10% – 20% of memory completely free (memAvailReal), so I’ll try an alarm on memAvailReal going below about 5% of memTotalReal. Unfortunately Kaseya doesn’t allow calculations on counters, so we’ll have to monitor memAvailReal, memBuffer, memCached, and memTotalReal. Memory monitoring isn’t as straightforward.Back in the main SNMP Monitor Sets window, add the monitor on dskPercent.A fairly easy workaround was to directly edit the XML for an existing SNMP set, adding in the objects I want to use, then to import that SNMP set. It may be that I don’t have permission to update the object list. Note: this is the way it is supposed to work, but for some reason, I was not able to add the MIB objects from the MIB tree. If the object you want to monitor isn’t listed, you’ll need to import into Kaseya the UCD-SNMP-MIB mib file (available near the bottom of this page): click Add Object then follow the screen instructions to Load MIB, Add MIB Objects that you’ll use, then Remove MIB. Click Add to add your first MIB object.Go to Monitor > Edit > SNMP Sets > Edit an existing SNMP set (or Add a new one).Work on the following while the scan runs. Used the community name you specified in step 2 above. Go to Monitor > SNMP Monitoring > LAN Watch and schedule a scan from one of your servers with Enable SNMP checked. Make sure Kaseya can see your newly configured Linux machine as an SNMP device.If you want to start from the simple SNMP Set that I created, you can download it from the bottom of this article, import it into Kaseya, and pick up at step 8. These are the steps to do that from scratch. this article).įinally, set up the SNMP monitoring set in Kaseya. Update : at least on CentOS, memTotalFree is the sum of memAvailReal + memAvailSwap and seems like a more commonly-used basis for determining available memory (cf. Divide that total by memTotalReal and you would have percent free. My understanding is that “free” memory is made up of memAvailReal + memBuffer + memCached (buffer and cached are used by the operating system but could be allocated to programs if necessary). Besides the SNMP results, you can try the free and cat /proc/meminfo commands to see how memory is allocated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |