CPU, Disk and Memory Monitoring using SNMP
Monitors of SNMP type for CPU, Disk and Memory are associated to the devices based on the device template definitions. For instance, for Linux servers, the default template has SNMP-based monitors associated. So, all Linux servers have SNMP-based resource monitors associated to it. In the device snapshot page you can see the dial graphs for these three resource monitors.
All the server templates have the monitors defined for various host resources. By default, the CPU, disk and memory monitors are associated to the servers. The device snapshot page displays the values of these monitored resources with dial graphs.
If you don't see these monitors associated to the device, it could be due to any of the following reasons:
- These monitors are not included in the device template. Go to the device template and include the monitors.
- SNMP is not enabled on the device. Enable SNMP and associate the monitors to the device once again.
- Incorrect SNMP credentials are associated. Check the credentials like SNMP version, community string etc.
Steps to add the monitors to the device again:
- From the Central/Probe web client, go to the device snapshot page.
- Under the Monitors tab and click on Performance Monitors.
- You will see the monitors displayed on the right if associated. Click on Add Monitors button on the right.
- From the list of monitors, select the SNMP monitors for CPU, Memory, and Disk Utilization.
- You can also add other required monitors like Partition monitors etc.
- Click on OK.
- The selected monitors are associated to the device and the resources are monitored.
To check if the SNMP agent in the device returns response, try the following:
- Click the Edit icon
against any of the associated monitor names. - From the edit screen, click on Test Monitor button. This does a dynamic query to the device for the value of the selected resource, and shows the data.
Incase the agent does not respond, you see a message to this effect. Refer to the troubleshooting tips to resolve the issue.
As an alternative, you can monitor the non-SNMP Linux servers using CLI (telnet or SSH), or the non-SNMPWindows devices using WMI.
