Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_network.pl
Last Release Date
2017-11-30
Compatible With
- Nagios 3.x
- Nagios 4.x
Owner
License
GPL
Hits
5448
Files:
| File | Description |
|---|---|
| check_network.pl | check_network.pl |
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!
https://github.com/throwsb/nagios-checks/blob/master/check_network.md
check_network.pl - Checks the Network statistics. It will also provide the following statistics:
rxKBsec - Total number of kilobytes received per second.
txKBsec - Total number of kilobytes transmitted per second.
rxPCKsec - Total number of packets received per second.
txPCKsec - Total number of packets transmitted per second.
Usage:
usage: check_network.pl -blhds -c -w
-b Network device bandwidth
Alerts can be used against rxKBsec and txKBsec. Data is collected for each
network interface except for localhost (l0). You will be required to pass
the warning and critical values. The choice is also available to set alerting
against the high (-h) or low (-l) range. An example of low would be alerting if received
or transfer bandwidth is below a certain threshold. An example of high would
be alerting if received or transfer bandwidth exceeds a certain threshold.
Details on metrics collected are as follows.
rxKBsec - Total number of kilobytes received per second.
txKBsec - Total number of kilobytes transmitted per second.
rxPCKsec - Total number of packets received per second.
txPCKsec - Total number of packets transmitted per second.
Example call
Call with thresholds on high values:
check_network.pl -b -h -w 100 -c 200
-e Network device failures or errors
Data is collected for each network interface except for localhost (l0). You
will be required to pass the warning and critical values. The choice is also
available to set alerting against the high (-h) or low (-l) range. An
example of low would be alerting if errors are below a certain threshold.
An example of high would be alerting if errors exceeds a certain threshold.
Details on metrics collected are as follows. All will report alerts.
rx_errorsec - Total number of bad packets received per second.
tx-errorsec - Total number of bad packets received per second.
coll_sec - Total number of bad packets received per second.
rx_dropsec - Number of received packets dropped per second because of
a lack of space in linux buffers.
tx_dropsec - Number of transmitted packets dropped per second because of
a lack of space in linux buffers.
Example call
Call with thresholds on high values:
check_network.pl -e -h -w 10 -c 20
-s Network TCP established socket count.
Data is collected for TCP sockets currently in use by the system. You
will be required to pass the warning and critical values. The choice is also
available to set alerting against the high (-h) or low (-l) range. An
example of low would be alerting if errors are below a certain threshold.
An example of high would be alerting if errors exceeds a certain threshold.
Details on metrics collected are as follows. All will report alerts.
TCP_Active_Sockets - Number of TCP sockets currently in use.
Example call
Call with thresholds on high values:
check_network.pl -s -h -w 100 -c 200
-c
Sets the critical threshold value. This will depend if checking for high
limit (-h) or low limit (-l).
-w
Sets the warning threshold value. This will depend if checking for high
limit (-h) or low limit (-l).
-i
This sets the interval for a single data run to collect.
The result is the average of the collected sample.
The default is 10.
-h Set threshold checking to high limit.
-l Set threshold checking to low limit.
-d Debug
rxKBsec - Total number of kilobytes received per second.
txKBsec - Total number of kilobytes transmitted per second.
rxPCKsec - Total number of packets received per second.
txPCKsec - Total number of packets transmitted per second.
Usage:
usage: check_network.pl -blhds -c
-b Network device bandwidth
Alerts can be used against rxKBsec and txKBsec. Data is collected for each
network interface except for localhost (l0). You will be required to pass
the warning and critical values. The choice is also available to set alerting
against the high (-h) or low (-l) range. An example of low would be alerting if received
or transfer bandwidth is below a certain threshold. An example of high would
be alerting if received or transfer bandwidth exceeds a certain threshold.
Details on metrics collected are as follows.
rxKBsec - Total number of kilobytes received per second.
txKBsec - Total number of kilobytes transmitted per second.
rxPCKsec - Total number of packets received per second.
txPCKsec - Total number of packets transmitted per second.
Example call
Call with thresholds on high values:
check_network.pl -b -h -w 100 -c 200
-e Network device failures or errors
Data is collected for each network interface except for localhost (l0). You
will be required to pass the warning and critical values. The choice is also
available to set alerting against the high (-h) or low (-l) range. An
example of low would be alerting if errors are below a certain threshold.
An example of high would be alerting if errors exceeds a certain threshold.
Details on metrics collected are as follows. All will report alerts.
rx_errorsec - Total number of bad packets received per second.
tx-errorsec - Total number of bad packets received per second.
coll_sec - Total number of bad packets received per second.
rx_dropsec - Number of received packets dropped per second because of
a lack of space in linux buffers.
tx_dropsec - Number of transmitted packets dropped per second because of
a lack of space in linux buffers.
Example call
Call with thresholds on high values:
check_network.pl -e -h -w 10 -c 20
-s Network TCP established socket count.
Data is collected for TCP sockets currently in use by the system. You
will be required to pass the warning and critical values. The choice is also
available to set alerting against the high (-h) or low (-l) range. An
example of low would be alerting if errors are below a certain threshold.
An example of high would be alerting if errors exceeds a certain threshold.
Details on metrics collected are as follows. All will report alerts.
TCP_Active_Sockets - Number of TCP sockets currently in use.
Example call
Call with thresholds on high values:
check_network.pl -s -h -w 100 -c 200
-c
Sets the critical threshold value. This will depend if checking for high
limit (-h) or low limit (-l).
-w
Sets the warning threshold value. This will depend if checking for high
limit (-h) or low limit (-l).
-i
This sets the interval for a single data run to collect.
The result is the average of the collected sample.
The default is 10.
-h Set threshold checking to high limit.
-l Set threshold checking to low limit.
-d Debug
Reviews (0)
Be the first to review this listing!
