Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
check_snmp_memory - Monitoring the memory
1.1
2013-12-18
- Nagios 1.x
- Nagios 2.x
- Nagios 3.x
- Nagios 4.x
- Nagios XI
Other
42235
File | Description |
---|---|
check_snmp_memory.1.2 | The plugin |
check_snmp_memory.php | pnp4nagios template for performance graphs |
readme.txt | Just read it |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
By Martin Fuerstenau
Purpose and features of the program:
Checks the memory (physical and virtual) usage for Windows, Solaris, Linux servers, Cisco firewalls and MacAffee WebGateway
Author: Martin Fuerstenau, Oce Printing Systems
martin.fuerstenau_at_oce.com
Date: 14 Jul 2011
Setting a threshold for physical memory doesn't make much sense in modern operating systems. But the virtual
momory should be monitored.
- Windows: Physical and virtual memory is monitored. Threshold (and alarm) for virtual memory.
- Linux: Physical memory, swap space and momory buffers is monitored. Threshold (and alarm) for swap space.
- Solaris: This is a little bit tricky. The swapfs (virtual memory) uses a part of the physical memory and the
swap space. With most memory plugins you only will have the swap space monitored. This plugin monitors
the virtual monitor physical momory, virtual memory and swapspace. If you look for you swapspace with swap -l
you will see the use of your swapfs and not of the swapspace. Threshold (and alarm) is based on virtual memory (swapfs)
./check_snmp_memory -h
check_snmp_memory,Version 1.1
Copyright (c) 2011 Martin Fuerstenau - Oce Printing Systems
Usage: check_snmp_memory -H [-C community] [--cisco] -w -c
or
Usage: check_snmp_memory -h for help.
-H, --hostname=HOST Name or IP address of host to check
-C, --community=community SNMP community (default public)
-v, --snmpversion=snmpversion Version of the SNMP protocol. At present version 1 or 2c
-p, --portsnmpversion=snmpversion Version of the SNMP protocol. At present version 1 or 2c
-w, --warning=threshold Warning threshold of memory usage in percent for virtual memory
(MS Windows systems), swap space (Linux systems) or swapfs (Solaris)
-c, --critical=threshold Critical threshold of memory usage in percent for virtual memory
(MS Windows systems) or swap space (Unix/Linux systems)
--cisco It is a cisco firewall and not a standard Linux system
-h, --help Short help message
Checks the memory (physical and virtual) usage for Windows, Solaris, Linux servers, Cisco firewalls and MacAffee WebGateway
Author: Martin Fuerstenau, Oce Printing Systems
martin.fuerstenau_at_oce.com
Date: 14 Jul 2011
Setting a threshold for physical memory doesn't make much sense in modern operating systems. But the virtual
momory should be monitored.
- Windows: Physical and virtual memory is monitored. Threshold (and alarm) for virtual memory.
- Linux: Physical memory, swap space and momory buffers is monitored. Threshold (and alarm) for swap space.
- Solaris: This is a little bit tricky. The swapfs (virtual memory) uses a part of the physical memory and the
swap space. With most memory plugins you only will have the swap space monitored. This plugin monitors
the virtual monitor physical momory, virtual memory and swapspace. If you look for you swapspace with swap -l
you will see the use of your swapfs and not of the swapspace. Threshold (and alarm) is based on virtual memory (swapfs)
./check_snmp_memory -h
check_snmp_memory,Version 1.1
Copyright (c) 2011 Martin Fuerstenau - Oce Printing Systems
Usage: check_snmp_memory -H
or
Usage: check_snmp_memory -h for help.
-H, --hostname=HOST Name or IP address of host to check
-C, --community=community SNMP community (default public)
-v, --snmpversion=snmpversion Version of the SNMP protocol. At present version 1 or 2c
-p, --portsnmpversion=snmpversion Version of the SNMP protocol. At present version 1 or 2c
-w, --warning=threshold Warning threshold of memory usage in percent for virtual memory
(MS Windows systems), swap space (Linux systems) or swapfs (Solaris)
-c, --critical=threshold Critical threshold of memory usage in percent for virtual memory
(MS Windows systems) or swap space (Unix/Linux systems)
--cisco It is a cisco firewall and not a standard Linux system
-h, --help Short help message
Reviews (1)
bydangtran09, August 28, 2015
this works perfectly for my debian 7.8 checking for windows 2008 server.
however, when i loaded nagios on deb 8.1, and also checking on the same server, i'm getting errors:
Use of uninitialized value $os in substitution (s///) at ./check_snmp_memory line 251.
Use of uninitialized value $os in substitution (s///) at ./check_snmp_memory line 252.
Use of uninitialized value $os in substitution (s///) at ./check_snmp_memory line 253.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 259.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 259.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 430.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 540.
however, when i loaded nagios on deb 8.1, and also checking on the same server, i'm getting errors:
Use of uninitialized value $os in substitution (s///) at ./check_snmp_memory line 251.
Use of uninitialized value $os in substitution (s///) at ./check_snmp_memory line 252.
Use of uninitialized value $os in substitution (s///) at ./check_snmp_memory line 253.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 259.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 259.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 430.
Use of uninitialized value $os in string eq at ./check_snmp_memory line 540.