[Nagiosplug-devel] [ nagiosplug-New Plugins-703898 ] New Plugin: check_traceroute

SourceForge.net noreply at sourceforge.net
Wed Jan 26 20:19:16 CET 2005


New Plugins item #703898, was opened at 2003-03-14 23:03
Message generated for change (Comment added) made by stanleyhopcroft
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=541465&aid=703898&group_id=29880

Category: Perl plugin
Group: None
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Myke Place (mplace)
Assigned to: Subhendu Ghosh (sghosh)
Summary: New Plugin: check_traceroute

Initial Comment:
check_traceroute is a plugin that sends alerts to
Nagios if a specified host is greater than a certain
number of hops away. In cases where a multihomed
network looses a connection and the remote side can be
reached through another gateway check_ping will still
report the connection is being up, though it has
actually gone done. This is an admittedly rare
instance, but perhaps others will find varied uses for
this plugin as well.

check_traceroute is written in Perl and utilizes
Net::Traceroute and Getopts::Long. Usage is as follows:

check_traceroute -t <host> [-w <warning>] [-c <critical>]

----------------------------------------------------------------------

>Comment By: Stanley Hopcroft (stanleyhopcroft)
Date: 2005-01-27 04:18

Message:
Logged In: YES 
user_id=395628

No file attached.

Please would you upload check_traceroute to SourceForge so
it can be included in the /contrib plugins.

Sorry for the huge delay in getting nack to you about this.

----------------------------------------------------------------------

Comment By: Kev Green (kyrian)
Date: 2003-07-28 00:08

Message:
Logged In: YES 
user_id=99923

Just by way of random thought, it might be a useful addition to this 
plugin to add the facility to check for a traceroute via a given host (and 
give the option of whether a traceroute via this host should issue "OK", 
"WARNING", or "CRITICAL" nagios status), so eg. a network 
administrator could use it to check that their upstream transit had not 
failed over to a backup router/connection - or indeed that a routing loop 
had occured -, as it's common for the hostname of particular 
routers/hops in traceroute to change in the event of such a failover.

HTH, HAND.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=541465&aid=703898&group_id=29880




More information about the Devel mailing list