Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_bgp_neighbors
Owner
Website
Hits
162397
Files:
| File | Description |
|---|---|
| README.txt | Installation instructions |
| check_bgp_neighbors.sh | Check Script |
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!
BGP is a fairly hairy medium sized beast which can be hard for new admins to handle. This script was developed to catch some of the problems that can burn an admin when using and monitoring BGP. Several different things are checked to determine the health and status of the BGP connections with neighbors.Often these problems will be made obvious when other services start to fail because of BGP, but this script is meant to help catch BGP problems before they cause larger problems in the network. This script is written for BGP4 on a Cisco router, but it could easily be modified to use with other vendors if the correct OIDs were identified.
Reviews (1)
byhk@, July 16, 2012
this works well for checking our bgp-speakers.
it would be even nicer if the "-n" parameter could be ignored so only one command definition would be needed in case you have a different number of neighbors on some devices.
Also we had to fix one line:
last_output=`/bin/cat /tmp/check_bgp_all.$hostname|grep $neighbor`
changed to:
last_output=`/bin/cat /tmp/check_bgp_all.$hostname|grep $neighbor:`
the ":" is needed to match only exact neighbor IPs, we for example hat x.y.c.2 and x.y.c.20 as neighbors to one bgp-speaker therefore the grep without ":" made for some bad responses which lead to expr-errors later in the script.
it would be even nicer if the "-n" parameter could be ignored so only one command definition would be needed in case you have a different number of neighbors on some devices.
Also we had to fix one line:
last_output=`/bin/cat /tmp/check_bgp_all.$hostname|grep $neighbor`
changed to:
last_output=`/bin/cat /tmp/check_bgp_all.$hostname|grep $neighbor:`
the ":" is needed to match only exact neighbor IPs, we for example hat x.y.c.2 and x.y.c.20 as neighbors to one bgp-speaker therefore the grep without ":" made for some bad responses which lead to expr-errors later in the script.
