Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

Directory Tree

check_rx_tx_packets

Rating
0 votes
Favoured:
0
Current Version
1.0
Last Release Date
2015-08-11
Compatible With
  • Nagios 1.x
  • Nagios 2.x
  • Nagios 3.x
  • Nagios 4.x
Owner
License
GPL
Hits
6861
Files:
FileDescription
check_rx_tx.pyPython plugin described above
Network Monitoring Software - Download Nagios XI
Log Management Software - Nagios Log Server - Download
Netflow Analysis Software - Nagios Network Analyzer - Download
Plugin created for capture RX and TX statistics from Linux OS interfaces. Useful to analyze packet tendencies, such as total transferred, dropped, framed and overrun packets. This script follows a very simple approach and outputs a nagios formatted metric syntax for chart creation.

Usage: check_rx_tx.py [OS Interface]
Plugin created for capturing RX and TX statistics from Linux OS interfaces.
Useful to analyze package tendencies, such as total transfered, dropped, framed and overrun packets. This plugin follows a very simple approach and outputs a nagios formatted metric syntax for chart creation.

IMPORTANT: This script relies on `ifconfig` command, so soon it will be outdated but I hope to rewrite using a better replacement like ethtool or ip.

To better explain the output:

- RX: Received packets
- TX: Transfered packets
- errors: Packets which could not be transfered/received due errors
- dropped: Normally indicates configuration/communication
errors (eg: One side operating in half-duplex and the other in full-duplex)
- overruns: The interface has two buffers, one for transmit and the other one for receive and when one of these buffers reachs its limit the surplus packets are discarted as 'overrruns'
- frame: Malformed frames
- carrier: Physical link error. Very common in HUBS, should not never occur with switch environments.

Usage: check_rx_tx.py [OS Interface]

Author: Marcelo Varge (marcelo.varge@gmail.com)