monitoring router-interfaces

Cook, Garry GWCOOK at mactec.com
Wed Aug 25 18:06:56 CEST 2004


Alexander Schaefer wrote:
> Thanks Garry!
> 
> I am testing this both plugins at the moment and i am not
> shure which one i
> should prefere... Following cognitions:
> 
> check_ifstatus  - seems to work well, but i do not understand
> why it says:
> "OK: host 'xx.yy.zz.aa.', interfaces up: 3, down: 0, dormant: 0"
> Allthough i only have 2 active interfaces on this router:
> FastEthernet0 
> and Serial0, The
> BRI0 is in standby state.

check_ifstatus looks for interfaces that are administratively up, but
operationally down. You might want to actually dig into the script for
further understanding of how it counts the interfaces. I never noticed
this before, but the plugin does appear to report one more interface
than is actually in use. For instance, on all of my routers with a
Loopback, Serial, Serial-Subinterface, and Ethernet, I'm seeing 5
interfaces up with check_ifstatus.
Perhaps it's a bug, and maybe a tweak to the code will fix it, although
it's never adversely affected my implementation. It could also be that
I'm missing something about how the plugin actually works. Maybe if I
can find some spare time later I'll take a closer look at it.

 
> check_ifoperstatus - seems to be much more precise for my
> reason but its
> usage is more difficult, because i have about 50 routers in network, i
> should monitor, and the serial interface names are different
> from router to
> router: "Serial0/0", "Serial0". The same "problems" with
> InterfaceIndexValue which is dependent on router modell and
> configuration 

It is more precise in that it only checks a single interface. I've got
the same issue that you mention above, although with double the amount
of routers, so I don't use this plugin extensively.

 
> What is your expirience. Do you use only one of this plugins
> for each router
> or du you combine the plugins? What is your motivation?
> 
> Regards
> Alexander Schaefer

I use check_ifstatus on all of my routers. It's very simple to add the
router hostgroups to the service template, and it checks all of the
interfaces. In some special cases where I have important interfaces
(Core router ATM T1s, Border router Internet T1s), I also use
check_ifoperstatus on individual links. Which means when one of the
interfaces that I consider 'important' goes down, I might receive two
notifications. However, the check_ifstatus notification is more
detailed, and I don't have to login to the router to see which interface
is affected.


> ----- Original Message -----
> From: "Cook, Garry" <GWCOOK at mactec.com>
> To: "Alexander Schaefer" <samogonka at gmx.net>;
> <nagios-users at lists.sourceforge.net>
> Sent: Tuesday, August 24, 2004 8:08 PM
> Subject: RE: [Nagios-users] monitoring router-interfaces
> 
> 
> Alexander Schaefer wrote:
>> Hello!
>> 
>> I have to monitor a middle-large corporate network. To simplify my
>> [snip] Question: it is possible to minitor the failover interfaces
>> with nagios? Does any body do it? 
>> 
>> Thanks for all your suggestions
>> 
>> Alexander Schaefer
> 
> I check specific interfaces on my Cisco routers with
> check_ifstatus and
> check_ifoperstatus. These are in the plugins distribution,
> either in the
> contrib or plugins-scripts directory.
> 
> Garry W. Cook, CCNA
> Network Infrastructure Manager
> MACTEC, Inc. - http://www.mactec.com/
> 303.308.6228 (Office) - 720.220.1862 (Mobile)


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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





More information about the Users mailing list