Monitoring active WAN path

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Eric Welch
> Sent: Monday, November 13, 2006 1:44 PM
> To: nagios-users at lists.sourceforge.net; ewelch at novacoast.com
> Subject: [Nagios-users] Monitoring active WAN path
> 
> Hi list
> 
> I am trying to figure out how to monitor which WAN path is an active
path
> between a home office and a remote office.  I have two point to point
> connections.  The routers are cisco.  The routing protocol is eigrp.
All
> devices along both paths at any one time are all pingable.  EIGRP is
> controlling the "active" path.  I would like to determine if the
active
> path changes or which link is active.

Just a suggestion but we monitor our BGP links via SNMP via --

define command {
    command_name                   check_bgp_peer_state
    command_line                   $USER1$/check_snmp -H $HOSTADDRESS$
-o .1.3.6.1.2.1.15.3.1.2.$ARG1$ -s 6 -C $USER3$ -l 'BGP Peer $ARG1$
State'
    }

.1.3.6.1.2.1.15.3.1.2 is the bgpPeerState MIB for cisco routers, $ARG1$
is the ip of the peer and 6 is the response to expect when the peer is
established. Maybe there is something similar for EIGRP?
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hi
rp_c/ch07/h_eigmib.htm#wp1064141 looks promising.

--
Marc

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null